Hi,

I'm trying to set up Pervasive.SQL Server v7 (sp6) on Win2000 Server with
Terminal Services. I have an application that I can run locally on the
server, but when I attempt to run it via a terminal session, I get Btrieve
error 3020.

(3020: An error occurred while loading the MicroKernel. You receive this
status code when an error occurs while loading the MicroKernel or when
access to the server and client machine's shared memory objects are
unavailable. Check the Pervasive Event Log (PVSW.LOG) for more
information.).

When I check the PVSW.LOG file in the windows directory, there is no mention
of the error. I found another PVSW.LOG file in the user's WINDOWS directory
and it contained the error (08-21-2003 18:00:13 W3MIF112 0000088C
ce\Monitor.exe" REMUS E 00000225 3020:
EstablishSessionWithEngine(). Failed to get to InitData. OS rc=2), so it
looks like the pervasive engine is looking for W3MIF112.DLL in the wrong
place.

Does anyone know how to set up Pervasive.SQL Server v7 and MS Terminal
Services so that it will work.

Thanks,
- Greg

Did you install Pervasive through a terminal session (=nono) or at the
console?

On Thu, 21 Aug 2003 19:17:28 -0700, "Greg Doherty" <No Spam Please>
wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/

I installed everything from the console.
I tried installing everything before installing terminal services. After
installing terminal services it doesn't work through a terminal session.
I also tried installing after terminal services was installed (using
Add/Remove Programs). It still doesn't work through a terminal session.

Any Ideas? It looks like the server engine is trying to access stuff in the
clients WINDOWS directory (which it shouldn't).

Regards,
- Greg


"Gordon" <grafzerk (AT) bigfoot (DOT) no.spam.please.com> wrote

As the engine is (should) already be running, I see no reason why it
should poke in the client's windows directory. Only reason for this to
happen would be if the service is started using this particular
account. Obviously the client configuration *will* create a pvsw.log
file in this directory to log client-side activity.

Somehow your log seems to indicate that an attempt is made to
auto-start the server engine as if it were a workstation engine. With
the engine already started I would expect an error, though different
than 3020.

Just a silly question: can you target the server using a different
client machine?

Gordon

On Fri, 22 Aug 2003 09:35:22 -0700, "Greg Doherty" <No Spam Please>
wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/

Hi Gordon,

Thanks for your help.

I gave up on trying to get this to work and uninstalled the Pervasive.SQL
server from the Terminal Services machine. I installed Pervasive.SQL server
on a separate Win2000 server and just installed my app with the Pervasive
client on the Terminal Services machine. It works fine this way, but I now
have 2 servers.

Also, I did a search through DevTalk on the Pervasive website and every
mention of Terminal Services with Pervasive 7 has a reply from someone at
Pervasive saying the Pervasive 7 was not supported with terminal services.
I even found that P.SQL 2000 didn't work until SP 2.

Have you ever managed to get Pervasive.SQL Server v7 to work on a Win2000
Server with Terminal Services installed?

Regards,
- Greg

"Gordon" <grafzerk (AT) bigfoot (DOT) no.spam.please.com> wrote

Further, Pervasive never supported the use of the Pervasive Engine *AND* client
on the *same* terminal server, either, until PSQL2000i SP3 or SP4. Your
solution is correct for PSQL7. A better solution (if you wanted single-server)
would be to use PSQLV8 instead.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: September 16-18: See our web site for details!

Greg Doherty wrote:

Still don't fancy the idea of a Terminal Server acting as a database
server. Just like running MS Exchange server on it, but even with
worse timing issues....

Can't say I ever got it working, but then I never set my heart to
really try. Did have some serious issues already running P2000 from
within the administrative TS, still looks like a big 'nono' to me.


On 25 Aug 2003 20:18:48 GMT, Bill Bach <bbach (AT) cncdsl (DOT) com> wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/