How to Fix Sage Pervasive Error 3012

1. Status 3012: Local engine is not accessible Admittance to the neighborhood motor is absurd since it isn't stacked or couldn't be sent off. You can get this status code on the off chance that you attempt to get to a nearby document on a client and you don't have a Microkernel workstation motor introduced or on the other hand assuming you attempt to get to a neighborhood record on a server and the MicroKernel server motor isn't running. Reason for the Problem Admittance to the neighborhood motor is absurd since it isn't stacked or couldn't be sent off. You can get this status code on the off chance that you attempt to get to a nearby record on a client and you don't have a MicroKernel workstation motor introduced or then again assuming you attempt to get to a neighborhood document on a server and the MicroKernel server motor isn't running. Read More-: Sage Pervasive Error 3012 Arrangement Notes NOTE: The v10 and v11 items are recorded under Pervasive. Beginning with v12 items are recorded under Actian. Check the PSQL Engine is running. Workgroup: If introduced as an application check w3dbsmgr.exe is running in Task Manager. Whenever introduced as a help confirm the PSQL Workgroup administration is running. Beginning in v12 the item is introduced as a help of course. Server: Verify the PSQL Services are running (Transactional and Relational). Client introduced. In the event that you are attempting to open a record on a client and the Client item is introduced, you will get a Status Code 3012 as there is no motor accessible to open the document. Network issues. Assuming you are on a client and attempting to get to a record on a server with an authorized/running PSQL motor there might be an organization issue obstructing admittance to the server (you might get a Status Cod 3014 too). Check the name and IP Address of the server. On the client ping the server by name and check the right IP Address is returned. If not, there might be a DNS issue.

2. For PSQL.SQL 2000i items: On the off chance that you have just a server motor introduced and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 admonition sections, play out the following strides: To Turn Off Local Engine support (for clients and workstations as it were): 1. Click Start, highlight Programs, then, at that point, to Pervasive, and afterward Pervasive.SQL Control Center. 2. Grow Pervasive.SQL 2000i Engines and extend the ideal data set. 3. Grow Configuration, then, at that point, extend Client, and snap on Access. 4. In the right hand outline, double tap on Local, change the Current worth to Off, and click OK. 5. In the right-hand outline, double tap on Requester, change the Current worth to Off, and click OK. 6. In the right-hand outline, double tap Target Engine, change Current to Server just, and click OK. 7. In the left-hand outline, extend Client-16 cycle and snap on Access. 8. In the right-hand outline, double tap Use Local MicroKernel Engine, change Current worth to Off, and click OK. 9. Ensure the Use Remote MicroKernel Engine esteem is set to on and that the distant motor is set to acknowledge remote solicitations. Read More-: Sage Pervasive Error 3012