Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

8.7 sp3 server dies with no clear reason

Status
Not open for further replies.
wvotta

wvotta

MIS
Aug 19, 2009
31
US
Seemingly out of nowhere, my server dies and no one can log in to MAX (our ERP using pervasive) and neither can I on the server. We're running Windows Server 2000 with all available updates, service packs and patches. I've reinstalled the engine and am still having the issue. Out of nowhere, the db becomes unresponsive and new client login attempts time out and MAX throws Btrieve Config.dat file not open errors, even on the server.
The fix is to stop the 2 Pervasive services and start them again. Nothing helpful is in the logs pinpointing the exact problem, but I will post what the logs say after the restart. It seems to only catch the timeout errors when I attempt to start the client MAX application on the server itself. Also, the Control Center on the server doesn't even show its a Pervasive Server when this happens (until I restart the services and open it up again).

Here are the log items that seem to relate to this issue:
08-19-2009 06:32:32 W3CACHE 00000C2C W3DBSMGR.EXE MAX W Resources allocated
08-19-2009 06:33:37 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:34:35 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (5.22.1.10): Error 8520 - A timeout occurred during the initialization of SRDE engine
08-19-2009 06:34:35 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (5.22.1.10): Error 8520 - A timeout occurred during the initialization of SRDE engine
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:35:39 ECAS_API 00000B40 pcc.exe MAX E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 06:36:41 W3CACHE 00000C2C W3DBSMGR.EXE MAX I Resources released
08-19-2009 06:36:46 NTMKDE 00000564 NTDBSMGR.EXE MAX W Resources allocated
08-19-2009 07:33:47 NTMKDE 0000057C NTDBSMGR.EXE MAX W Resources allocated


Here's some error info from a client running xp and the CRD application that automates some crystal reports (going back days.. we have this problem at least once a day and this morning twice already!):
08-13-2009 11:03:44 ECAS_API 00001634 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-13-2009 11:17:18 ECAS_API 0000090C pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-14-2009 17:08:34 W3NSL244 0000096C crd.exe DEPLOY E 3112: Status 10054 returned while receiving a maximum of 40960 bytes.
08-17-2009 07:55:16 W3CACHE 00001A78 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 08:01:27 W3CACHE 00000448 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 08:05:56 W3CACHE 00000448 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 08:22:02 W3CACHE 000017A8 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 08:27:11 W3CACHE 000017A8 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 08:32:06 W3CACHE 00000FEC W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 08:49:16 W3CACHE 00000FEC W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 08:49:35 W3CACHE 00000DA4 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 08:57:04 W3CACHE 00000DA4 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 08:57:35 W3CACHE 000016AC W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 08:59:04 W3CACHE 000016AC W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 09:30:26 W3CACHE 00000620 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 09:50:25 W3CACHE 00000620 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 09:51:44 W3CACHE 000015AC W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 09:55:33 W3CACHE 000015AC W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 10:01:18 W3CACHE 0000066C W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 10:13:37 W3CACHE 0000066C W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 10:16:21 W3CACHE 000016BC W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 10:29:10 W3CACHE 000016BC W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 10:31:33 W3CACHE 00001608 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 10:43:32 W3CACHE 00001608 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 10:46:25 W3CACHE 00001408 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 10:58:24 W3CACHE 00001408 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 11:01:33 W3CACHE 00000EDC W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 11:13:42 W3CACHE 00000EDC W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 11:16:30 W3CACHE 000013EC W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 11:27:19 W3CACHE 000013EC W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 11:31:08 W3CACHE 000016C0 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 11:42:37 W3CACHE 000016C0 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 11:45:44 W3CACHE 00001778 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 11:58:23 W3CACHE 00001778 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 12:30:41 W3CACHE 000016A8 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 12:42:10 W3CACHE 000016A8 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 12:45:43 W3CACHE 000008E4 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 12:56:42 W3CACHE 000008E4 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 13:00:47 W3CACHE 00000AD8 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 13:12:16 W3CACHE 00000AD8 W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 13:15:51 W3CACHE 0000073C W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 13:30:20 W3CACHE 0000073C W3DBSMGR.EXE DEPLOY I Resources released
08-17-2009 13:30:52 W3CACHE 00000850 W3DBSMGR.EXE DEPLOY W Resources allocated
08-17-2009 13:49:00 ECAS_API 00001308 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-17-2009 15:07:59 W3NSL244 00001784 crd.exe DEPLOY E 3111: Status 10054 returned while sending 146 bytes.
08-17-2009 15:07:59 W3NSL244 00001784 crd.exe DEPLOY E 3131: Reconnect not attempted, AutoReconnect not enabled on either client or server.
08-18-2009 11:17:05 ECAS_API 00000818 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-18-2009 11:18:31 ECAS_API 0000173C pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-18-2009 11:21:26 ECAS_API 00001B34 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-18-2009 12:09:43 ECAS_API 00001110 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-18-2009 12:16:00 ECAS_API 00001A98 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:26 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:29 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-19-2009 07:54:32 ECAS_API 00001950 pcc.exe DEPLOY E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
 
Sort by date Sort by votes
I believe it's a configuration issue, but I don't know what the configurations should be. How do I output all the settings for posting here?
 
Upvote 0 Downvote
The settings are stored in the registry under HKLM\Software\Pervasive Software.
I don't think it's a config issue though.

The first thing I would suggest would be to rename the W3DBSMGR.EXE (which is the workgroup/cache engine). When the server engine crashes, the cache engine loads and causes other errors.

The second thing I would suggest would be to stop the PSQL services, rename the PVSW.LOG, and restart the services. This will clear out the PVSW.LOG and give you a better idea of the actual behavior being seen.

PCC doesn't display the server because it things the cache engine is running.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Upvote 0 Downvote
Ok, it crashed again last night but this morning I was not able to heal it by restarting the services. This is what I did:
Yesterday I renamed the cache engine so it'd stop loading (on your suggestion).
I stopped both Pervasive services in the Service manager and moved the old log file to my desktop (on your suggestion).
It took a long time for the transactional service to stop and didn't fully until after Windows complained.
Once completely stopped, I restarted them but still could not get back into Max, same error.
I tried again to stop and start both services, this time it going much faster, and still couldn't get back in.
I changed the cache engine filename back again and attempted the restart 2 or 3 more times with no success getting the Max client to work.
I finally renamed the cache engine once more (tried another time or two to no avail) and restarted the entire server. That worked, so now we're back up and the cache engine is still disabled.
Here's the new log info, which is more informative, thankfully, but still mysterious to me:
Date Time Component Process Process Name Machine Name Type Category Msg ID Message
---------- -------- --------------- -------- --------------- --------------- ---- ---------- -------- --------------------------------------------------
08-20-2009 06:19:22 W3MIF169 00000A90 SYSMAN.EXE MAX E WaitOnIPCControlSem(). WaitForSingleObject failed. OS rc=128.
08-20-2009 06:19:32 ECAS_API 00000A90 SYSMAN.EXE MAX E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-20-2009 06:19:32 ECAS_API 00000A90 SYSMAN.EXE MAX E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-20-2009 06:19:32 ECAS_API 00000A90 SYSMAN.EXE MAX E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-20-2009 06:19:32 ECAS_API 00000A90 SYSMAN.EXE MAX E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-20-2009 06:19:58 NTMKDE 00001230 NTDBSMGR.EXE MAX W Resources allocated
08-20-2009 06:20:01 W3MIF169 00000C40 SYSMAN.EXE MAX E WaitOnIPCControlSem(). WaitForSingleObject failed. OS rc=128.
08-20-2009 06:20:10 ECAS_API 00000C40 SYSMAN.EXE MAX E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-20-2009 06:20:10 ECAS_API 00000C40 SYSMAN.EXE MAX E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-20-2009 06:20:10 ECAS_API 00000C40 SYSMAN.EXE MAX E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-20-2009 06:20:10 ECAS_API 00000C40 SYSMAN.EXE MAX E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-20-2009 06:21:18 NTMKDE 00001230 NTDBSMGR.EXE MAX I Resources released
08-20-2009 06:22:41 W3MIF169 00001254 SYSMAN.EXE MAX E WaitOnIPCControlSem(). WaitForSingleObject failed. OS rc=128.
08-20-2009 06:22:55 W3CACHE 00001360 W3DBSMGR.EXE MAX W Resources allocated
08-20-2009 06:23:34 W3CACHE 00001360 W3DBSMGR.EXE MAX I Resources released
08-20-2009 06:23:39 W3MIF169 00001360 SYSMAN.EXE MAX E WaitOnIPCControlSem(). WaitForSingleObject failed. OS rc=128.
08-20-2009 06:23:48 W3CACHE 00000CDC W3DBSMGR.EXE MAX W Resources allocated
08-20-2009 06:24:21 W3CACHE 00000CDC W3DBSMGR.EXE MAX I Resources released
08-20-2009 06:24:33 W3MIF169 000013A8 pcc.exe MAX E WaitOnIPCControlSem(). WaitForSingleObject failed. OS rc=128.
08-20-2009 06:24:36 ECAS_API 000013A8 pcc.exe MAX E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-20-2009 06:24:36 ECAS_API 000013A8 pcc.exe MAX E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-20-2009 06:30:46 NTMKDE 00000C14 NTDBSMGR.EXE MAX W Resources allocated
08-20-2009 06:30:57 W3MIF169 00000F6C SYSMAN.EXE MAX E WaitOnIPCControlSem(). WaitForSingleObject failed. OS rc=128.
08-20-2009 06:32:19 NTMKDE 00000C14 NTDBSMGR.EXE MAX I Resources released
08-20-2009 06:37:59 NTMKDE 000005E0 NTDBSMGR.EXE MAX W Resources allocated
 
Upvote 0 Downvote
If it matters, here's the contents of the old log file that I moved to the desktop:
(I'm just pasting the tail end starting with the last line that you've already seen from this log in my first post, to show the complete file.)
08-19-2009 07:33:47 NTMKDE 0000057C NTDBSMGR.EXE MAX W Resources allocated
08-19-2009 09:21:33 W3CACHE 000013C0 W3DBSMGR.EXE MAX W Resources allocated
08-20-2009 06:15:12 W3CACHE 000013C0 W3DBSMGR.EXE MAX I Resources released
08-20-2009 06:17:51 ECAS_API 000012F4 pcc.exe MAX E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-20-2009 06:17:51 ECAS_API 000012F4 pcc.exe MAX E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
 
Upvote 0 Downvote
This server has 2 NICs (it's a HP DL380 G3 server), one of which is 192.168.100.151, which is the ip address every computer associates with the netbios name MAX in both their hosts file and our local dns. Pervasive is configured to listen on 0.0.0.0, so could that be the problem? The other NIC is 192.168.100.10...
I know you don't believe it's a configuration issue, but just in case, here are my settings, exported from the registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Btrieve Requester]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Btrieve Requester\Version 8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Btrieve Requester\Version 8\Settings]
"Splash Screen"="Yes"
"Embedded Spaces"="no"
"Verify Key Length"="yes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 8\Settings]
"TCP connect timeout"=dword:0000000f
"Supported protocols"="TCPIP"
"Runtime server"="Yes"
"Enable AutoReconnect"="No"
"Max Multiple Connections"=dword:00000000
"Log Statistics"="No"
"NumSatEntries"=dword:00000001
"SatEntry0"="Max,0,4,3,1,0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{A3896D81-BDF8-11d3-BC90-00104B12EF1F}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{A3896D81-BDF8-11d3-BC90-00104B12EF1F}\Menu]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{A3896D81-BDF8-11d3-BC90-00104B12EF1F}\Namespace]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{C1273D0E-92A5-4242-BDAB-E945472D13C2}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{C1273D0E-92A5-4242-BDAB-E945472D13C2}\Menu]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{C1273D0E-92A5-4242-BDAB-E945472D13C2}\Namespace]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Extendable\{C1273D0E-92A5-4242-BDAB-E945472D13C2}\Namespace\{140B1898-B47A-11D3-9194-00A024C8C314}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Pervasive.SQL BCP]
"ExternalTools"=hex(7):4c,00,69,00,63,00,65,00,6e,00,73,00,65,00,20,00,41,00,\
64,00,6d,00,69,00,6e,00,69,00,73,00,74,00,72,00,61,00,74,00,6f,00,72,00,00,\
00,43,00,3a,00,5c,00,50,00,56,00,53,00,57,00,5c,00,42,00,49,00,4e,00,5c,00,\
47,00,55,00,49,00,4c,00,43,00,41,00,44,00,4d,00,2e,00,45,00,58,00,45,00,00,\
00,2f,00,73,00,00,00,52,00,65,00,62,00,75,00,69,00,6c,00,64,00,00,00,43,00,\
3a,00,5c,00,50,00,56,00,53,00,57,00,5c,00,42,00,49,00,4e,00,5c,00,52,00,42,\
00,4c,00,44,00,47,00,55,00,49,00,2e,00,45,00,58,00,45,00,00,00,00,00,4d,00,\
6f,00,6e,00,69,00,74,00,6f,00,72,00,00,00,43,00,3a,00,5c,00,50,00,56,00,53,\
00,57,00,5c,00,42,00,49,00,4e,00,5c,00,57,00,33,00,4d,00,4f,00,4e,00,56,00,\
37,00,35,00,2e,00,45,00,58,00,45,00,00,00,00,00,4d,00,61,00,69,00,6e,00,74,\
00,65,00,6e,00,61,00,6e,00,63,00,65,00,00,00,43,00,3a,00,5c,00,50,00,56,00,\
53,00,57,00,5c,00,42,00,49,00,4e,00,5c,00,57,00,33,00,32,00,4d,00,41,00,49,\
00,4e,00,54,00,2e,00,45,00,58,00,45,00,00,00,00,00,46,00,75,00,6e,00,63,00,\
74,00,69,00,6f,00,6e,00,20,00,45,00,78,00,65,00,63,00,75,00,74,00,6f,00,72,\
00,00,00,43,00,3a,00,5c,00,50,00,56,00,53,00,57,00,5c,00,42,00,49,00,4e,00,\
5c,00,57,00,42,00,45,00,58,00,45,00,43,00,33,00,32,00,2e,00,45,00,58,00,45,\
00,00,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers\{140B1898-B47A-11D3-9194-00A024C8C314}]
@="Pervasive Config ECP"
"Name"="Pervasive.SQL Configuration"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers\{140B1898-B47A-11D3-9194-00A024C8C314}\Extendable]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers\{8CDB7CF7-8206-484A-A3FB-CE42CFEFDD8B}]
@="Pervasive.SQL BCP"
"Name"="Pervasive.SQL Base Content Provider"
"BaseProvider"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers\{8CDB7CF7-8206-484A-A3FB-CE42CFEFDD8B}\Extendable]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers\{8CDB7CF7-8206-484A-A3FB-CE42CFEFDD8B}\Extendable\{A3896D81-BDF8-11d3-BC90-00104B12EF1F}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Control Center\2.0\Providers\{8CDB7CF7-8206-484A-A3FB-CE42CFEFDD8B}\Extendable\{C1273D0E-92A5-4242-BDAB-E945472D13C2}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Database Names]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Database Names\Version 8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Database Names\Version 8\Settings]
"DBNamesDirectory"="C:\\WINNT"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Microkernel Router]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Microkernel Router\Version 8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Microkernel Router\Version 8\Settings]
"Local"="yes"
"Requester"="yes"
"Use IDS"="no"
"IDS Username"="<None>"
"IDS Password"="<None>"
"Compress IDS Data"="no"
"Gateway Durability"="no"
"Use Cache Engine"="no"
"Load Retries"=dword:00000005
"Target Engine"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Server Engine]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Server Engine\Version 8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Server Engine\Version 8\Settings]
"Balanced Trees"="NO"
"File Version"="0800"
"System Data"="YES"
"Max MicroKernel Memory Usage"=dword:0000003c
"Logging"="NO"
"Cache Size"=dword:0006664c
"Merge Sort Buffer Size"=dword:00000000
"Max Communication Buffer Size"=dword:00000040
"Transaction Durability"="NO"
"Transaction Log Buffer Size"=dword:00000400
"Transaction Log File Size"=dword:00000800
"Systrans Bundle Limit"=dword:0000ffff
"Systrans Time Limit"=dword:00002710
"Transaction Logging"="YES"
"Background Threads"=dword:00000020
"Wait-lock Timeout"=dword:0000000f
"Transaction Log Directory"="C:\\PVSW\\BIN\\MKDE\\LOG"
"Trace"="NO"
"Trace File"="C:\\PVSW\\BIN\\MKDE.TRA"
"Trace Databuf Len"=dword:00000080
"Trace Keybuf Len"=dword:00000080
"Trace Ops"="ALL"
"Validate Request"="NO"
"Max Pending IO"=dword:00000800
"File Growth Factor"=dword:0000000f
"Page Server Allow Client Cache"="YES"
"Prompt For Client Credentials"="NO"
"Allow Client-Stored Credentials"="YES"
"Enable Watchdog"="YES"
"System Cache"="NO"
"Preallocate"="NO"
"Minimal States"="NO"
"Minimal States Delay"=dword:0000012c
"Worker Threads"=dword:00000004
"Max Remote Communications Buffer Size"=dword:00000040
"Remote Read Buffer Size"=dword:00000004
"Remote Worker Threads"=dword:00000010
"Remote Sessions Enabled"="YES"
"Supported Protocols"=hex(7):54,00,43,00,50,00,2f,00,49,00,50,00,00,00,00,00
"Protocol Init Timeout"=dword:0000003c
"TCPIP Multi-Homed"="YES"
"Listen IP Address"="0.0.0.0"
"Home Directory"="C:\\PVSW\\BIN"
"Enable AutoReconnect"="NO"
"AutoReconnect Timeout"="180"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Server Engine\Version 8\Settings\Hook Modules]
"0"="c:\\pvsw\\bin\\cnstring.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Server Engine\Version 8\Settings\Hook Modules\CNString]
@="0"
"Description"="Connection String Hook Module for remote DB Names"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Workgroup Engine]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Workgroup Engine\Version 8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Workgroup Engine\Version 8\Settings]
"Balanced Trees"="NO"
"File Version"="0800"
"System Data"="YES"
"Max MicroKernel Memory Usage"=dword:0000003c
"Logging"="NO"
"Cache Size"=dword:00008000
"Merge Sort Buffer Size"=dword:00000000
"Max Communication Buffer Size"=dword:00000040
"Transaction Durability"="NO"
"Transaction Logging"="YES"
"Transaction Log Buffer Size"=dword:00000400
"Transaction Log File Size"=dword:00000800
"Systrans Bundle Limit"=dword:0000ffff
"Systrans Time Limit"=dword:00002710
"Background Threads"=dword:00000020
"Wait-lock Timeout"=dword:0000000f
"Transaction Log Directory"="C:\\PVSW\\BIN\\MKDE\\LOG"
"Work Space"=""
"Trace"="NO"
"Trace File"="C:\\PVSW\\BIN\\MKDE.TRA"
"Trace Databuf Len"=dword:00000080
"Trace Keybuf Len"=dword:00000080
"Trace Ops"="ALL"
"Prompt For Client Credentials"="NO"
"Allow Client-Stored Credentials"="YES"
"System Cache"="YES"
"Preallocate"="NO"
"Worker Threads"=dword:00000004
"Max Remote Communications Buffer Size"=dword:00000040
"Remote Read Buffer Size"=dword:00000004
"Remote Worker Threads"=dword:00000010
"Remote Sessions Enabled"="YES"
"Supported Protocols"=hex(7):53,00,50,00,58,00,49,00,49,00,00,00,54,00,43,00,\
50,00,2f,00,49,00,50,00,00,00,4e,00,45,00,54,00,42,00,49,00,4f,00,53,00,00,\
00,00,00
"Home Directory"="C:\\PVSW\\BIN"
"Protocol Init Timeout"=dword:0000003c
"TCPIP Multi-Homed"="YES"
"Listen IP Address"="0.0.0.0"
"Enable AutoReconnect"="NO"
"AutoReconnect Timeout"="180"
"Validate Request"="NO"
"Max Pending IO"=dword:00000800
"File Growth Factor"=dword:0000000f
"Enable Watchdog"="YES"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MKC]
"UseDelayedSyncClose"="YES"
"SyncCloseDelay(msecs)"="50"
"ThreadsPerConnection"="10"
"UseDelayedSyncCloseForRI"="YES"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Monitor Utility]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Monitor Utility\Version 8.70]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Monitor Utility\Version 8.70\Settings]
"Save Settings"="Yes"
"Refresh Rate"=dword:00000004
"MKDE Resource Usage Window AutoRefresh"="Yes"
"MKDE Communication Statistics Window AutoRefresh"="Yes"
"MKDE Active Files Window AutoRefresh"="Yes"
"MKDE Active Users Window AutoRefresh"="Yes"
"SQL Connection Manager Window AutoRefresh"="Yes"
"Save Layout"="Yes"
"Main Window X"=dword:000000a0
"Main Window Y"=dword:00000060
"Main Window Width"=dword:00000300
"Main Window Height"=dword:00000219
"Show MKDE Resource Usage Window"="No"
"Show MKDE Communication Statistics Window"="No"
"Show MKDE Active Files Window"="No"
"Show MKDE Active Users Window"="No"
"Show SQL Connection Manager Window"="No"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Pervasive System Analyzer]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Pervasive System Analyzer\8.0]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Pervasive System Analyzer\8.6]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Pervasive System Analyzer\8.7]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Pervasive System Analyzer]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Pervasive System Analyzer\InstallInfo]
"InstallDir"="C:\\Program Files\\Common Files\\Pervasive Software Shared\\PSA"
"VersionLevel"="8.7"
"PatchLevel"="3"
"BuildLevel"="014"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Pervasive.SQL NT Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Pervasive.SQL NT Server\InstallInfo]
"InstallDir"="C:\\PVSW"
"SystemDir"="C:\\WINNT\\system32"
"InstallIniName"="PTKSETUP.INI"
"VersionLevel"="8.70"
"PatchLevel"="3"
"BuildLevel"="014"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Temp]
"InstallDir"="C:\\PVSW\\"
"SystemDir"="C:\\WINNT\\system32\\"
"SupportDir"="C:\\DOCUME~1\\smalcolm\\LOCALS~1\\Temp\\1\\{5CA60F17-0BFA-4854-906C-5A6D31B7199A}"
"Engine"="NTSVR"
"SetupDir"="C:\\kjtemp\\Pervasive.SQL_8.6_complete_Windows"
"CommonDir"="C:\\Program Files\\Common Files\\"
"UILevel"="5"
"WindowsDir"="C:\\WINNT\\"
"myarpcomments"=""
"CommonFilesDir"="C:\\Program Files\\Common Files\\"
"ServicesStart"="Automatic"
"StartMenuDir"="C:\\Documents and Settings\\All Users\\Start Menu\\Programs\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Security]
"Wire Encryption"="IF NEEDED"
"Wire Encryption Level"="2"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\SQL Connection Manager]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\SQL Connection Manager\SERVER.INI]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\SQL Connection Manager\SERVER.INI\Processes]
"W3ODBCEI"="2001"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\SQL Connection Manager\SERVER.INI\SQLManager]
"LogEvent"="1"
"MgrPort"="1583"
"MgrSPXPort"="29320"
"MgrMaxConnections"="2001"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\SQL Relational Engine]
"CurrentDateBasedDSTConversion"="NO"

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Utilities Interface]

[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Utilities Interface\Settings]
"Restricted Access On WTS client"=dword:00000000


 
Upvote 0 Downvote
FYI nothing in the windows event viewer application log but informational notices that stop at 2:36 am last night until the restart I had to do.

Also, I lied, the 2nd nic is .248 not .10
I do get this system event on startup:
Event Type: Error
Event Source: Dhcp
Event Category: None
Event ID: 1002
Date: 8/20/2009
Time: 6:35:11 AM
User: N/A
Computer: MAX
Description:
The IP address lease 192.168.100.248 for the Network Card with network address 000E7FB2CB6A has been denied by the DHCP server 192.168.100.2 (The DHCP Server sent a DHCPNACK message).

but it retries automatically and connects just fine. Not sure why my router gives it an issue on first boot... perhaps it's not releasing properly on shutdown?
Anyway, that's just the 2nd nic, which as I said is not usually used by clients. But should I force Pervasive to just use one nic?

Aside from this after reboot, there are no system event errors or warnings or notices for a week (the 13th).
 
Upvote 0 Downvote
Greetings! I would always assign a static IP address to a Pervasive DB server...perhaps this would resolve your issue.

Many thanks!


James Keep, PMP
Crystal Reports(tm) Certified Consultant 8.5 (CRCC)
Authorized Crystal Engineer (ACE)

Member of the Project Management Institute® (PMI – Montreal) (PMBOK® Guide)
Member of Microsoft® Project User Group (MPUG – Montreal)
 
Upvote 0 Downvote
do you mean assign one of the NICs? I have static ip's on both NIC's already, but Pervasive is configured to 0.0.0.0
 
Upvote 0 Downvote
When Pervasive listens on 0.0.0.0, it is listening on all NICs.
I don't see anything in the settings that could cause this.

How long have these crashes been happening (days, weeks, months,etc)?

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Upvote 0 Downvote
about 10 days or so they begun. it seems to happen only when MRP runs, whether from a local client or from a remote client, but not every time. MRP is an application that performs various operations on the data through Btrieve. It's possible to do MRP manually through the client interface to Max, so it's really a scripted series of SQL commands that have windows popping up displaying what it's doing and reporting any errors.
Since it's not every time, for example MRP is set to run 4 times during the work day, it's not anything specific MRP is doing that's causing this.
It feels like it's a simultaneous accessing of the database through multiple sources. For example, we use NetVault 8 to backup our data (pretty much a copy operation of the contents of the server's "E:" drive which contains the data files and ddf's for Max). It's pretty quick, under a half an hour to save it to tape, and it runs at night.
Similarly we have MRP running at night (takes about 15 minutes) and we have reports that are run from CRD (a program scheduling crystal reports).
It seems that something happens at night, as all this week I came in to Max being down and this error to be the cause.
That's not last week -- last week the problem seemed more random, but still somehow connected to MRP, as it happened once or twice a day and MRP was set to run each time.
I've now configured CRD to NOT be running at all when MRP is scheduled, but that hasn't stopped it. Also, the backups are set to run hours after MRP is, so I'm not sure that's the issue.
MRP runs 3am, 9am, noon, and 2pm. The backup for Max runs at 9pm.
We have only one report that runs nightly with CRD, and it takes literally 20 seconds to do so.
CRD runs on a client computer (named deploy) and NetVault server is on a different server (named bebe).

So, I really don't see how all these can conflict at night or why. The backups have been successful, but NetVault wouldn't care about the status of Pervasive since it's just copying files.

Could it be a listening issue? Is having 2 NICs troublesome for pervasive? With only 25 clients, I think one gigabit nic can handle the traffic, and the clients refer to max by netbios name instead of ip. The clients refer to max by the ip of only one nic when they ping Max or use \\max
the 2nd nic we use for servicing etc. I should dedicate reports to use the 2nd nic through odbc referring to an ip address instead of a name when I configure the DSN but I don't.

Why the hell is this happening and how do I stop it? How do I find out more as to why this is happening?
 
Upvote 0 Downvote
Right! What is Max? Is this Maximizer Enterprise? If so, what version are you running?

Thanks!



James Keep, PMP
Crystal Reports(tm) Certified Consultant 8.5 (CRCC)
Authorized Crystal Engineer (ACE)

Member of the Project Management Institute® (PMI – Montreal) (PMBOK® Guide)
Member of Microsoft® Project User Group (MPUG – Montreal)
 
Upvote 0 Downvote
Were there any recent MS patches added to the server this week??

James Keep, PMP
Crystal Reports(tm) Certified Consultant 8.5 (CRCC)
Authorized Crystal Engineer (ACE)

Member of the Project Management Institute® (PMI – Montreal) (PMBOK® Guide)
Member of Microsoft® Project User Group (MPUG – Montreal)
 
Upvote 0 Downvote
No, it's Exact's product (formerly a Macola one) called simply Max.
It's version 3.7 (which is old now, but we don't have the ability to upgrade due to costs).
MS patches, hrm.

Damn it! It just happened again. MRP set to run at 2pm.
ARG!!!
I tried restarting the services and still nothing. Rebooting now, DURING THE WORK DAY.
 
Upvote 0 Downvote
it really seems as if mrp is causing this. I'm not sure it's a nic thing, since this happens even if mrp runs on the local server.
I just don't get it.
I'll report back when it boots up if there's any history of recent patches from MS from the add/remove programs.
 
Upvote 0 Downvote
I can't get back in.
It's finally died and restarting the server isn't helping. There's no more info in any logs, no other error messages to troubleshoot. It simply fails to connect to itself. I cannot even browse the tables in PCC when it goes down like this. When I restart the services it goes back up and it goes back down again. I think there's a rogue system that's corrupting the tables.
 
Upvote 0 Downvote
What error do the Pervasive tools (PCC, Function Executor) return when trying to open the files?
Are NTDBSMGR.EXE and W3DBSMGR.EXE listed in Task Manager (Processes) on the server?

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Upvote 0 Downvote
ok it seems i'm up, but attempting to load the max client on the server takes it down completely and I have to reboot.
 
Upvote 0 Downvote
ok, I cannot open the Max client on the server, nor can I on a critical workstation that runs CRD. Further, I can't run crystal reports that use btrieve either from both machines.
The workstation shows file cannot be opened, while the server shows btrieve error 3012... it's like I don't have the right service pack installed on my server, but I'm sure I do!
It's 8.7 sp3... how do I verify?
 
Upvote 0 Downvote
More oddity, I can run that btrieve report just fine from another workstation!!!!
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

ianbtheog
  • Locked
  • Question
Connection Manager is not running at the specified port number - Pervasive 13.31.014 - Intermittent
Replies
2
Views
545
ianbtheog
ianbtheog
bojimuncher
  • Locked
  • Question
Daily Scheduled Exports or Mirror from Pervasive Server to Different Pervasive Server 1
Replies
2
Views
373
bojimuncher
bojimuncher
mSportsman
  • Locked
  • Question
Trouble with foreign Keys
Replies
0
Views
223
mSportsman
mSportsman
soocallmebrady
  • Locked
  • Question
Pervasive SQL Update with Joins - Error: Unknown table or correlation name
Replies
0
Views
250
soocallmebrady
soocallmebrady
Sladybug
  • Locked
  • Question
Pervasive SQL - Updating database date fields via ODBC with null and '' values
Replies
0
Views
221
Sladybug
Sladybug

Part and Inventory Search

Sponsor

Back
Top