Can you post the last portion (50 lines or so) of the log file?
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - March 2008 ***

guig wrote:


--

Can you post the last portion (50 lines or so) of the log file?
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - March 2008 ***

guig wrote:


--

Can you post the last portion (50 lines or so) of the log file?
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - March 2008 ***

guig wrote:


--

Looks like Normal termination in every case.

The only thing I found in the KB was this:

ID: 00016028 - Status 2 or MKDE Terminated Error
Description: With Btrieve for Windows NT Server Edition v6.15.445, 32
bit Windows application may return a Status 2: "the application
encountered an I/O error" or "MKDE Terminated with Service Specific
Error 0" after running an application for some time.
Environment: Btrieve v6.15 Windows NT Microsoft Windows NT Server 4.0
Cause: This may occur when an application performs a large number of
open and close operations and the service has been running a long time.
The symptom appears when the server runs out of memory.
Solution: A repair has been made to the engine (NTMKDE.EXE) and to the
32 bit interface (WBTRV32.DLL). This corrects the way handles are
allocated and released. This was addressed in the 6.15.451 patch. Click
here to download the patch.

Obviously, though, you already have the 6.15.451 patch applied.


May not be any solution outside of upgrading...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***


guig wrote:



--

Looks like Normal termination in every case.

The only thing I found in the KB was this:

ID: 00016028 - Status 2 or MKDE Terminated Error
Description: With Btrieve for Windows NT Server Edition v6.15.445, 32
bit Windows application may return a Status 2: "the application
encountered an I/O error" or "MKDE Terminated with Service Specific
Error 0" after running an application for some time.
Environment: Btrieve v6.15 Windows NT Microsoft Windows NT Server 4.0
Cause: This may occur when an application performs a large number of
open and close operations and the service has been running a long time.
The symptom appears when the server runs out of memory.
Solution: A repair has been made to the engine (NTMKDE.EXE) and to the
32 bit interface (WBTRV32.DLL). This corrects the way handles are
allocated and released. This was addressed in the 6.15.451 patch. Click
here to download the patch.

Obviously, though, you already have the 6.15.451 patch applied.


May not be any solution outside of upgrading...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***


guig wrote:



--

Looks like Normal termination in every case.

The only thing I found in the KB was this:

ID: 00016028 - Status 2 or MKDE Terminated Error
Description: With Btrieve for Windows NT Server Edition v6.15.445, 32
bit Windows application may return a Status 2: "the application
encountered an I/O error" or "MKDE Terminated with Service Specific
Error 0" after running an application for some time.
Environment: Btrieve v6.15 Windows NT Microsoft Windows NT Server 4.0
Cause: This may occur when an application performs a large number of
open and close operations and the service has been running a long time.
The symptom appears when the server runs out of memory.
Solution: A repair has been made to the engine (NTMKDE.EXE) and to the
32 bit interface (WBTRV32.DLL). This corrects the way handles are
allocated and released. This was addressed in the 6.15.451 patch. Click
here to download the patch.

Obviously, though, you already have the 6.15.451 patch applied.


May not be any solution outside of upgrading...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***


guig wrote:



--

You posted a logfile from the Btrieve 6.15 Server Engine, so I was
assuming that you are using THAT engine. However, you then post the
BTI.INI file? The INI file has no link to the server engine at all.


If you are using a Win16 application, then you need to have the right
Btrieve 16-bit components, namely WBTRCALL.DLL, WBTRVRES.DLL, and
WBTICOMM.DLL. However, this is NOT the preferred setup, since it keeps
you in the 16-bit world, and problems can easily occur.

You may be better off using the 32-bit requesters, by changing to
"Thunk=Yes" and making sure that you ALSO have WBTRTHNK.DLL,
WBTRV32.DLL, and W32BTICM.DLL.

However, none of this has any impact on the database server engine,
which is what you say is crashing out, right? Or were your original
error messages indicating some other engine? I recall that the log
file you posted was not showing any evidence of crashing, so now I am
not sure which engine you are trying to run...
BB


guig wrote:



--

You posted a logfile from the Btrieve 6.15 Server Engine, so I was
assuming that you are using THAT engine. However, you then post the
BTI.INI file? The INI file has no link to the server engine at all.


If you are using a Win16 application, then you need to have the right
Btrieve 16-bit components, namely WBTRCALL.DLL, WBTRVRES.DLL, and
WBTICOMM.DLL. However, this is NOT the preferred setup, since it keeps
you in the 16-bit world, and problems can easily occur.

You may be better off using the 32-bit requesters, by changing to
"Thunk=Yes" and making sure that you ALSO have WBTRTHNK.DLL,
WBTRV32.DLL, and W32BTICM.DLL.

However, none of this has any impact on the database server engine,
which is what you say is crashing out, right? Or were your original
error messages indicating some other engine? I recall that the log
file you posted was not showing any evidence of crashing, so now I am
not sure which engine you are trying to run...
BB


guig wrote:



--

You posted a logfile from the Btrieve 6.15 Server Engine, so I was
assuming that you are using THAT engine. However, you then post the
BTI.INI file? The INI file has no link to the server engine at all.


If you are using a Win16 application, then you need to have the right
Btrieve 16-bit components, namely WBTRCALL.DLL, WBTRVRES.DLL, and
WBTICOMM.DLL. However, this is NOT the preferred setup, since it keeps
you in the 16-bit world, and problems can easily occur.

You may be better off using the 32-bit requesters, by changing to
"Thunk=Yes" and making sure that you ALSO have WBTRTHNK.DLL,
WBTRV32.DLL, and W32BTICM.DLL.

However, none of this has any impact on the database server engine,
which is what you say is crashing out, right? Or were your original
error messages indicating some other engine? I recall that the log
file you posted was not showing any evidence of crashing, so now I am
not sure which engine you are trying to run...
BB


guig wrote:



--