I have a customer that can run a btrieve application fine from any workstation and even from the server. But when he tries to run it remotely throught terminal services he gets a status 3014
The MicroKernel router could not complete the operation because it did not find an engine (local or remote) that could process the operation. Possible causes include:
• The target network operating system is not available.
• The target engine is not available.
• In a Windows 3.x environment, you are using a shared drive name that contains a space. To resolve the condition, remove the space from the shared drive name. For example, if you connect to a server named “D Drive”, change the share name to “D_Drive”.
Server Windows 2000 Server S/P 4
Pervasive v7 S/P 6
Instead of using a Drive Mapping, you need to use the local file (C:\\).
This isn't a Pervasive setting but an application setting.
On the other hand, if the Terminal Server and the Database Server are the same box, then you may continue to have problems. Pervasive did not start supporting this configuration until Pervasive.SQL 2000i SP3. Having said that, Pervasive, Microsoft and even Citrix all recommend that you not run background services on Terminal Servers. A Terminal Server box is tuned for running foreground (user) processes, and background processes (of which Pervasive.SQL is one) may not get sufficient CPU time or memory to do their job correctly.
There are two options:
1) Set up a different server as the TS box.
2) Upgrade the database to a more current version.