69.0 TIMESYNC Messages

The following includes messages from TIMESYNC.NLM.

TIMESYNC-X-48: Cannot initialize time synchronization.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-49: Cannot start time synchronization.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-51: Cannot allocate settable parameters tag.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-53: Cannot allocate alloc tag.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-55: Cannot allocate NCP resource tag.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-57: Cannot allocate process tag.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-59: Cannot allocate event tag.

Source: TIMESYNC.NLM
Explanation: Time synchronization cannot be initialized.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-60: Cannot parse load command line arguments.

Source: TIMESYNC.NLM
Explanation: One of the following probably accounts for this error:
Possible Cause: The syntax in the command line is invalid possibly due to typos or use of illegal characters.
Action: Make sure the syntax in your command line is valid.
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-61: Cannot initialize global information.

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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-62: Cannot hook TimeSync NCP verb.

Source: TIMESYNC.NLM
Explanation: The TIMESYNC program cannot get a resource. Someone or another program is already running a version of TIMESYNC.NLM that is interfering with the current NLM program running.
Action: Find out who or what is running the interfering NLM program and unload it
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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-63: Couldn’t allocate main stack.

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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-65: Couldn’t create main process.

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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

TIMESYNC-X-72: Time synchronization has been lost after number successful polling loops.

Source: TIMESYNC.NLM
Explanation: Time synchronization was lost for some unexplained reason. This is normally not a problem and the system will reestablish synchronization. However, if the problem occurs frequently, the system may have a hardware or network problem.
Action: Try the following:

  • Check for recent time changes or configuration changes that may have caused this problem.

  • Check the Synchronization Radius parameter and make sure it is not unreasonably small. A practical limit is 1000 milliseconds (1 second).

  • The system might be experiencing a hardware or network problem. See Troubleshooting in the online documentation.

TIMESYNC-X-73: Unrecognized command line parameter: parameter.

Source: TIMESYNC.NLM
Explanation: The user entered an invalid parameter in the command line.
Action: Try again using the correct syntax.

TIMESYNC-X-77: Unrecognized parameter in configuration file: string.

Source: TIMESYNC.NLM
Explanation: The user entered an invalid parameter in the TIMESYNC.CFG file.
Action: Try again using the correct syntax.

TIMESYNC-X-92: Primary, reference and single servers should not follow a secondary server. This server polled: server_name. The time exchange was ignored.

Source: TIMESYNC.NLM
Possible Cause: A Time Source List was configurated incorrectly. A Single Reference, Primary, or Reference server was instructed to synchronize to a Secondary server. This error only results from a custom configuration. It cannot occur when SAP is used.
Action: Check the Time Source List in the TIMESYNC.CFG file for each Primary and Reference server. The order of servers in the list determines the polling order. Secondary servers should never be listed.

TIMESYNC-X-114: Synchronization Radius less than number will prevent synchronization.

Source: TIMESYNC.NLM
Explanation: The Synchronization Radius parameter is set to a value lower than the current correction floor setting for the TIMESYNC.NLM. The default synchronization radius is 2000 milliseconds; the default correction floor setting is 1 millisecond. (The correction floor parameter can be changed, though normally it should not be.)
Action: Set the Synchronization Radius parameter to a value higher than the correction floor setting. A value of 1000-2000 milliseconds (1-2 seconds) or higher is usually adequate.

TIMESYNC-X-129: Synchronization Radius less than number will prevent synchronization.

Source: TIMESYNC.NLM
Action: See message TIMESYNC-X-114: Synchronization Radius less than number will prevent synchronization..

TIMESYNC-X-133: Cannot allocate timer 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 NW 6.5 SP8: Server Operating SystemAdministration Guide.

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 NW 6.5 SP8: Server Operating SystemAdministration 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.