Database Error: 3012 or Database Create Error 3012
Topic T1144
Applies to All NEO Products
Problem NEO reports a Database Error 3012 and will not start. Pervasive refers to this as encountering a 'Status 3012'.
Description This is an uncommon problem that confronts new users trying to start NEO for the first time and is related to a Pervasive conflict, setup or configuration problem.
Resolution 1, from the Pervasive Knowledge Base Status 3012: Local engine is not accessible to the MicroKernel router
Problem Description: Status 3012: Local engine is not accessible to the MicroKernel router
Problem Environment: Pervasive.SQL 2000
Status Codes and Messages
Cause of this problem: Access to the local engine is not possible because it is not loaded or could not be launched. You can receive this status code if you try to access a local file on a client and you do not have a MicroKernel workstation engine installed or if you try to access a local file on a server and the MicroKernel server engine is not running.
Solution: If you have only a server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, perform the following steps to 'Turn Off Local Engine Support' (for clients and workstations only):
Click Start, point to Programs, then to Pervasive, and then Pervasive.SQL Control Center.
Expand Pervasive.SQL 2000 Engines and expand the desired database.
Expand Configuration, then expand Client, and click on Access.
In the right hand frame, double-click on Local, change the Current value to Off, and click OK.
In the right-hand frame, double-click on Requester, change the Current value to Off, and click OK.
In the right-hand frame, double-click Target Engine, change Current to Server only, and click OK.
In the left-hand frame, expand Client-16 bit and click on Access.
In the right-hand frame, double-click Use Local MicroKernel Engine, change Current value to Off, and click OK.
Make sure the Use Remote MicroKernel Engine value is set to on and that the remote engine is set to accept remote requests.
Resolution 2, from the Pervasive Knowledge Base
Multithreaded app fails to restart MKDE
Problem Description: Multithreaded app fails to restart MKDE
Problem reproduced with test program which has two threads running. One thread opens a Btrieve file. WGE auto loads and open is successful. Thread issues reset. The WGE auto unloads. Sometime later, the second thread tries to open a file. It gets status 95.
Status 3012: 'Local engine is not accessible to MicroKernel router.'
Problem Environment: Pervasive.SQL 2000 WG
Service Pack 2a, Defect: 27603
Solution: This issue was addressed by Service Pack 3.
