hello,
I started working at a place that uses pervasive 2000i on win2k server.
The database is for an accounting app. called AMSI.

It's getting odd errors (error 3119, 98 and now 88-Mode error, file
opened elsewhere in different mode. Operation code = 0)

So, from previous experience, I started looking at whether or not the
database has been tuned for this server. I've found that lots of
times, the database is not tuned for the server it's running at - they
just leave it at default settings.

I'm not very familiar with pervasive. Can an experienced person please
review these files and make some suggestions as to improving the
database config? The server has 1GB of RAM, P4 2.4GHZ CPU. Another
database (foxpro) is also running on it. The foxpro gets about 10
people connecting to it, the pervasive has 5 at the most.
It's for a small business, they also have the server running file/print
sharing and Active Directory. (I know you shouldn't run all these
things on one box, but that's what this company has...) The server
only runs TCP/IP.

Also, how do you rebuild the indexes on this database? I know this can
also help - probably never done on this server.

Thank you,

Oskar


[Btrieve Requester]
Splash Screen=Yes
Embedded Spaces=no
chkparms=no
[InstallInfo]
InstallDir=C:\PVSW
SystemDir=C:\WINNT\system32
InstallIniName=PTKSETUP.INI
VersionLevel=7.90
PatchLevel=3
BuildLevel=230
[btrieve Client]
trnfile=C:\Program Files\Common Files\Macola Shared
[Scalable SQL Engine]
external sort path=C:\Program Files\Common Files\Macola Shared
[Btrieve]
Local=NO
Requester=NO
Thunk=YES
[Scalable SQL]
Local=YES
Requester=NO
[Microkernel Router]
Local=yes
Requester=yes
Thunk=yes
Use IDS=yes
[Communications Requester]
TCP connect timeout=15
Supported protocols=SPX,TCPIP,MS_SPX
Runtime server=Yes
[Rebuild]
Save Settings=Yes
Continue On Error=No
Page Size=EXISTING
System Data=SYSTEM_DATA_NO
Key Number=NONE
Output Directory=
Status File Path=C:\PVSW\BIN\rebuild.log

************************************************** *********************************

Date Time Component Process Process Name Computer
Name Type Category Msg ID Message
---------- -------- --------------- -------- ---------------
--------------- ---- ---------- --------
-------------------------------------------------------------------------
11-29-2003 09:37:22 NTMKDE 00000634 NTDBSMGR.EXE KMPSERVER
I MicroKernel is using default settings.
11-29-2003 09:37:22 W3COMSRV 00000634 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
11-29-2003 09:37:22 NTMKDE 00000634 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
11-29-2003 09:37:33 NTMKDE 00000634 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-29-2003 09:38:07 NTMKDE 00000634 NTDBSMGR.EXE KMPSERVER
I Resources released
11-29-2003 09:39:52 W3COMSRV 000003C8 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
11-29-2003 09:39:52 NTMKDE 000003C8 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
11-29-2003 09:44:47 NTMKDE 000003C8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-29-2003 09:45:18 NTMKDE 000003C8 NTDBSMGR.EXE KMPSERVER
I Resources released
11-29-2003 09:45:29 NTMKDE 000003C8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-29-2003 09:46:08 NTMKDE
09-25-2005 13:41:15 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
09-27-2005 09:20:34 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
09-28-2005 11:08:19 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
09-28-2005 11:13:31 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
09-29-2005 18:43:40 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
09-30-2005 09:20:10 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
09-30-2005 09:22:35 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
09-30-2005 10:17:18 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
09-30-2005 10:24:53 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
09-30-2005 10:58:20 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
09-30-2005 19:17:57 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-03-2005 09:47:01 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-03-2005 17:16:59 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-04-2005 09:06:00 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-04-2005 17:05:02 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-05-2005 09:50:54 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-05-2005 17:40:46 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-06-2005 09:41:29 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-06-2005 17:10:51 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-07-2005 09:56:51 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-07-2005 17:24:09 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-10-2005 10:17:27 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-10-2005 17:32:21 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-11-2005 08:28:19 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-11-2005 17:28:15 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-12-2005 08:38:49 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-12-2005 11:25:40 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-12-2005 13:09:37 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-12-2005 17:15:31 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-13-2005 08:07:54 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-13-2005 08:08:37 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-13-2005 09:45:15 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-13-2005 15:54:46 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-14-2005 09:44:21 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-14-2005 17:10:34 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-17-2005 09:22:10 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-17-2005 17:41:11 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-18-2005 08:38:36 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-18-2005 11:00:53 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-18-2005 13:50:49 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-18-2005 14:11:35 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-18-2005 14:19:04 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-18-2005 17:16:07 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-19-2005 08:50:27 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-20-2005 08:39:16 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-20-2005 10:33:13 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-20-2005 16:19:39 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-20-2005 16:39:25 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-20-2005 16:55:39 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-21-2005 09:59:00 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-21-2005 11:46:43 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-21-2005 12:01:01 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-21-2005 15:57:09 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-21-2005 16:45:13 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-21-2005 16:50:01 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-24-2005 09:21:32 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-25-2005 08:29:34 NTMKDE 000006C0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-25-2005 08:43:36 ECAS_API 00000CD0 2\odbcad32.exe" KMPSERVER
E ECASAPI (1.12.1.4083): Error 8505 - An
initialization error occurred when trying to establish a session with
the WSE
10-25-2005 08:43:36 ECAS_API 00000CD0 2\odbcad32.exe" KMPSERVER
E ECASAPI (1.1.1.4083): Error 8517 - An
error occurred when closing the session with the WSE
10-25-2005 10:47:15 W3COMSRV 00000DF0 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
10-25-2005 10:47:15 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
10-25-2005 10:47:39 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-26-2005 17:07:37 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-27-2005 08:33:57 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-27-2005 08:36:58 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-27-2005 14:01:32 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-31-2005 08:29:28 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-31-2005 10:32:25 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-31-2005 10:50:57 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
10-31-2005 11:13:10 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
10-31-2005 16:08:14 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-01-2005 09:13:42 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-01-2005 17:16:25 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-02-2005 11:44:58 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-02-2005 17:03:02 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-03-2005 08:50:43 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-03-2005 17:55:58 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-04-2005 08:12:34 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-07-2005 08:28:44 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-07-2005 08:35:20 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-07-2005 13:05:48 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-07-2005 13:10:16 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-08-2005 17:50:57 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-09-2005 09:36:13 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-09-2005 09:54:48 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-09-2005 10:05:58 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-09-2005 16:49:12 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-10-2005 08:56:39 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-10-2005 14:05:00 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-10-2005 14:29:45 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-10-2005 17:38:41 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-11-2005 10:06:07 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-11-2005 14:42:53 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-11-2005 15:49:56 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-14-2005 08:47:52 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-14-2005 08:50:13 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-15-2005 17:09:42 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-16-2005 09:32:19 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-16-2005 10:06:53 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-16-2005 10:15:00 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-16-2005 11:59:21 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-16-2005 12:26:50 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-16-2005 16:54:37 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-17-2005 09:00:36 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-17-2005 17:17:39 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-18-2005 09:50:48 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-18-2005 15:36:58 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-21-2005 10:04:26 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-21-2005 17:07:32 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-22-2005 08:58:55 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-22-2005 16:58:20 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-23-2005 10:40:00 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-23-2005 12:02:12 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-29-2005 11:41:17 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-30-2005 16:59:10 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
11-30-2005 17:57:25 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
11-30-2005 18:06:08 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-01-2005 10:06:16 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-01-2005 10:30:01 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-01-2005 13:02:46 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-01-2005 17:53:54 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-02-2005 08:36:47 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-05-2005 09:56:08 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-05-2005 14:41:54 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-06-2005 08:21:37 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-06-2005 09:45:41 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-06-2005 09:52:47 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-06-2005 09:56:22 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-06-2005 17:01:10 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-07-2005 08:45:49 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-07-2005 08:59:37 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-07-2005 13:06:44 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-07-2005 17:27:44 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-08-2005 08:54:33 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-08-2005 17:45:27 NTMKDE 00000DF0 NTDBSMGR.EXE KMPSERVER
I Resources released
12-09-2005 03:21:47 NTSRDE 00000E94 N\W3SQLMGR.EXE" KMPSERVER
E NTSRDE.EXE failed to load. RC = 4083.
12-09-2005 03:26:19 W3COMSRV 00000688 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-09-2005 03:26:19 NTMKDE 00000688 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-09-2005 04:22:44 W3COMSRV 000006A8 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-09-2005 04:22:44 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-09-2005 10:07:52 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-12-2005 18:01:22 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-13-2005 08:49:15 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-13-2005 08:53:18 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-13-2005 08:55:52 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-13-2005 10:23:54 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-13-2005 10:25:40 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-13-2005 11:59:29 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-13-2005 13:23:37 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-13-2005 17:53:22 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-14-2005 09:15:10 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-14-2005 15:16:52 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-14-2005 16:00:10 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-14-2005 17:47:23 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-14-2005 18:00:38 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-14-2005 18:21:40 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-15-2005 09:27:41 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-15-2005 18:03:25 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-16-2005 08:54:57 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-16-2005 09:26:29 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-16-2005 11:30:11 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-16-2005 11:50:51 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-16-2005 15:49:46 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-16-2005 17:12:14 NTMKDE 000006A8 NTDBSMGR.EXE KMPSERVER
I Resources released
12-16-2005 18:54:44 W3COMSRV 0000068C NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-16-2005 18:54:44 NTMKDE 0000068C NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-19-2005 10:14:04 W3COMSRV 00000648 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-19-2005 10:14:04 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-19-2005 10:18:17 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-20-2005 18:11:27 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-21-2005 10:42:55 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-21-2005 17:06:02 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-22-2005 09:03:27 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-22-2005 09:25:24 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-22-2005 09:36:42 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-22-2005 11:24:57 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-22-2005 12:13:57 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-22-2005 12:14:39 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-22-2005 12:15:32 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-22-2005 12:18:34 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-23-2005 10:01:15 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-23-2005 14:30:36 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources released
12-27-2005 09:42:57 NTMKDE 00000648 NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-27-2005 12:52:17 W3COMSRV 0000069C NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-27-2005 12:52:17 NTMKDE 0000069C NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-27-2005 13:23:46 W3COMSRV 000006DC NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-27-2005 13:23:46 NTMKDE 000006DC NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-27-2005 13:32:50 W3COMSRV 000006BC NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
12-27-2005 13:32:50 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
12-27-2005 14:05:00 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-27-2005 14:53:24 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
12-28-2005 10:12:42 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-28-2005 17:06:02 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
12-29-2005 08:38:12 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-29-2005 14:24:24 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
12-30-2005 08:59:42 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
12-30-2005 13:08:40 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-03-2006 09:12:21 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-03-2006 09:16:02 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-03-2006 09:29:29 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-03-2006 16:11:59 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-04-2006 11:25:58 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-04-2006 11:27:34 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-04-2006 13:35:58 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-04-2006 17:35:44 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-04-2006 18:08:45 W3COMSRV 000006C4 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-04-2006 18:08:45 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-05-2006 10:03:39 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-05-2006 17:32:46 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-06-2006 13:55:56 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-06-2006 17:50:30 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-07-2006 17:20:59 W3COMSRV 000006BC NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-07-2006 17:20:59 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-09-2006 09:06:45 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-09-2006 17:33:48 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-10-2006 09:57:11 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-11-2006 04:16:59 NTMKDE 000006BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-11-2006 04:21:27 W3COMSRV 000006C4 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-11-2006 04:21:27 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-11-2006 09:41:27 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-11-2006 09:42:03 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-11-2006 09:54:10 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-11-2006 15:03:18 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-11-2006 15:11:47 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-11-2006 19:58:53 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 11:45:07 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 11:47:16 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 11:58:42 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 11:59:36 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 14:43:41 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 17:12:43 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 17:15:28 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 17:16:03 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 17:16:34 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 17:17:41 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 18:02:58 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 18:15:44 NTMKDE 000006C4 NTDBSMGR.EXE KMPSERVER
I Resources released
01-12-2006 18:25:41 W3COMSRV 000006D8 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-12-2006 18:25:41 NTMKDE 000006D8 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-12-2006 18:32:11 NTMKDE 000006D8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-12-2006 18:39:47 NTMKDE 000006D8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-13-2006 10:15:13 NTMKDE 000006D8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-13-2006 14:37:12 NTMKDE 000006D8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-13-2006 15:04:48 W3COMSRV 000009BC NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-13-2006 15:04:48 NTMKDE 000009BC NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-13-2006 15:19:35 NTMKDE 000009BC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-13-2006 17:59:09 NTMKDE 000009BC NTDBSMGR.EXE KMPSERVER
I Resources released
01-13-2006 18:05:13 W3COMSRV 0000052C NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-13-2006 18:05:13 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-13-2006 18:06:12 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-13-2006 18:08:27 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources released
01-13-2006 19:00:12 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-13-2006 19:53:00 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources released
01-16-2006 08:59:25 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-16-2006 09:00:17 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources released
01-16-2006 09:06:19 NTMKDE 0000052C NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-16-2006 09:25:56 W3COMSRV 000006E8 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-16-2006 09:25:56 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-16-2006 13:00:20 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-16-2006 17:06:52 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-16-2006 18:47:42 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-16-2006 18:49:11 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-17-2006 08:52:11 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-17-2006 08:58:58 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-17-2006 08:59:30 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-17-2006 11:43:59 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-17-2006 14:41:30 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-17-2006 16:30:32 W3COMSRV 000006EC NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-17-2006 16:30:32 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-17-2006 16:43:01 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-17-2006 16:47:36 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-17-2006 16:49:30 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-17-2006 16:51:17 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-17-2006 16:53:07 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-17-2006 16:53:53 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 09:22:14 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 09:25:12 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 09:52:12 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 09:56:41 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 10:23:34 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 10:24:23 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 10:25:49 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 10:27:02 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 10:40:26 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 10:50:36 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 11:25:29 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 11:26:03 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 13:36:38 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 14:22:13 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 15:02:24 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 15:45:52 NTMKDE 000006EC NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 15:50:44 NTSRDE 00000684 N\W3SQLMGR.EXE" KMPSERVER
E NTSRDE.EXE failed to load. RC = 10.
01-18-2006 15:55:34 W3COMSRV 000006E8 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-18-2006 15:55:34 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-18-2006 15:55:51 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 16:40:48 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 16:41:57 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 19:10:04 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-18-2006 19:25:16 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-18-2006 19:25:51 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-19-2006 08:41:24 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-19-2006 08:42:29 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-19-2006 08:42:29 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-19-2006 10:05:44 NTMKDE 000006E8 NTDBSMGR.EXE KMPSERVER
I Resources released
01-19-2006 10:10:22 W3COMSRV 000006D0 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-19-2006 10:10:22 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-19-2006 10:21:40 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-19-2006 14:10:03 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-20-2006 08:27:02 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-20-2006 16:02:37 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-20-2006 16:03:41 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-20-2006 16:04:22 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-20-2006 16:08:33 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-20-2006 16:09:08 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-20-2006 16:19:31 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-20-2006 16:20:05 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-23-2006 09:34:59 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-23-2006 13:07:43 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-23-2006 13:23:50 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-23-2006 13:24:27 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-23-2006 14:02:55 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-23-2006 14:03:31 NTMKDE 000006D0 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 09:34:51 W3COMSRV 0000120C NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-24-2006 09:34:51 NTMKDE 0000120C NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-24-2006 09:35:07 NTMKDE 0000120C NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 09:35:43 NTMKDE 0000120C NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 09:35:54 NTMKDE 0000120C NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 10:09:01 W3COMSRV 00000608 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-24-2006 10:09:01 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-24-2006 10:31:08 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 13:02:49 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 13:05:57 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 13:07:17 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 13:36:58 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 13:38:14 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 13:53:00 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 13:53:56 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 14:27:16 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 14:27:56 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 14:32:29 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources allocated
01-24-2006 14:33:14 NTMKDE 00000608 NTDBSMGR.EXE KMPSERVER
I Resources released
01-24-2006 21:46:23 NTBTRV 00000380 BIN\NTBTRV.EXE" KMPSERVER
E NTBTRV.EXE failed to load. RC = 10.
01-24-2006 21:51:14 W3COMSRV 00000618 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-24-2006 21:51:14 NTMKDE 00000618 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-25-2006 09:01:02 W3COMSRV 00000610 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-25-2006 09:01:02 NTMKDE 00000610 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-25-2006 09:41:35 W3COMSRV 0000060C NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-25-2006 09:41:35 NTMKDE 0000060C NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
01-31-2006 21:19:14 W3COMSRV 000005DC NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
01-31-2006 21:19:15 NTMKDE 000005DC NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
02-01-2006 08:25:52 W3COMSRV 00000624 NTDBSMGR.EXE KMPSERVER
E WinSock socket() error=10047.
02-01-2006 08:25:52 NTMKDE 00000624 NTDBSMGR.EXE KMPSERVER
I Error initializing the SPX protocol.
Error code: 11.
02-01-2006 21:11:21 NTMKDE 00000624 NTDBSMGR.EXE KMPSERVER
I Resources allocated
02-01-2006 21:15:56 NTMKDE 00000624 NTDBSMGR.EXE KMPSERVER
I Resources released

There isn't much of value in the Event log -- you are getting some
10047 errors, which Microsoft defines as:
10047 WSAEAFNOSUPPORT Address family not supported by protocol family
This can be caused by the NIC on the server going to sleep.


A much more likely issue is that the config is not up to snuff, as you
suspected. It would be helpful if you could post the configuration
data from the PCC on the server.

It is also very likely that you are simply getting conflicts between
multiple database engines. The data in the BTI.INI file that you
submitted indicates that a very old version of Macola was on this box
-- one that came with a Btrieve 6.15 Workstation Engine. It may be as
simple as some workstations finding an old 6.x engine instead of using
the new one. Scour your systems (including the server) for the files
WBTR32.EXE or W32MKDE.EXE -- the old 6.x engines -- and rename them
where you find them. This will help ensure that all files are opened
with the server engine.


Your other problem may be within the Windows Named Pipes calls,
resulting in the Status 3119. While there are several causes for this,
one of the bigger one is due to bugs in the engine. Please be sure
that you have patched the server to Pervasive.SQL 2000i Service Pack 4
AND the SP4 HotFixes. Then, assuming the clients arer all SP3 already,
update them with the Client HotFixes as well. This may help.

Other issues could be related to anti-virus software (an old version of
McAfee used to cause 3119's) and similar problems.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Sydney: Pervasive.SQL Service & Support Class - 02/27/06 ***
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***

h0u wrote:

Thank you for the reply,
How can I get an output list of all the settings in the control center?
I'd have to write a lot of things down here to get all the settings.
I see where it's looking for multiple protocols (ipx, ms_spx and
tcp/ip). They only use tcp/ip. I assume it would be safe to have only
tcp/ip as the protocol. Would you agree?

Also, is there a text config file for all the stuff in control center?
I guess I'm biased to text config files instead of GUI-based stuff.
Tomorrow I'll look for the 2 files you pointed out.

One other thing, this was working fine for a while. But lately, the
windows server seems to be going downhill (it's getting corrupt). In
your experience, how does this affect pervasive?
The accountant (using the AMSI software) had done closes for 2005 and
they were fine. But around the 19 or 20 of January, there was a hard
server crash. After that, she can't get into the 2005 closes anymore
and all these problems started happening. AMSI uses pervasive as its
database.
I called AMSI and they said they have nothing to do with this problem -
the problem is the database! I'll make sure to remember to never
recommend that vendor! Every other vendor I've worked with supports
their application and the database they chose to write their
application to!


This only proves my opinion that for running anything important, it
should NOT be run on windows. I'm sure you've seen corporate
datacenters. Almost all the ones I've worked at use unix (now linux)
or novell to run anything important. Whatever is left over (that isn't
too important) can run on windows. This case is a text-book example.

Thank you,

Oskar


Bill Bach wrote:

There is an easy way to capture most of the settings.
Most are stored in the registry under HKLM\Software\Pervasive Software
Just dump the registry key. If you do not feel comfortable in the
registry yourself there is a little utility that captures that
information plus quite a bit of other Pervasive centric information.

http://www.pervasive.com/ComponentZo...+%2F+Utilities
The utility in question is "ToolBox - WGE as an NT Service".
It works best when run from the \pvsw\bin folder. It also captures
the most usable information when you have the error message on the
screen before you run it.
Under the "File" menu select "Save Full Report"

More information about the 3119 is in the manual.
http://www.pervasive.com/library
For 3119 specifically the link is here.
http://www.pervasive.com/library/doc..._msg-2-11.html

If you are in a windows environment Bill is correct that the most
likely cause is the Named Pipe failing.

Leonard

On 2 Feb 2006 18:41:15 -0800, "h0u" <pheonix1t (AT) gmail (DOT) com> wrote:

I agree with only having TCP -- this is by far the most preferred
protocol, especially for Windows.

See Leonard's post for the config options.

If the server is mangling itself, then ANYTHING running on the server
can get corrupted -- DLL's, EXE's, databases, Word Docs, etc. If the
server is unstable, it should be replaced as soon as possible.
Continuing to run will be like building your house on sand -- it may
work fine for a while, but one strong wind and it will collapse quickly.

As for AMSI support policy, this is quite unfortunate, as most vendors
that I work with will support the database AND the application.
However, some have chosen to distance themselves, because of limited
time or limited skill set -- there is a reason why companies such as
ours (providing support for JUST the database, regardless of the
application) exist and thrive. Perhaps they are just too busy to get
involved with something that will be a protracted error. Of course,
this is only an explanation -- not an excuse, especially for a company
that sells their application to people for use in critical services.

As for Windows vs. Linux/NetWare, I can agree, but I also see MANY
sites running Windows nowadays, and most successfully. I also worked
with a company in Australia recently that had a physical problem on
their NetWare server -- and it caused major file corruption in numerous
files. Bad hardware will mangle the data on any OS. It's just a mater
of using the best tool for the job.


On your original post, you also asked about rebuilding indices. This
is NOT required from Pervasive, but you can do so if you wish. Use the
Rebuild Utility (if the files are NOT damaged), or the BUTIL Recover
process (if they are damaged). For instructions on BUTIL, see our
white papers at www.goldstarsoftware.com/press.asp for the one on File
Maintenance and another on using Rebuild.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Sydney: Pervasive.SQL Service & Support Class - 02/27/06 ***
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***

h0u wrote: