When you start Service Accent, or run DBRouter.exe, you receive a Pervasive.SQL status code of 3012 or 3014.
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.
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:
- Go to Windows Explorer
- 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
- 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