amerretz
asked on
ODBC permissions needed...
Error: Pervasive ODBC engine DSN ... An error occurred while retrieving local database names. Insufficient rights to get or set information.
I get this error when I try to create connector.
I get this error when I try to create connector.
What does your connect string look like?
Which database server you are trying to connect?(SQL ,ORACLE)
Check on server do the user you are using to configure the ODBC have access on the database server or no. should have atlease read access on one database.
Check on server do the user you are using to configure the ODBC have access on the database server or no. should have atlease read access on one database.
It's a Pervasive engine. What OS are you trying this on? Is it Terminal Server?
What version of Pervasive are you using?
Does this user have rights to the DBNAMES.CFG in the "WIndows" directory?
What version of Pervasive are you using?
Does this user have rights to the DBNAMES.CFG in the "WIndows" directory?
If this is trying to attach to a web server with data, you may need to give the IUSR account more access rights on that web server to allow entry from the driver requests.
ASKER
The OS is windows server 2003. It is for a excel sheet on a client computer to read a accounting database on the server.
I have setup the client side on the winXP pro machine but the server is locked down hard with security template.
But the problem I am having is not knowing which files need to have less strick security permission in regards to creating a pervasive/ btreive server DSN ODBC connection for the server side.
I have setup the client side on the winXP pro machine but the server is locked down hard with security template.
But the problem I am having is not knowing which files need to have less strick security permission in regards to creating a pervasive/ btreive server DSN ODBC connection for the server side.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thats whats so strange... I do login as administrator but it displays the error I initally posted. Another network guy setup this server, I guess he must have been studying 70-299.....
I will try what you suggested.
I will try what you suggested.
When you logged in, were you physically at the server or were you creating the DSN/DBN from a Terminal Server session? If it was the TS session, try it physically at the server.
ASKER
Ahhh... I was installing through a TS session but once in I also looped back through the console local on the server. I thought doing this was like being at the physical machine...???
From what I understand, the Pervasive components can't determine the true admin in a TS session. There is a registry key that will allow you to create DSN/DBNs in a session but it opens all of the "administrative" functions (monitor, pcc configuration, etc) to everyone. The registry information is:
ID: psql2646
Unable to use DTI Functionality through a terminal session to a Windows Terminal Server.
Problem Description:
Unable to use DTI Functionality through a terminal session to a Windows Terminal Server.
DTI Functionality includes Pervasive Server Configuration, Creating and Maintaining Engine DSNs and the Pervasive Monitor Utility.
"Unable to save settings values" message may be returned.
Problem Environment:
Pervasive.SQL 2000i Windows NT
Service Pack 4
Microsoft Windows NT Server 4.0
Microsoft Windows 2000
Microsoft Terminal Server
psql2646
Solution:
In order to access DTI functionality through a terminal session, the server must have W3UPI228.DLL or later. Pervasive.SQL 2000i includes W3UPI229.DLL.
In addition, Pervasive.SQL 2000i has an additional registry entry
HKEY_LOCAL_MACHINE\SOFTWAR E\Pervasiv e Software\Utilities Interface\Settings\
The value for Restricted Access On WTS client has a default value of 1 meaning access will be restricted. If the administrator changes this to 0, everyone will be able to run utilities as if they are logged on to the machine physically. This will allow them to remotely administer their P.SQL 2000i server.
It should be noted that changing this value to 0 gives all users full control of the DTI functions on the server.
NOTE:
Editing your registry is dangerous and can disable your operating system causing you to reinstall your software. Pervasive Software will not be responsible for any mishap due to registry changes
This still applies to PSQL v8 and v9.
ID: psql2646
Unable to use DTI Functionality through a terminal session to a Windows Terminal Server.
Problem Description:
Unable to use DTI Functionality through a terminal session to a Windows Terminal Server.
DTI Functionality includes Pervasive Server Configuration, Creating and Maintaining Engine DSNs and the Pervasive Monitor Utility.
"Unable to save settings values" message may be returned.
Problem Environment:
Pervasive.SQL 2000i Windows NT
Service Pack 4
Microsoft Windows NT Server 4.0
Microsoft Windows 2000
Microsoft Terminal Server
psql2646
Solution:
In order to access DTI functionality through a terminal session, the server must have W3UPI228.DLL or later. Pervasive.SQL 2000i includes W3UPI229.DLL.
In addition, Pervasive.SQL 2000i has an additional registry entry
HKEY_LOCAL_MACHINE\SOFTWAR
The value for Restricted Access On WTS client has a default value of 1 meaning access will be restricted. If the administrator changes this to 0, everyone will be able to run utilities as if they are logged on to the machine physically. This will allow them to remotely administer their P.SQL 2000i server.
It should be noted that changing this value to 0 gives all users full control of the DTI functions on the server.
NOTE:
Editing your registry is dangerous and can disable your operating system causing you to reinstall your software. Pervasive Software will not be responsible for any mishap due to registry changes
This still applies to PSQL v8 and v9.
ASKER
I still receive the error when physical trying to create it from the server. Any ideas?
ASKER
I have also looked at that registry key and the dbnames file... they have administrator rights already applied....
ASKER
The issue generally comes up if you have lower versions of MDAC which is not supported on Windows 2003 Server.(MDAC 2.1 or below)
check the instructions to take care of it.
1.Go to the following link and download a utility called Component checker.exe.
http://support.microsoft.com/?kbid=301202
2. Run it on your machine and do an analysis on which version of MDAC you have.
3. Once you find it, you will see the second option to do a comparison for any mismatches.
4. Regardless of whether you find any mismacthes or not, download the latest version of MDAC (MDAC 2.8 SP2).
Get back to us with the result if that doesnt work.
regards,
Lokesh
check the instructions to take care of it.
1.Go to the following link and download a utility called Component checker.exe.
http://support.microsoft.com/?kbid=301202
2. Run it on your machine and do an analysis on which version of MDAC you have.
3. Once you find it, you will see the second option to do a comparison for any mismatches.
4. Regardless of whether you find any mismacthes or not, download the latest version of MDAC (MDAC 2.8 SP2).
Get back to us with the result if that doesnt work.
regards,
Lokesh
ASKER
SOrry for the delayed response, I downloaded and installed the version you specified. This has not solved the problem.
Is there something else to try?
Is there something else to try?
Did the WTS registry key have any effect?
What user is logged in on the server trying to create the DSN/DBN?
DOes that user have "Full Control" to DBNAMES.CFG?
What user is logged in on the server trying to create the DSN/DBN?
DOes that user have "Full Control" to DBNAMES.CFG?
ASKER
Yes the user is part of the administrators group and therefore should have access to all files. I took a look at the registry key and dbnames.cfg file and I have access to both.
Can you open DBNAMES.CFG through the Function Executor (WBEXEC32.EXE) and read the records? You won't be able to update the file but you should be able to read it. You'll need to change the DataBuffer Length to 800 and issue a GetFirst (operation 12) to test reading ability.
ASKER
I can open it up.... I dont know really where to look to change the data buffer ...can u explain please. Also the getfirst.
In the lower right hand corner of the window, you should see an "OpCode" and a "DataLen". See the circled items at: www.mirtheil.com/dbnames.jpg. Change the "OpCode" to 12 and the DataLen to 800. Then press "Execute". If that works, change the OpCode to 6 (Get NExt) and press Execute.
Do you get any errors?
Do you get any errors?
ASKER
No I didnt get any error,... What shall I do now?
ASKER
I still cant configure a current DSN entry...same error
Can you create a Database through the PCC?
Are you in a Terminal Server Session?
Have you tried it physically at the server?
Are you in a Terminal Server Session?
Have you tried it physically at the server?
ASKER
What is PCC?
I am using remote desktop as the problem is for a client of ours.
I have phoned and talked someone through the steps and they experience the problem at the server itself. Not using RDP.
I am using remote desktop as the problem is for a client of ours.
I have phoned and talked someone through the steps and they experience the problem at the server itself. Not using RDP.
PCC is the Pervasive Control Center. It's the "Enterprise Manager" for Pervasive.
If you're still using RDP, did you set the WTS registry key:
HKEY_LOCAL_MACHINE\SOFTWAR E\Pervasiv e Software\Utilities Interface\Settings\
The value for Restricted Access On WTS client has a default value of 1 meaning access will be restricted. If the administrator changes this to 0, everyone will be able to run utilities as if they are logged on to the machine physically. This will allow them to remotely administer their P.SQL 2000i server.
POst the PVSW.LOG (should be in the Windows directory). Let's see if there's anything in that might help.
If you're still using RDP, did you set the WTS registry key:
HKEY_LOCAL_MACHINE\SOFTWAR
The value for Restricted Access On WTS client has a default value of 1 meaning access will be restricted. If the administrator changes this to 0, everyone will be able to run utilities as if they are logged on to the machine physically. This will allow them to remotely administer their P.SQL 2000i server.
POst the PVSW.LOG (should be in the Windows directory). Let's see if there's anything in that might help.
ASKER
Date Time Component Process Process Name Computer Name Type Category Msg ID Message
---------- -------- --------------- -------- --------------- --------------- ---- ---------- -------- -------------------------- ---------- ---------- ---------- ---------- -------
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Balanced Trees.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for File Version.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for System Data.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Max MicroKernel Memory Usage.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Logging.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Cache Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Merge Sort Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Max Communication Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Durability.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Log Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Log File Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Systrans Bundle Limit.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Systrans Time Limit.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Logging.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Background Threads.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Wait-lock Timeout.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Log Directory.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace File.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace Databuf Len.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace Keybuf Len.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace Ops.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for File Growth Factor.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Enable Watchdog.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for System Cache.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Preallocate.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Minimal States.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Minimal States Delay.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Worker Threads.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Max Remote Communications Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Remote Read Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Remote Worker Threads.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Remote Sessions Enabled.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Supported Protocols.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Protocol Init Timeout.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for TCPIP Multi-Homed.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Listen IP Address.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Home Directory.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Enable AutoReconnect.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for AutoReconnect Timeout.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
05-27-2005 09:13:47 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER W Resources allocated
06-04-2005 00:34:13 NTMKDE 00000880 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-04-2005 00:37:29 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-04-2005 04:32:31 NTMKDE 00000820 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-06-2005 08:32:08 NTMKDE 00000820 NTDBSMGR.EXE HORSERVER W Resources allocated
06-08-2005 14:09:28 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-08-2005 14:11:14 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER W Resources allocated
06-08-2005 14:11:20 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HOR\ACCUSER.D AT is rolling back.
06-08-2005 14:11:24 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HOR\ACCMASC.D AT is rolling back.
06-27-2005 09:20:00 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER I Resources released
06-27-2005 09:22:19 NTMKDE 000006AC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-27-2005 09:24:07 NTMKDE 000006AC NTDBSMGR.EXE HORSERVER W Resources allocated
06-27-2005 09:36:49 W3CACHE 000013EC w3dbsmgr.exe HORSERVER I MicroKernel is using default settings.
07-01-2005 12:12:42 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-01-2005 12:23:16 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER W Resources allocated
07-11-2005 16:31:36 W3CACHE 0000193C w3dbsmgr.exe HORSERVER I MicroKernel is using the default setting for Max Pending IO.
07-11-2005 16:31:36 W3CACHE 0000193C w3dbsmgr.exe HORSERVER I MicroKernel is using the default setting for File Growth Factor.
07-11-2005 16:31:36 W3CACHE 0000193C w3dbsmgr.exe HORSERVER I MicroKernel is using the default setting for Enable Watchdog.
07-11-2005 22:57:51 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER I Resources released
07-11-2005 22:59:50 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-12-2005 07:56:37 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER W Resources allocated
07-13-2005 14:25:03 W1MIF145 0000170F EXPORT.EXE HORSERVER W 00000004 3012: Could not locate component: WBTRLOCL.DLL. AIF stat=8013. Binding Rule=lib:///wbtrlocl.dll, CID=@(#);producer=Pervasiv e Software, Inc.;platform=W1;type=MIF; level=1;re vision=45; site=AUS00 1;build=11 4;timestam p=20021122 235605Z;de sc=MKDEID Requester;6b73
07-15-2005 21:18:09 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Resources released
07-15-2005 21:20:13 NTMKDE 000008D8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-16-2005 10:54:33 NTMKDE 000008D8 NTDBSMGR.EXE HORSERVER W Resources allocated
07-28-2005 17:42:56 NTMKDE 000008D8 NTDBSMGR.EXE HORSERVER I Resources released
07-28-2005 17:44:49 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-28-2005 17:52:25 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER W Resources allocated
08-01-2005 10:18:24 NTMKDE 000008B0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
08-01-2005 10:18:24 NTMKDE 000008B0 NTDBSMGR.EXE HORSERVER W Resources allocated
08-31-2005 17:33:42 NTMKDE 000008B0 NTDBSMGR.EXE HORSERVER I Resources released
08-31-2005 17:35:38 NTMKDE 000008BC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
08-31-2005 17:41:53 NTMKDE 000008BC NTDBSMGR.EXE HORSERVER W Resources allocated
09-02-2005 06:11:17 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-02-2005 08:16:43 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER W Resources allocated
09-20-2005 17:25:00 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER I Resources released
09-20-2005 17:26:57 NTMKDE 000008B4 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-20-2005 17:27:15 NTMKDE 000008B4 NTDBSMGR.EXE HORSERVER W Resources allocated
09-20-2005 17:31:36 NTMKDE 000008B4 NTDBSMGR.EXE HORSERVER I Resources released
09-20-2005 17:33:25 NTMKDE 000008F8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-20-2005 17:37:10 NTMKDE 000008F8 NTDBSMGR.EXE HORSERVER W Resources allocated
09-28-2005 09:44:24 NTMKDE 00000868 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-28-2005 09:48:58 NTMKDE 00000868 NTDBSMGR.EXE HORSERVER W Resources allocated
10-05-2005 01:35:42 NTMKDE 00000854 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-05-2005 01:38:18 NTMKDE 00000854 NTDBSMGR.EXE HORSERVER W Resources allocated
10-11-2005 09:20:28 NTMKDE 00000854 NTDBSMGR.EXE HORSERVER I Resources released
10-11-2005 09:22:23 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-11-2005 09:24:10 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER W Resources allocated
10-27-2005 09:15:16 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER I Resources released
10-27-2005 09:17:09 NTMKDE 00000818 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-27-2005 09:19:46 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-27-2005 09:24:01 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER W Resources allocated
10-28-2005 15:48:23 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER I Resources released
10-28-2005 16:00:35 NTMKDE 00000830 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-28-2005 16:00:36 NTMKDE 00000830 NTDBSMGR.EXE HORSERVER W Resources allocated
11-09-2005 16:52:07 NTMKDE 00000830 NTDBSMGR.EXE HORSERVER I Resources released
11-10-2005 08:23:58 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
11-10-2005 08:26:12 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER W Resources allocated
11-17-2005 03:48:47 NTMKDE 000004FC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
11-17-2005 08:31:43 NTMKDE 000004FC NTDBSMGR.EXE HORSERVER W Resources allocated
11-18-2005 17:39:53 NTMKDE 000004FC NTDBSMGR.EXE HORSERVER I Resources released
11-21-2005 08:20:31 NTMKDE 00000888 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
11-21-2005 08:26:09 NTMKDE 00000888 NTDBSMGR.EXE HORSERVER W Resources allocated
12-29-2005 11:53:11 NTMKDE 0000083C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
12-29-2005 11:53:30 NTMKDE 0000083C NTDBSMGR.EXE HORSERVER W Resources allocated
12-29-2005 11:55:58 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
12-29-2005 11:58:22 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER W Resources allocated
01-19-2006 14:38:38 NTMKDE 000006D8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
01-19-2006 14:40:02 NTMKDE 000006D8 NTDBSMGR.EXE HORSERVER W Resources allocated
01-19-2006 14:45:08 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
01-19-2006 15:04:52 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER W Resources allocated
01-27-2006 09:19:44 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
01-27-2006 09:22:14 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER W Resources allocated
02-17-2006 09:03:07 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
02-17-2006 09:41:00 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER W Resources allocated
02-22-2006 09:20:29 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
02-22-2006 09:32:43 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER W Resources allocated
03-01-2006 16:05:30 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-01-2006 16:09:51 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER W Resources allocated
03-09-2006 17:13:50 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Resources released
03-09-2006 17:15:51 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-09-2006 17:16:10 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER W Resources allocated
03-09-2006 17:20:36 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-09-2006 17:32:47 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 13:01:43 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 13:02:02 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 13:04:51 NTMKDE 00000804 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 13:09:31 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 13:17:02 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 13:18:38 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HORNEW\ACCOI. DAT is rolling back.
03-10-2006 15:31:40 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-10-2006 15:34:53 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-10-2006 15:42:00 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-10-2006 15:44:07 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER I Resources released
03-10-2006 15:46:08 NTMKDE 000006E4 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 15:46:13 NTMKDE 000006E4 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 15:50:15 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 15:53:03 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 15:53:56 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 15:56:50 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-10-2006 16:07:33 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-10-2006 16:09:40 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-10-2006 17:15:41 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 08:33:13 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER I Resources released
03-13-2006 08:35:23 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-13-2006 08:36:28 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER W Resources allocated
03-13-2006 08:40:29 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-13-2006 08:43:53 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER W Resources allocated
03-13-2006 08:43:59 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HORNEW\ACCUSE R.DAT is rolling back.
03-13-2006 09:06:21 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 09:08:21 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 09:20:40 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 09:28:42 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HORNEW\ACCBTN 1.004 is rolling back.
03-13-2006 09:28:55 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 09:41:30 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 09:56:07 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI. DAT
03-13-2006 10:19:10 NTMKDE 00000400 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-13-2006 10:25:33 NTMKDE 00000400 NTDBSMGR.EXE HORSERVER W Resources allocated
03-15-2006 03:06:23 NTMKDE 00000400 NTDBSMGR.EXE HORSERVER I Resources released
03-15-2006 03:08:43 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-15-2006 08:29:52 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER W Resources allocated
03-15-2006 17:26:05 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER I Resources released
03-15-2006 17:28:03 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-15-2006 17:28:45 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER W Resources allocated
03-17-2006 08:17:41 W1MIF145 000016BF BTSEARCH.EXE HORSERVER W 00000004 3012: Could not locate component: WBTRLOCL.DLL. AIF stat=8013. Binding Rule=lib:///wbtrlocl.dll, CID=@(#);producer=Pervasiv e Software, Inc.;platform=W1;type=MIF; level=1;re vision=45; site=AUS00 1;build=11 4;timestam p=20021122 235605Z;de sc=MKDEID Requester;6b73
03-20-2006 08:49:54 NTMKDE 000006BC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-20-2006 08:50:04 NTMKDE 000006BC NTDBSMGR.EXE HORSERVER W Resources allocated
03-20-2006 08:54:30 NTMKDE 000004B0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-20-2006 08:54:38 NTMKDE 000004B0 NTDBSMGR.EXE HORSERVER W Resources allocated
---------- -------- --------------- -------- --------------- --------------- ---- ---------- -------- --------------------------
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Balanced Trees.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for File Version.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for System Data.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Max MicroKernel Memory Usage.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Logging.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Cache Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Merge Sort Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Max Communication Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Durability.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Log Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Log File Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Systrans Bundle Limit.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Systrans Time Limit.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Logging.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Background Threads.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Wait-lock Timeout.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Transaction Log Directory.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace File.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace Databuf Len.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace Keybuf Len.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Trace Ops.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for File Growth Factor.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Enable Watchdog.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for System Cache.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Preallocate.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Minimal States.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Minimal States Delay.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Worker Threads.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Max Remote Communications Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Remote Read Buffer Size.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Remote Worker Threads.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Remote Sessions Enabled.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Supported Protocols.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Protocol Init Timeout.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for TCPIP Multi-Homed.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Listen IP Address.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Home Directory.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for Enable AutoReconnect.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I MicroKernel is using the default setting for AutoReconnect Timeout.
05-27-2005 09:13:38 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
05-27-2005 09:13:47 NTMKDE 00001334 NTDBSMGR.EXE HORSERVER W Resources allocated
06-04-2005 00:34:13 NTMKDE 00000880 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-04-2005 00:37:29 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-04-2005 04:32:31 NTMKDE 00000820 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-06-2005 08:32:08 NTMKDE 00000820 NTDBSMGR.EXE HORSERVER W Resources allocated
06-08-2005 14:09:28 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-08-2005 14:11:14 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER W Resources allocated
06-08-2005 14:11:20 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HOR\ACCUSER.D
06-08-2005 14:11:24 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HOR\ACCMASC.D
06-27-2005 09:20:00 NTMKDE 000005D8 NTDBSMGR.EXE HORSERVER I Resources released
06-27-2005 09:22:19 NTMKDE 000006AC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
06-27-2005 09:24:07 NTMKDE 000006AC NTDBSMGR.EXE HORSERVER W Resources allocated
06-27-2005 09:36:49 W3CACHE 000013EC w3dbsmgr.exe HORSERVER I MicroKernel is using default settings.
07-01-2005 12:12:42 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-01-2005 12:23:16 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER W Resources allocated
07-11-2005 16:31:36 W3CACHE 0000193C w3dbsmgr.exe HORSERVER I MicroKernel is using the default setting for Max Pending IO.
07-11-2005 16:31:36 W3CACHE 0000193C w3dbsmgr.exe HORSERVER I MicroKernel is using the default setting for File Growth Factor.
07-11-2005 16:31:36 W3CACHE 0000193C w3dbsmgr.exe HORSERVER I MicroKernel is using the default setting for Enable Watchdog.
07-11-2005 22:57:51 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER I Resources released
07-11-2005 22:59:50 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-12-2005 07:56:37 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER W Resources allocated
07-13-2005 14:25:03 W1MIF145 0000170F EXPORT.EXE HORSERVER W 00000004 3012: Could not locate component: WBTRLOCL.DLL. AIF stat=8013. Binding Rule=lib:///wbtrlocl.dll, CID=@(#);producer=Pervasiv
07-15-2005 21:18:09 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Resources released
07-15-2005 21:20:13 NTMKDE 000008D8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-16-2005 10:54:33 NTMKDE 000008D8 NTDBSMGR.EXE HORSERVER W Resources allocated
07-28-2005 17:42:56 NTMKDE 000008D8 NTDBSMGR.EXE HORSERVER I Resources released
07-28-2005 17:44:49 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
07-28-2005 17:52:25 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER W Resources allocated
08-01-2005 10:18:24 NTMKDE 000008B0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
08-01-2005 10:18:24 NTMKDE 000008B0 NTDBSMGR.EXE HORSERVER W Resources allocated
08-31-2005 17:33:42 NTMKDE 000008B0 NTDBSMGR.EXE HORSERVER I Resources released
08-31-2005 17:35:38 NTMKDE 000008BC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
08-31-2005 17:41:53 NTMKDE 000008BC NTDBSMGR.EXE HORSERVER W Resources allocated
09-02-2005 06:11:17 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-02-2005 08:16:43 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER W Resources allocated
09-20-2005 17:25:00 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER I Resources released
09-20-2005 17:26:57 NTMKDE 000008B4 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-20-2005 17:27:15 NTMKDE 000008B4 NTDBSMGR.EXE HORSERVER W Resources allocated
09-20-2005 17:31:36 NTMKDE 000008B4 NTDBSMGR.EXE HORSERVER I Resources released
09-20-2005 17:33:25 NTMKDE 000008F8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-20-2005 17:37:10 NTMKDE 000008F8 NTDBSMGR.EXE HORSERVER W Resources allocated
09-28-2005 09:44:24 NTMKDE 00000868 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
09-28-2005 09:48:58 NTMKDE 00000868 NTDBSMGR.EXE HORSERVER W Resources allocated
10-05-2005 01:35:42 NTMKDE 00000854 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-05-2005 01:38:18 NTMKDE 00000854 NTDBSMGR.EXE HORSERVER W Resources allocated
10-11-2005 09:20:28 NTMKDE 00000854 NTDBSMGR.EXE HORSERVER I Resources released
10-11-2005 09:22:23 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-11-2005 09:24:10 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER W Resources allocated
10-27-2005 09:15:16 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER I Resources released
10-27-2005 09:17:09 NTMKDE 00000818 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-27-2005 09:19:46 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-27-2005 09:24:01 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER W Resources allocated
10-28-2005 15:48:23 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER I Resources released
10-28-2005 16:00:35 NTMKDE 00000830 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
10-28-2005 16:00:36 NTMKDE 00000830 NTDBSMGR.EXE HORSERVER W Resources allocated
11-09-2005 16:52:07 NTMKDE 00000830 NTDBSMGR.EXE HORSERVER I Resources released
11-10-2005 08:23:58 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
11-10-2005 08:26:12 NTMKDE 00000870 NTDBSMGR.EXE HORSERVER W Resources allocated
11-17-2005 03:48:47 NTMKDE 000004FC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
11-17-2005 08:31:43 NTMKDE 000004FC NTDBSMGR.EXE HORSERVER W Resources allocated
11-18-2005 17:39:53 NTMKDE 000004FC NTDBSMGR.EXE HORSERVER I Resources released
11-21-2005 08:20:31 NTMKDE 00000888 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
11-21-2005 08:26:09 NTMKDE 00000888 NTDBSMGR.EXE HORSERVER W Resources allocated
12-29-2005 11:53:11 NTMKDE 0000083C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
12-29-2005 11:53:30 NTMKDE 0000083C NTDBSMGR.EXE HORSERVER W Resources allocated
12-29-2005 11:55:58 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
12-29-2005 11:58:22 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER W Resources allocated
01-19-2006 14:38:38 NTMKDE 000006D8 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
01-19-2006 14:40:02 NTMKDE 000006D8 NTDBSMGR.EXE HORSERVER W Resources allocated
01-19-2006 14:45:08 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
01-19-2006 15:04:52 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER W Resources allocated
01-27-2006 09:19:44 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
01-27-2006 09:22:14 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER W Resources allocated
02-17-2006 09:03:07 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
02-17-2006 09:41:00 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER W Resources allocated
02-22-2006 09:20:29 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
02-22-2006 09:32:43 NTMKDE 00000874 NTDBSMGR.EXE HORSERVER W Resources allocated
03-01-2006 16:05:30 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-01-2006 16:09:51 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER W Resources allocated
03-09-2006 17:13:50 NTMKDE 000008A0 NTDBSMGR.EXE HORSERVER I Resources released
03-09-2006 17:15:51 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-09-2006 17:16:10 NTMKDE 00000828 NTDBSMGR.EXE HORSERVER W Resources allocated
03-09-2006 17:20:36 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-09-2006 17:32:47 NTMKDE 00000858 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 13:01:43 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 13:02:02 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 13:04:51 NTMKDE 00000804 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 13:09:31 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 13:17:02 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 13:18:38 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 15:31:40 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 15:34:53 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 15:42:00 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 15:44:07 NTMKDE 00000850 NTDBSMGR.EXE HORSERVER I Resources released
03-10-2006 15:46:08 NTMKDE 000006E4 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 15:46:13 NTMKDE 000006E4 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 15:50:15 NTMKDE 00000810 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 15:53:03 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-10-2006 15:53:56 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER W Resources allocated
03-10-2006 15:56:50 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 16:07:33 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 16:09:40 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-10-2006 17:15:41 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 08:33:13 NTMKDE 00000660 NTDBSMGR.EXE HORSERVER I Resources released
03-13-2006 08:35:23 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-13-2006 08:36:28 NTMKDE 00000840 NTDBSMGR.EXE HORSERVER W Resources allocated
03-13-2006 08:40:29 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-13-2006 08:43:53 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER W Resources allocated
03-13-2006 08:43:59 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HORNEW\ACCUSE
03-13-2006 09:06:21 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 09:08:21 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 09:20:40 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 09:28:42 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER W The file E:\HORPASTEL\HORNEW\ACCBTN
03-13-2006 09:28:55 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 09:41:30 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.10.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 09:56:07 NTMKDE 00000814 NTDBSMGR.EXE HORSERVER E System Error: 116.2.0 File: E:\HORPASTEL\HORNEW\ACCOI.
03-13-2006 10:19:10 NTMKDE 00000400 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-13-2006 10:25:33 NTMKDE 00000400 NTDBSMGR.EXE HORSERVER W Resources allocated
03-15-2006 03:06:23 NTMKDE 00000400 NTDBSMGR.EXE HORSERVER I Resources released
03-15-2006 03:08:43 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-15-2006 08:29:52 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER W Resources allocated
03-15-2006 17:26:05 NTMKDE 0000085C NTDBSMGR.EXE HORSERVER I Resources released
03-15-2006 17:28:03 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-15-2006 17:28:45 NTMKDE 0000082C NTDBSMGR.EXE HORSERVER W Resources allocated
03-17-2006 08:17:41 W1MIF145 000016BF BTSEARCH.EXE HORSERVER W 00000004 3012: Could not locate component: WBTRLOCL.DLL. AIF stat=8013. Binding Rule=lib:///wbtrlocl.dll, CID=@(#);producer=Pervasiv
03-20-2006 08:49:54 NTMKDE 000006BC NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-20-2006 08:50:04 NTMKDE 000006BC NTDBSMGR.EXE HORSERVER W Resources allocated
03-20-2006 08:54:30 NTMKDE 000004B0 NTDBSMGR.EXE HORSERVER I Error initializing the SPX protocol. Error code: 6.
03-20-2006 08:54:38 NTMKDE 000004B0 NTDBSMGR.EXE HORSERVER W Resources allocated
Well, there's nothing I can see that would cause the error you see. I do see a couple things that might cause other problems. FOr example, the WBTRLOCL.DLL error could cause problems with 16 bit applications.
That gives me an idea. Check for WBTRV32.DLL and W3BTRV7.DLL. Are there multiple copies of those two files? If there are, remove all of them except the ones in PVSW\BIN.
THe other thing I see in the PVSW.LOG are the system errors. THey could imply a corrupted file. Again, that shouldn't be causing this problem.
That gives me an idea. Check for WBTRV32.DLL and W3BTRV7.DLL. Are there multiple copies of those two files? If there are, remove all of them except the ones in PVSW\BIN.
THe other thing I see in the PVSW.LOG are the system errors. THey could imply a corrupted file. Again, that shouldn't be causing this problem.
ASKER
I am using version 8 ....should I search for W3BTRV8.DLL in that case?
I have a double up of WBTRV32.DLL but its in the C:\PVSW\Bin\btcompat.bck location
Can I leave this one alone?
I have a double up of WBTRV32.DLL but its in the C:\PVSW\Bin\btcompat.bck location
Can I leave this one alone?
No. W3BTRV8.DLL doesn't exist. It's only W3BTRV7.DLL and WBTRV32.DLL.
Yes, you can leave the one in the btcompat.bck directory.
Yes, you can leave the one in the btcompat.bck directory.
ASKER
Any other suggestions?