Microframe Corporation 3007 Series Guía de usuario descargar pdf (Pagina 136)

1-128

Status Codes

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 32-bit Platforms:

 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.

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

1 2 ... 131 132 133 134 135 136 137 138 139 140 141 ... 251 252

Sin comentarios

Microframe Corporation 3007 Series Guía de usuario Pagina 136