Since upgrading to Pervasive 8 about 2 weeks ago, we have experienced 3 instances where the process ntdbsmgr.exe will jump up to 95-99% utilization on the server.  I can't identify the cause, but the result is that all of my clients' DBA programs will lock up.  The only way to resolve is to reboot the server.
 
I am running Windows NT4.0 SP6a, and I had to upgrade from 2000i to add additional seats.
 
Any suggestions would be greatly appreciated.

Actually. the Pervasive web site does cite NT4SP6a as the minimum WIN NT Platform for Pervasive 8 but I concur, upgrading to WIN2K would probably be a good idea.

Do either of you have port-scanning software installed on the server or the clients?

I don't have port scanning installed either.
 
In looking at my Pervasive monitor, I noticed one client using an SPX connection instead of a TCP connection (indicated with an address formatted as s:000000000 123456).  I uninstalled and reinstalled that particular client, recalling that I had trouble with the initial installation.  The lock-up has not yet reproduced itself - that was on 4/27.
 
Also, in checking the pvsw.log file on the server, I found entries (the last 4) that seem to coincide with the times that the process begins hogging memory.  I don't know for sure that these entries are actually related to my problem, but  there have been no other entries logged since I reinstalled the client.
 
04-13-2005 17:11:01 NTMKDE  0000005E NTDBSMGR.EXE    DBASERVER   I  MicroKernel is using default settings.
04-13-2005 17:11:12 NTMKDE  0000005E NTDBSMGR.EXE    DBASERVER  W Resources allocated
04-13-2005 17:12:03 NTMKDE  0000005E NTDBSMGR.EXE    DBASERVER   I   Resources released
04-13-2005 17:14:46 NTMKDE  00000099 NTDBSMGR.EXE    DBASERVER    I   MicroKernel is using the default setting for File Growth Factor.
04-13-2005 17:14:46 NTMKDE  00000099 NTDBSMGR.EXE    DBASERVER   I    MicroKernel is using the default setting for Enable Watchdog.
04-13-2005 17:15:34 NTMKDE  00000099 NTDBSMGR.EXE    DBASERVER   W  Resources allocated
04-18-2005 12:49:34 NTMKDE  000000B9 NTDBSMGR.EXE    DBASERVER   W  Resources allocated
04-22-2005 11:16:05 NTMKDE  0000006D NTDBSMGR.EXE    DBASERVER   W  Resources allocated
04-25-2005 12:49:48 NTMKDE  000000C1 NTDBSMGR.EXE    DBASERVER   W  Resources allocated
04-26-2005 11:28:16 NTMKDE  000000BD NTDBSMGR.EXE    DBASERVER   W  Resources allocated
 
I will follow up again in a week or two with another update.

Well, after finding and reinstalling the SPX client, I thought we were in the clear.  All was running smoothly for about 3 weeks.  Alas, the process has again started locking up - another two times so far.

Any further information on this thread?
 
I just found in Taskmamager that  my NTDBSMGR is hogging tons of memory (58,596 K!)-- hadn't noticed it before -- and my clients have been very slow recently and locking up.  (I haven't noticed the utilization going high).
 
I'm running WIN2K server, 2000i SP3, with Vers 7.90.230.36 of NTDBSMGR.
 
A Google search found references to this problem (one also referred specifically to TAS), but frankly  it's beyond my level. Has anyone pursued it thru Pervasive Support and gotten any answers?
 
I can do SP4, but will it help?
 
Sure would appreciate any help.
 
Thanks.
 
 
 

Quote from Dick   on 06/17/05 at 07:45:15:

 
I installed 2000i SP4 a week ago. I have yet to have another lock-up or fault crash. before that the log showed one almost daily. So far So good.
 
John

"There should be a big button on the front of the box that deletes all unwanted dialogs..... "
 
David, what box are we talking about?  I haven't seen any errors/error messages and no big buttons.  Just this big number in Taskmanager...do I hit 'end process' there?