[ArunaPBSS]

Hi,

We are running a Pastel Partner and each and every day we are en counting the following error ( This was in the PVSW.LOG)

08-10-2008 14:11:48 ECAS_API 00000D4C ptksetup.ini PO E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-10-2008 14:12:18 ECAS_API 000002D4 W3DBSMGR.EXE PO E W3DBSMGR (3.1.1.10): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-10-2008 14:12:41 ECAS_API 00000D4C ptksetup.ini PO E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-10-2008 14:13:11 ECAS_API 00000798 W3DBSMGR.EXE PO E W3DBSMGR (3.1.1.10): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-10-2008 14:40:42 ECAS_API 00000950 Partner2007.exe PO E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-10-2008 14:41:12 ECAS_API 000001DC W3DBSMGR.EXE PO E W3DBSMGR (3.1.1.10): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-10-2008 14:42:17 ECAS_API 00000F28 Partner2007.exe PO E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-10-2008 14:42:19 MKDE 00000814 W3DBSMGR.EXE PO W Resources allocated
08-10-2008 14:42:52 MKDE 00000814 W3DBSMGR.EXE PO I Resources released


And after that database get unusable and has to use DDF builder to rebuild this .This commonly claims as network error but we hardly find any evidence for treat this as a network error.

Any one of you have aver come across this error and what was the resolution.


Please advice,
Regards,

[mirtheil]

08-10-2008 14:11:48 ECAS_API 00000D4C ptksetup.ini PO E ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
08-10-2008 14:12:18 ECAS_API 000002D4 W3DBSMGR.EXE PO E W3DBSMGR (3.1.1.10): Error 8517 - An error occurred when closing the session with the Workgroup engine

The above "errors" aren't usually critical. They occur when a client/server application tries to connect to the local engine and the local engine doesn't exist. The best solution would be to disable the local engine. In the PCC, click the "Configure Microkernel Router" and then unselect the "Use Local Microkernel Engine" in the Access section.

[ArunaPBSS]

Mirtheil Thank you for your prompt reply.

My worry is everyday the Appliation returns the following error :

STATUS 46 (Access to File Denied)
File 31
Opcode 2 (Insert)

After this error appeared some of the functions in the system are unusable and when we check the pvsw.log earlier error as well as the following error( in some workstations) appears.

08-12-2008 12:40:35 ECAS_API 00000AFC fg -showsplash OUTP E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-12-2008 12:40:35 ECAS_API 00000AFC javaw.exe OUTP E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine
08-12-2008 12:40:35 ECAS_API 00000AFC fg -showsplash OUTP E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the Workgroup engine
08-12-2008 12:40:35 ECAS_API 00000AFC javaw.exe OUTP E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the Workgroup engine



So every time we have to do a rebuild using DDF builder for that perticular file.

This is being a major problem to the us sine we have to stop the work for couple of hours every day ( sometimes ouple of times for a day) . Is there any thing we can do from the network ( hardware ) perspective.

we are running 24/7 operation and this is a major problem we are facing.

Please advice.

thanks best regards,

Aruna

[mirtheil]

- What exactly does this "rebuild using DDF Builder" entail?
- Are you excluding the data files (and DDFs) from anti-virus/anti-spyware programs? I've seen error 46 when an AV scans the file and the engine tries to write to it.
Again, the ECAS_API (Error 8505/8517) are not an issue unless you're trying to use a workgroup engine. Change the setting I suggested in my first posting and see if it's fixed.