|
Code
|
Definition
|
Explanation
|
Solution
|
|
3
|
General Error
|
The details of the event message will explain the exact cause of the error.
|
|
|
101
|
Windows Socket initialization failed
|
Unable to initialize socket communication.
|
Reboot server. If it continues to fail, re-apply service pack.
|
|
12288
|
CPU Limit Reached
|
Server machine has more virtual CPU’s than current license supports.
|
Contact Pragma Systems to order an upgrade.
|
|
12289
|
Evaluation expires
|
Evaluation time period is over.
|
Call Pragma Systems to order
|
|
12290
|
Bad InetD Setup
|
An InetD Services has an invalid value for a setup configuration.
|
Check all services under InetD Configuration. All values for each service must be valid.
|
|
12291
|
InetD Access Denied
|
InetD has been configured to deny access to the remote machine or InetD cannot run the configured process.
|
Check Granted/Denied IP List for service under InetD Configuration. Check path and spelling for program to launch.
|
|
12292
|
Alloc Error
|
InetD was unable to allocate a console for the session
|
Increase the InetD Desktop Count, or check the Shared Section value. See the FAQ regarding a small number of sessions.
|
|
12293
|
Winsock Error
|
|
|
|
|
Receive from client failure.
|
A socket error occurred during read of data. Following error code will give more information. See error codes below.
|
|
|
|
Client dropped before sending data.
|
Data was removed from socket before it could be received by server. There might be another program monitoring sockets.
|
Check all TCP/IP applications for possible interference.
|
|
|
getpeername failure
|
The server is unable to collect information on the remote client.
|
Another program has added a Layered Service Provider (LSP) which is conflicting with the server. Uninstall the other application and re-boot.
|
|
12294
|
Registration Error
|
There is an error with the registration key. The Event Log will give further details.
|
Repair the registration key.
|
|
12295
|
Successful Logon
|
A user successfully logged on to the server.
|
|
|
12296
|
Failed Logon
|
A user failed to logon to the server.
|
|
|
12297
|
Successful Logoff
|
A user successfully logged off the server.
|
|
|
12298
|
Session Reconnects
|
A user successfully reconnected to an active session.
|
|
|
12299
|
Child Process Terminated
|
A child process was terminated by the monitor child process feature.
|
|
|
12300
|
Session closed by server
|
A session was closed due to one of the orphan cleanup features.
|
|
|
12301
|
User shell error
|
The configured user shell or startup program experienced a problem.
|
Check event details for application return code to troubleshoot application run within user session.
|
|
12302
|
InetD Connection Message
|
A connection was attempted by a remote client.
|
|
|
12303
|
InetD Service start failure
|
The service Pragma InetD failed to initialize. This can caused by resources insufficient to launch the service.
|
Correct network configuration for server network.
|
|
12304
|
InetD Service sub-service error
|
Service died before the quick die threshold of Fortress SSH or custom process.
|
Check sub-server to make sure it can be executed on the server.
|
|
12299
|
TelmSrvc Warning Event Message
|
|
|
|
|
Successful Logoff
|
User was successful logged off by an Administrator
|
|
|
|
Failed Logoff
|
User could not be logged off by an Administrator
|
Try again. If still fails, have user log out manually.
|
|
|
Server Process closed
|
Administrator successfully killed the server process
|
|
|
|
Server Process could not be closed
|
Administrator failed to kill the server process
|
Try again. If still fails, have user log out manually.
|
|
10004
|
Interrupted function call
|
Windows Socket Error
|
Try operation again.
|
|
10009
|
The file handle supplied is not valid.
|
Windows Socket Error
|
Disconnect and try again.
|
|
10013
|
Permission Denied.
|
Windows Socket Error
|
Disconnect and try again.
|
|
10014
|
Bad address
|
Windows Socket Error
|
Disconnect and try again.
|
|
10022
|
Invalid argument
|
Windows Socket Error
|
Disconnect and try again.
|
|
10024
|
Too many open files
|
Windows Socket Error
|
Disconnect and try again.
|
|
10035
|
Resource temporarily unavailable
|
Slow network communication is causing socket errors.
|
Check network performance.
|
|
10036
|
Operation now in progress
|
Slow network communication is causing socket errors.
|
Check network performance.
|
|
10037
|
Operation already in progress
|
Slow network communication is causing socket errors.
|
Check network performance.
|
|
10038
|
Socket operation on non-socket
|
Windows Socket Error
|
Disconnect and try again.
|
|
10039
|
Destination address required
|
Windows Socket Error
|
Disconnect and try again.
|
|
10040
|
Message too long
|
Windows Socket Error
|
Try the operation again.
|
|
10041
|
Protocol wrong type for socket
|
A wrong type for a protocol is specified in the socket function call.
|
Check services under InetD Configuration for correct Type.
|
|
10042
|
Bad protocol option
|
A bad option was specified in a call.
|
Check services under InetD Configuration for correct Network Properties.
|
|
10043
|
Protocol not supported
|
A requested protocol is not supported.
|
Check services under InetD Configuration for correct Protocol.
|
|
10044
|
Socket type not supported
|
An unsupported socket type is in use.
|
Check service under InetD Configuration for correct Type and Protocol.
|
|
10045
|
Operation not supported
|
The type of object referenced is not supported by the operation.
|
Check service under InetD Configuration for correct Type and Protocol.
|
|
10046
|
Protocol family not supported
|
The protocol family has not been configured.
|
Install required protocol.
|
|
10047
|
Address family not supported by protocol family.
|
Socket address is already defined for a different protocol.
|
Check service under InetD Configuration for correct Type and Protocol.
|
|
10048
|
Address already in use.
|
Program attempting to connect on socket in use by other program.
|
Try again. If continues to fail, reboot.
|
|
10049
|
Cannot assign requested address
|
The remote address or port is not valid.
|
Check address and port for remote machine.
|
|
10050
|
Network is down
|
Network went down.
|
Check network configurations.
|
|
10051
|
Network is unreachable
|
There is not a route to the remote machine.
|
Check network configurations.
|
|
10052
|
Network dropped connection on reset
|
Windows Keep Alive feature detected a failure.
|
Try again. If continues, re-apply service packs, and check network configurations and connections.
|
|
10053
|
Software caused connection abort
|
Remote machine closed connection.
|
This is reported if the client disconnects in an ungraceful manner. Check client for any problems.
|
|
10054
|
Connection reset by peer
|
Remote machine closed connection.
|
This is reported if the client disconnects in an ungraceful manner. Check client for any problems.
|
|
10055
|
No buffer space available
|
System Socket Error
|
Disconnect and try again. Reboot server, if problem continues.
|
|
10056
|
Socket is already connected
|
Windows Socket Error
|
Disconnect and try again.
|
|
10057
|
Socket is not connected
|
Windows Socket Error
|
Disconnect and try again.
|
|
10058
|
Cannot send after socket shutdown
|
Windows Socket Error
|
Disconnect and try again.
|
|
10059
|
Too many references to some kernel object.
|
System Socket Error
|
Disconnect and try again. Reboot server, if problem continues.
|
|
10060
|
Connection timed out
|
Remote machine did not respond before network timeout.
|
Check network configuration and connections between server and client.
|
|
10061
|
Connection refused
|
The remote machine refused connection.
|
Make sure InetD service is running and protocol server is configured and enabled.
|
|
10062
|
Cannot translate name.
|
The remote machine name cannot be translated to a valid IP.
|
Connect using IP.
|
|
10063
|
Name component or name was too long.
|
The remote machine name is too long.
|
Check the name.
|
|
10064
|
Host is down.
|
The remote machine is no longer active.
|
Check remote machine is on.
|
|
10065
|
No route to host.
|
The remote machine became unreachable during session.
|
Check all network connections between client and server.
|
|
10091
|
Network subsystem is unavailable
|
The Windows Socket system files are damaged or incorrect.
|
Re-apply latest service pack to server.
|
|
10092
|
WINSOCK.DLL version out of range
|
The Windows Socket system files are damaged or incorrect.
|
Re-apply latest service pack to server.
|
|
10093
|
Successful WSAStartup not yet performed
|
Windows Socket Error
|
Disconnect session and try again.
|
|
11001
|
Host not found
|
The server name is not known.
|
Check the server name or connect by IP address.
|
|
11002
|
Non-authoritative host not found
|
An authoritative server did not answer to the local server.
|
Try again at a later time.
|
|
11003
|
This is a non-recoverable error
|
Network setup (DNS, HOSTS, Services) for the host machine are damaged.
|
Correct network configuration of server.
|
|
11004
|
Valid name, no data record of requested type
|
The requested name does not have the correct associated data.
|
Correct network configuration for server network.
|
|
|
AllocConsole error
|
Unable to open a command shell.
|
Possible solution is to alter the global window heap for the Win32 subsystem. This is done by altering SharedSection option for the Win32 subsystem. We recommend SharedSection=1024,3074,1024.
|