
1-129
3100 to 3199
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 32-bit
server, and the Server engine’s Accept Remote Requests setting is
set to Off. You must turn this setting On. See To access
configuration settings in PCC for a local client in Advanced
Operations Guide. Click the Access category in the Properties
tree.
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
Kommentare zu diesen Handbüchern