Possible Cause: Occurs when configuring NAAS Database using the default configuration utility.
Action: Check the connectivity problems using Pervasive System Analyzer (PSA).
Click Start > Pervasive > Pervasive.SQL 2000i > Utilities > Pervasive System Analyzer > Next.
Select Test Network Communication > enter the path to the file for storing the test log > Next.
Enter or browse to the location of the Pervasive engine (for example, \\SERVER_NAME\SYS:\PVSW) and click Next.
The PSA performs the connectivity test and logs the errors in the test log.
Click Next to view the log file.
The latest standalone version of the PSA available for Pervasive.SQl 2000 SP3 can be downloaded from the Pervasive support site. For information about using PSA, refer to the Webinar archive
Action: Resolve and verify the IP address of the NetWare server, since Pervasive.SQL 2000 SP3 uses either the DNS or eDirectory name of the NetWare server to resolve the IP address.
To resolve the IP address of the NetWare server based on its eDirectory name, the following conditions should be satisfied.
To verify whether the IP address of the machine has been resolved, refer to the connection test log generated by the PSA.
To check whether the IP address can be resolved using the DNS name of the server, PING the server using the server name. If this is successful, then the Pervasive.SQL 2000 SP3 client will resolve the IP address.
Action: Configure the Pervasive client such that only TCP/IP is used as the communication protocol. Ensure that both the Btrieve* and the Pervasive.SQL 2000 clients are configured for TCP/IP protocol.
To configure the Pervasive client:
In the client, go to the Pervasive Control Center (PCC) and click Configuration > Client > Communications Protocol.
Set Supported Protocols to Microsoft* TCP/IP Only.
To configure the Pervasive server:
Go to the PCC and register the server.
Click Configuration > Server and set supported protocols and ODBC supported protocols to Novell TCP/IP.
Restart the PCC and the server.
Action: If the server has multiple IP addresses, the IP address used for the client communication should be checked.
If the server has both public and private IP address, ping the server using the private IP addresss.
HINT: If you are unable to ping the server using the server name or its IP address, then check the network connectivity.
Action: If the server has multiple IP addresses, the DNS query will return only the public IP address. To connect the client through the firewall, open the ports 1583 and 3351 (Decimal).
All the errors generated during the process of establishing the server connection are logged in the log file PVSW.LOG. This file is located in SYS:\SYSTEM directory in the server or C:\WINNT directory in Windows NT or 2000 client.