Resolving Pervasive.SQL status 3012 and 3014 (Part 2)

Article ID: 090827105752 - Last Review: 27 August 2009 by jasonl - Revision: 1 - Views: 63006


Symptom
When you start Service Accent, or run DBRouter.exe, you receive a Pervasive.SQL status code of 3012 or 3014.


Cause
These error codes imply that the Pervasive.SQL client could not communicate with the Pervasive.SQL server component on the target machine.

A misconfigured network is often to blame here, whereby the hostname of the server (e.g., "server") resolves to a different IP address than the actual IP of the server. This can be verified by getting to the command prompt and typing
ping server

where server is your actual server's host name.

Typically, you will see output similar to the following:
C:\>ping server

Pinging server.ourcompany.com [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


However, if the IP address returned in the ping results is not correct, this would indicate the cause of the Pervasive.SQL error.

You can verify if this is the case or not by typing in
ping -a IPADDRESS

where IPADDRESS is the IP address returned in the previous ping. For example:
C:\>ping -a 192.168.0.1

Pinging server.ourcompany.com [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

In these examples, pinging the host returned the correct IP address and pinging the IP address returned the correct host. If either of these returns a different result, you need to contact your system administrator to resolve the DNS issue.


Solution
In this case, you can force the correct IP address to be used even though your server's hostname is not configured correctly. To do this, follow these steps:


  1. Go to Windows Explorer
  2. In the Address Bar, type
    \\IPADDRESS\ShareName

    Where IPADDRESS is the local IP address of the server and ShareName is the shared volume's name, e.g.,
    \\192.168.0.1\AccentDB

  3. Locate DBRouter and run it to force Service Accent (i.e., Pervasive.SQL) to use the server at that specific IP address and not the one configured for the server's hostname



 
 Related articles

3103, 3012 or 3014 error when trying to access a Pervasive database
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
Message 'Setup has detected that unInstallShield is in use' when installing Pervasive.SQL 2000i
Pervasive.SQL error 2 using Windows Server 2003 and Pervasive.SQL Server Edition
Pervasive.SQL returns a status of 46 when starting Service Accent
Pervasive.SQL V8 compatibility
Resolving Pervasive status 84
Running Pervasive.SQL V8 Server Edition on a Windows XP Professional platform
Running the Pervasive.SQL server engine under Windows Server 2003
Status 94 with Pervasive.SQL Server on Windows NT, 2000, 2003
Unable to configure Pervasive.SQL ODBC via Remote Desktop
Unable to connect to Pervasive.SQL Monitor remotely
Using Pervasive.SQL on a 64 bit CPU
Windows NT 4 Server with Windows 2000 clients and Pervasive.SQL 2000 Server

 Additional articles from the white papers

Pervasive Backup Agent v3
Service Accent - Installing Pervasive. SQL
Installing and configuring Pervasive. SQL 2000



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.