3100 to 3199

---

Network Services Layer Status Codes

The following status codes originate from the Pervasive Network Services Layer (PNSL).

3103: Server name not found by Pervasive Network Services Layer

The search for a target server name was unable to resolve an address after searching NDS, bindery, named pipes, and DNS. Some possible causes include:

• No common communication protocol is available between the server and the client. Check the Supported protocols setting within the Communication protocols option for both the client and server. Make sure there is a common protocol (either SPX or TCP/IP) between the server and the requester.
• For Windows NT/2000:
  • The MicroKernel engine not running.
  • Server only: Named pipes are used in these two operating systems to resolve server names. The networking at the operating system level was unable to find the target named pipe.
• For NetWare:
  • The Server Addressing Protocol (SAP) filtered out the server name. SAP is used in NetWare 3.x and can be used in version 4.x. This type of filtering is common in WAN environments.
  • NWCALLS.DLL and/or NWIPXSPX.DLL is missing when using the Win16 client. This is especially likely if the Win32 clients are functioning but the Win16 clients do not. These are NetWare system files that can be obtained from Novell web site (http://www.novell.com).
  • For NetWare using TCP/IP: The server name is not in DNS.
• For Novell NetWare 4.11 and Microsoft Windows 98 installs of Pervasive.SQL Client:
  • When the Pervasive System Analyzer tries to perform the first communication/functionality test, a status 3103 is returned. This status code may be caused by having no supported protocols set in the Pervasive.SQL client configuration utility. If Microsoft SPX is added as a supported protocol, the installation should complete without error.

3104: The Pervasive Network Services Layer encountered a permission error

For Windows NT only: Permission to access the target named pipe is denied. If you receive this status code:

• Verify that you have access to the inter-process communication mechanism.
• Ensure that your passwords are identical if you have the same user name on two systems.

3105: No available transport protocol for the Pervasive Network Services Layer

No transport protocol that is common to both the target server engine and clients is available. For example, this status code could be caused by a client using SPX when the server engine only has TCP/IP available. Check the Supported protocols setting within the Communication protocols option for both the client and server. For more information on Communication protocols, refer to Advanced Operations Guide.

3106: The Pervasive Network Services Layer encountered a connection failure

The Pervasive Network Services Layer was able to establish a transport connection at the client side, but the connection attempt at the target side failed. Some possible causes are:

• The MicroKernel is not running on the server.
• The network is overloaded.
• The connection path is invalid.
• You have more than one mapped drive to the same server.
• You are trying to access a Server engine on a Windows NT server, and the Server engine's Access4Accept Remote Requests setting is set to Off. You must turn this setting On using the Configuration utility in Pervasive Control Center. See Advanced Operations Guide for more information.

Check the Pervasive Event Log (PVSW.LOG) for more information if you receive this status code.

3107: The Pervasive Network Services Layer is out of memory

The Pervasive Network Services Layer has insufficient memory to continue. Verify that you are not in a low memory condition.

3108: The Pervasive Network Services Layer detected an invalid session

The application attempted to use a network session that was not recognized by the Pervasive Network Services Layer. If the error persists, contact Technical Support at Pervasive Software.

3110: The network layer is not connected

The application attempted to use a network connection that was no longer active. This happens when the session with the Pervasive Network Services Layer is still valid, but was dropped by the network. Stop and restart the application.

3111: Failure during send to the target server

The Pervasive Network Services Layer attempted to send an application request to the target server and encountered a network specific error from the target. Check the Pervasive Event Log (PVSW.LOG) for more information.

You may receive this error when attempting to connect to a Workgroup engine on Windows 95 if the machine has not been upgraded to Winsock 2. If you are not running Winsock 2 on your Windows 95 computer with Workgroup engine installed, you should download the WinSock 2 update from Microsoft: http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/default.asp?site=95.

---

Note
If there is a problem with AutoReconnect, a further status code 3131 will be issued.

---

3112: Failure during receive from the target server

The Pervasive Network Services Layer attempted to receive data from the target server and encountered a network specific error. Check the Pervasive Event Log (PVSW.LOG) for more information.

You may receive this error when attempting to connect to a Workgroup engine on Windows 95 if the machine has not been upgraded to Winsock 2. If you are not running Winsock 2 on your Windows 95 computer with Workgroup engine installed, you should download the WinSock 2 update from Microsoft: http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/default.asp?site=95.

---

Note
If there is a problem with AutoReconnect, a further status code 3131 will be issued.

---

You may also receive this error under the following circumstances:

• When using only the NetBIOS protocol with a remote Workgroup engine, the client is sending more bytes than can fit into the engine's network read buffer. Go the machine where the remote Workgroup engine is installed, and try increasing the value of the configuration parameter, Server4Communication Buffer Size4Read Buffer Size.

3114: The routing table of the Pervasive Network Services Layer is full

The Pervasive Network Services Layer Server Routing Table is full. This table normally grows dynamically as needed. Verify that you are not in a low memory condition.

3115: Pervasive Network Services Layer encountered a transport failure

The Pervasive Network Services Layer encountered a WinSock (Win32, Win16) error while creating the local transport endpoint on the client side. Check the Pervasive Event Log (PVSW.LOG) for more information.

3119: No authentication context is available

NSL was unable to return the access context on the specified session for the supplied object. There are several reasons why NSL could not obtain the context and it varies depending on the transport type.

• NamePipe - It is possible that NSL was able to locate the server via DNS, but when it tried to make a Named Pipes call to request authentication of the client, the Named Pipes communications failed. Ensure that Named Pipes is configured correctly for the network for both the client and server. See your operating system documentation for information on Named Pipes configuration.
• Novell NetWare Client - NSL asks the NetWare Client if this workstation has access to the database on the NetWare server. Ensure the user is configured to access the database file on the server.
• NetWare - You can configure this operating system to use RunTime Server Support. NSL creates a context using one of the following:
  • the userID and password configured in the NetWare RTSS setting
  • the userID and password already used on this workstation to connect to any server
  • the workstation userID and password.

If you want to use this mechanism, RTSS must be enabled. See the Advanced Operations Guide for more information on enabling RTSS and userID and password configuration.

• Windows - you use stored client credentials to authenticate to the server, and there are no credentials stored and value for the Prompt for Client Credentials setting is Off.

To resolve this condition, use the Configuration utility to change the Prompt for Client Credentials setting to On, or use the pvnetpass utility to store a valid set of client credentials for the server. See Advanced Operations Guide for more information about security. See Pervasive.SQL User's Guide for more information about the pvnetpass utility.

• Linux - You must configure a username and password for all remote server data access. To resolve this condition, use the pvnetpass utility to specify a username and password for the given server, or create a default username and password for the server using pvnetpass. See Advanced Operations Guide for more information about security. See Pervasive.SQL User's Guide for more information about the pvnetpass utility.

3124: Pervasive Network Services Layer task table is full

For each user of the Network Services Layer, a task entry is created. If the maximum number of tasks has already been reached (512 and not configurable), this error is returned. Close any applications using Pervasive.SQL that are no longer needed.

3125: The Pervasive Network Services Layer was unable to resolve the Novell Directory Services name into a NetWare server name

The Pervasive Network Services Layer was unable to resolve the Novell Directory Services name into a NetWare server name. This occurs on Windows 95/98/ME workstations with the Microsoft Service for Novell Directory Services in cases where the system is unable to load the Windows 95 Requester support modules. Ensure that the Requester Win95 support modules are installed and available, and that NWCALLS.DLL is available on the Windows 95 workstation.

3126: The Pervasive Network Services Layer was unable to resolve the given filename into a valid path

Check that the given filename is a valid file format and path.

3127: Failure during send to the IDS target server

The IDS client requester attempted to send data to the IDS target server and encountered a TCP/IP specific error. Stop and restart the application. If the problem persists, consult your network administrator.

3128: Failure during receive from the IDS target server

The IDS client requester attempted to receive data from the IDS target server and encountered a TCP/IP specific error. Stop and restart the application. If the problem persists, consult your network administrator.

3131: Pervasive Network Services Layer encountered an error while reconnecting

This status code means that AutoReconnect was unsuccessful. The following messages will appear in PVSW.LOG:

• "3131: Reconnect failed. Client and Server Message IDs out of synchronization." The client and server did not agree on the current context. Because the integrity of the last request cannot be verified, the connection was terminated.
• "3131: Reconnect not attempted, AutoReconnect not enabled on either client or server." In this case, either the client, server or both has AutoReconnect disabled or your server version does not support AutoReconnect (pre-Pervasive.SQL V8). The reconnection attempt will not be made.
• "3131: Reconnection attempt timed out." This means that the client was unable to obtain a new connection to the server within the AutoReconnect timeout period.
• "3131: Reconnection negotiations failed after re-establishing network connection." This means that the client was successful in making a new network connection to the server, but communications failed during the Pervasive AutoReconnect negotiations.

---

Note
A PVSW.log entry of "0: Reconnect after send/receive failure was successful" indicates a successful connection.

---

3132: Unsupported Function

This error is returned when the Scalable SQL interface attempts to communicate with the Pervasive.SQL 8 Network Services Layer (NSL).

The legacy Scalable SQL Engine is not supported in any combination with Pervasive.SQL 8 components. If you receive this error, search for and uninstall Scalable SQL (or Pervasive.SQL 7), and/or all if its components.