User Guide

690 System Messages
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
TIMESYNC-X-137: SINGLE servers are incompatible with REFERENCE and PRIMARY
servers and should not follow secondary servers. This server polled: server_name.
The time exchange was ignored!
Source: TIMESYNC.NLM
Explanation: A Single Reference server should not exist in an environment that includes a
Reference or Primary server.
Action: Check the Time Source List in the TIMESYNC.CFG file for both the named
server and the server reporting the error. Single servers do not need a Time
Source List. Secondary servers should never be in a Time Source List.
TIMESYNC-X-138: Time synchronization has been established.
Source: TIMESYNC.NLM
Explanation: This message appears right after you load TIMESYNC.NLM or after you
reestablish synchronization.
Action: If the time period between when you lost synchronization and when it was
reestablished is no more than a few minutes, no action is needed. If, however,
the gap is significant (more than 15 minutes), use standard troubleshooting
techniques to make sure that the system does not have a hardware problem.
See Troubleshooting in the online documentation.
TIMESYNC-X-150: Cannot allocate SAP socket tag.
Source: TIMESYNC.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory
Temporarily in the Server Operating System Administration Guide.
TIMESYNC-X-151: Cannot open SAP socket.
Source: TIMESYNC.NLM
Possible Cause: The operating system has no more sockets to allocate. The user is probably
trying to run more processes on a single server than is practical.
Action: To alleviate the problem temporarily, unload any unneeded NLM programs
that require SAP sockets. To prevent future occurrences of the problem, try
distributing your network services over more than a single server.