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 cra****ng 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 cra****ng, so now I am
not sure which engine you are trying to run...
BB
guig wrote:
> On 2008-04-03 13:12:09 +0100, "Bill Bach" <goldstar@[EMAIL PROTECTED]
>
> said:
>
> > 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.
> >
>
>
> Hi Bill,
>
> this is the INI file we are using. The bizarre thing is that the
> physical server we had this setup running on prior to virtualisation
> worked perfectly without these errors.
>
> ;*********************************************************************
> ******* ; Copyright (c) Btrieve Technologies,Inc. 1982-1995. All
> rights reserved. ;
> ; Btrieve Technologies Inc. product initialization file for MS
> Windows
> ;*********************************************************************
> *******
>
> [Btrieve]
> Tasks=30
> Local=No
> Requester=Yes
> Thunk=No
> Verbose=0
> Chkparms=No
>
> [Btrieve Client]
> Options=/f:20 /h:60 /l:20 /t:15 /m:512 /u:0
> Trnfile=C:\WINNT
> Desktopicon=No
> SharingOnLocalFiles=SingleEngine
> SharingOnRemoteFiles=MultiEngine
> EnableSharingBias=Yes
> Tracefile=
> DeleteLockFile=Yes
>
> [Btrieve Requester]
> Runtime Server Sup****t=yes
> Datalength=4096
>
> [wbroll]
> Datalength=4
> Exclusive=No
> Outputmode=ASCII
> Listverbose=No
> Datalist=0
> Keylist=0
>
> [Database Names]
> DBNamesDirectory=
>
--
|
