Receving error as noted in Subject. Running environment is as noted
in knowledgbase response.

Performed recommendation as noted from Pervasive knowledgbase. The
error stopped for the remainder of the day, but has reappeared the
next day. This is a recent problem, application code has been
operational for months w/o any recent modifications. Pervasive
service pack have been install.ed

Other recommendations appreciated.


Solution Details
Solution ID: 00016559

A DOS application which uses the windows dos box returns status 3019.
Problem Description:

A DOS application which uses the windows dos box returns status
3019.
The Function Executor can open the btrieve file successfully.
Status 3019: The MicroKernel router encountered a semaphore error

Problem Environment:Pervasive.SQL 2000i
Service Pack 4

Windows 2000 Server

Cause of this problem:
This situation may happen when old components from Pervasive''s
previous products exist in C:\Winnt\system32 directory or in the
application''s directory.

Solution Notes:

(1) Reproduce the error.

(2) Use SmartScout to check which components are loaded when the
application is run. You can find SmartScout (sscout32.exe) in C:\Pvsw
\Bin directory.

(3) If the components are not from C:\Pvsw\Bin directory, rename
them.

(4) Retry the application.

Are you already running SP4? If so, then try applying the SP4
hotfixes, to see if that helps.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/2007 ***

dstevno (AT) gmail (DOT) com wrote:

Applied the recommended hotfixes (we were running SP4) and the error
once again appeared.

Any other suggestions are welcome.

Thanks

dstevno (AT) gmail (DOT) com wrote:

No other ideas. Upgrading to PSQLv9 may or may not have any impact,
but may be worth a try if an upgrade is in the cards. Alternatively,
you might be able to get some ideas from a network trace (with Sniffer,
WireShark, etc.).

Hi Bill -

These are the messages in the pvsw.log - this is the Dos application
that is executing when the error appears. Search documentation -
nothing apparent.

02-28-2007 08:00:14 W3MIF13B 00000424 w-pap013.EXE ACI-
ISP E 00000233 WaitOnIPCControlSem().
WaitForSingleObject failed. OS rc=128
02-28-2007 08:00:14 W3MIF13B 000001E4 w-pap013.EXE ACI-
ISP E 00000233 WaitOnIPCControlSem().
WaitForSingleObject failed. OS rc=128
02-28-2007 08:00:14 W3MIF13B 00000DB0 w-pap013.EXE ACI-
ISP E 00000233 WaitOnIPCControlSem().
WaitForSingleObject failed. OS rc=128
02-28-2007 08:23:18 W3MIF13B 00000C18 dllhost.exe ACI-
ISP E 00000233 WaitOnIPCControlSem().
WaitForSingleObject failed. OS rc=128

Thanks in advance

dstevno (AT) gmail (DOT) com wrote:

I've got nothing on that error as it pertains to your issue -- only
relating to Terminal Services users continually reconnecting.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/2007 ***