enterprise 6.0 and sql2000 on NT

Hi Keegen,

It sounds like you've been having some fun! The errors 86/87 are likely a down to either a resource running out on the server, they mean there are no more handles for files left in pervasive, this can be tweaked to a higher value.

3006 and 3111 are Problems with sessions to the Microkernal being lost or disconnected. This can be due to failing/unreliable hardware but given the other errors I would be inclined to suggest they may also be a symptom of the error code 86/87 the system has run out of handles and then it loses track of a session which may then give a 3006 at the client.

Error 97, this is indicative of the Pervasive engine not being set up correctly for use with Maximizer.

I feel that you are probably going to need some professional help to get this sorted out.

I would suggest from your location that I'm probably a bit further away than may be convienient
I recommend that you contact Gord Thompson at Regensys in Kingston ON, he is VERY good and will be able to resolve this problem.

I am however more than happy to keep discussing this on this site, what we will need to try and further track down the root cause of the problem is to establish what sequence the errors occur in, and the conditions under which they occur. For instance is it the first user into the system that fails or is only when you have ten or more machines running that you start to have difficulties.

Hopefully we can resolve this quickly for you,

Regards

Nick Welburn
CABC Support Manager
+44 (0)1635 579970

>loaded maximizer ent 6.0 onto server(25 users)
>now we get error codes 87/86/97/3006/3111
>nobody can log on

I did a client/server upgrade in Ottawa last weekend and had a similar experience.

- Installed P.SQL_2000 and patched to SP2a. Worked great.

- Installed Maximizer on the server. All workstations stopped working. ("There has been a data access error probably caused by this single user version...".)

- Reinstalled P.SQL_2000 on the server. No joy.

- Installed the full P.SQL_2000 Client software on the server. Still no joy.

- Removed Maximizer and P.SQL_2000, then reinstalled P.SQL_2000. Joy.

Lesson learned: Don't install Maximizer on the server.

keegan: Try removing Maximizer and P.SQL_2000 from the server, then reinstall P.SQL_2000 and patch to SP2a. Use the information in
http: //204.174.40.40/scripts/content.asp?ref_no=000825-0000

as a guide. If you continue to have difficulties, either post back here or drop me a note at

gdt (at) kingston.net

Oops. The configuration document referenced above is obsolete. The current one is

http: //204.174.40.40/scripts/content.asp?ref_no=000905-0002

Thanks Gord
your new link has more info than the previous one I had

P2000SQL seems to be working We did not install maxEnt 6.0 on server
however when installing on to Wkstn after SQL
max ent over wrote BT 7.91 and required and did not connect to server
Should MAX Ent be installed on wkstn first before the SQL setup
Tks

>Should MAX Ent be installed on wkstn first before the SQL setup

Under normal circumstances it is not necessary to install the full P.SQL client on each workstation. Just run the Maximizer setup program and select "client/server" as the configuration.