3103, 3012 or 3014 error when trying to access a Pervasive database

Article ID: 120105094316 - Last Review: 05 January 2012 by nigelp - Revision: 2 - Views: 18056


Symptom
3103, 3012, 3014 error when trying to access the Service Accent database on the server from a workstation


Cause
The target server is actively refusing the connection, probably caused by Windows Firewall or 3rd Party software or hardware firewalls.


Solution
You need to either open the firewall for the ports that Pervasive.SQL listens on, or add the appropriate component to the firewall access list. To add Pervasive PSQL components to the firewall access list, add the following:

* For Pervasive PSQL 32-bit Server, ntdbsmgr.exe.
* For Pervasive PSQL Workgroup, w3dbsmgr.exe.
* For Pervasive PSQL 64-bit Server, ntdbsmgr.exe and ntdbsmgr64.exe.

If you prefer to open ports, open 3351 for the transactional interface, 1583 for the relational interface, and 139 for named pipes.


If you cannot get any of the above to resolve your issue then try uninstalling Pervasive from the server and reinstall it



 
 Related articles

Can not link to the WORK table using Pervasive.SQL ODBC
Can't start Pervasive Server Engine, Error 1069, login failure
Configuring Pervasive.SQL ODBC
Connecting to your Service Accent database via ODBC with Pervasive.V8 and later
Error message "1607:Unable to install InstallShield Scripting runtime" when trying to install Pervasive.SQL
Error message "DBU - Access Denied" when entering Pervasive.SQL license key
How to close Pervasive.SQL tables manually
How to configure Pervasive Backup Agent
How to disable the Local MicroKernel Engine under Pervasive.SQL V9
Installing Pervasive.SQL results in an 'Installation was interrupted' message

 Additional articles from the white papers

Service Accent - Adding client reports



For additional resources and information, you can go to the Service Accent Support Centre

Click here to go to the Service Accent Support Centre



Copyright © 2003-2018 Vantage Computing Ltd. All rights reserved. The information contained on this web site is correct as of its publication date.