A Pervasive 3012 error occurs when Windward cannot connect to the Pervasive database. Specifically, a Pervasive “engine” runs on a computer where your System Five data files are located. The two events listed below will occur that prevent Pervasive communications:
Windward System Five uses a mapped network drive connection in order to communicate data between the client and the server. A share is set up on the server, usually, a folder named Windward which contains System5\Data where Data is your company dataset.
In Windows, the Map Network Drive function is used and a network drive is set to the drive letter W with the server path as “\\server\Windward”. An easy troubleshooting step is to determine if the mapped drive will open. If the mapped drive does not open, then the computer network will need to be checked.
The following link is to a networking best practices document that will assist in explaining Windows networking setups.
A ping test can be run to determine if the server is responding to requests across the network. The link below will show a demonstration of the ping test.
All versions of Pervasive come with a diagnostic tool called “Pervasive System Analyzer”. When the test operates correctly we will see 75 test messages sent via TCP/IP to the server computer. The link below will demonstrate how to use the Pervasive System Analyzer.
All windows computers have a host file that will set a server name to a network address. This file will need to be reviewed for correctness. A standard windows network should run Pervasive without any entries in the host file.
The Pervasive Engine on the server needs to be running or all workstations will receive the 3012 error. The following link will demonstrate the steps to locate the Pervasive service on the server.