Microframe Corporation 3007 Series Betriebsanweisung PDF herunterladen (Seite 140)

1-132

Status Codes

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.

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 PSQL v11). 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

1 2 ... 135 136 137 138 139 140 141 142 143 144 145 ... 251 252

Keine Kommentare

Microframe Corporation 3007 Series Betriebsanweisung Seite 140