Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

status 3012 and diagnostics

77 views
Skip to first unread message

David Flaschen

unread,
Jun 2, 2002, 8:56:26 PM6/2/02
to
Is there any way to find out WHY I am getting an error 3012. I have
an installation that is running Btrieve 7.1 without any problems using
a non-local database. I now want this installation to be able to also
access a local database. I have simulated (or at least tried to
simulate) their environment on my own computer. I have no problem. I
added the following 5 files and became able to access local files.
WBTRLOCL.DLL
W3MKDE.DLL
W3MKDERC.DLL
W3DBSMGR.EXE
W3DBA75.DLL
However, when I added those same 5 files to the customer's
environment, the error 3012 persists.

So, I have 2 questions, please
1. What's wrong?
2. How do I find out what is wrong? In other words, is there some
utility or switch or something that will tell me WHY I am getting an
error 3012. The PVSW.LOG file from the problem machine says:

Date Time Component Process Process Name Machine
Name Type Category Msg ID Message
---------- -------- --------------- -------- ---------------
--------------- ---- ---------- --------
--------------------------------------------------
06-08-2001 12:39:09 ECAS_API 00000368 krnl386.exe FOCUS2
E ECASAPI (1.12.1.4083): Error 8505 - An
initialization error occurred when trying to establish a session with
the WSE
06-08-2001 12:39:09 ECAS_API 00000368 krnl386.exe FOCUS2
E ECASAPI (1.1.1.4083): Error 8517 - An
error occurred when closing the session with the WSE
05-30-2002 15:18:25 ECAS_API 000003A8 krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-30-2002 15:18:26 ECAS_API 00000318 W3DBSMGR.EXE FOCUS2
E W3DBSMGR (24.4.8591): Error 8591 -
Database manager already loaded
05-30-2002 15:18:27 ECAS_API 000003A8 krnl386.exe FOCUS2
E ECASAPI (1.12.1.4083): Error 8505 - An
initialization error occurred when trying to establish a session with
the WSE
05-30-2002 15:18:28 ECAS_API 000003A8 krnl386.exe FOCUS2
E ECASAPI (1.1.1.10): Error 8517 - An
error occurred when closing the session with the WSE
05-30-2002 15:24:39 ECAS_API 000003A8 krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-30-2002 15:24:39 ECAS_API 00000408 W3DBSMGR.EXE FOCUS2
E W3DBSMGR (24.4.8591): Error 8591 -
Database manager already loaded
05-30-2002 15:24:40 ECAS_API 000003A8 krnl386.exe FOCUS2
E ECASAPI (1.12.1.4083): Error 8505 - An
initialization error occurred when trying to establish a session with
the WSE
05-30-2002 15:24:41 ECAS_API 000003A8 krnl386.exe FOCUS2
E ECASAPI (1.1.1.10): Error 8517 - An
error occurred when closing the session with the WSE
05-30-2002 15:36:20 ECAS_API 00000358 krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-30-2002 15:36:24 ECAS_API 00000358 krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-30-2002 15:40:23 ECAS_API 00000358 krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-31-2002 09:55:55 ECAS_API 000002DC krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-31-2002 09:56:00 ECAS_API 000002DC krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-31-2002 10:00:30 ECAS_API 000002DC krnl386.exe FOCUS2
E ECASAPI (1.21.1.18): Error 8509 - A
timeout occurred during the initialization of MKDE
05-31-2002 10:00:30 ECAS_API 00000180 W3DBSMGR.EXE FOCUS2
E W3DBSMGR (24.4.8591): Error 8591 -
Database manager already loaded
05-31-2002 10:00:31 ECAS_API 000002DC krnl386.exe FOCUS2
E ECASAPI (1.12.1.4083): Error 8505 - An
initialization error occurred when trying to establish a session with
the WSE
05-31-2002 10:00:32 ECAS_API 000002DC krnl386.exe FOCUS2
E ECASAPI (1.1.1.10): Error 8517 - An
error occurred when closing the session with the WSE

So, again, I am looking for either
- What is wrong
or
- A way to find out what is wrong.

Thanks for any assistance any of you can provide.

David Flaschen
DavidF...@DFESoftware.com
1-800-521-2475 x8522

Bill Bach

unread,
Jun 3, 2002, 8:18:04 AM6/3/02
to
You don't need to just add files -- you need to install the Pervasive.SQL
2000i Workstation Engine (WSE). This will properly install and configure
the various components that you need. The WSE is available for only $25.

The switches appear to be correct -- the errors in the PVSW.LOG indicate
that the system is TRYING to fins the WSE, but it cannot do so. As such,
there must be a missing file or configuration in the registry yet.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
Bill...@goldstarsoftware.com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: July 15-18, 2002 - See our web site for details!

0 new messages