53.0 Policy Manager Messages
The following includes messages from POLIMGR.NLM.
POLICY MANAGER-(X-1): Unable to get a resource tag for the policy manager. There may be a memory problem.
Source:
POLIMGR.NLM
Explanation:
The operating system is unable to allocate a resource tag.
Action:
Reboot the server.
POLICY MANAGER-(X-2): Unable to get the memory resource tag for the policy manager. There may be a memory problem.
Source:
POLIMGR.NLM
Explanation:
The operating system is unable to get a memory resource tag.
Action:
Reboot the server or add more memory to the server.
POLICY MANAGER-(X-3): Unable to get the event resource tag for the policy manager.
Source:
POLIMGR.NLM
Explanation:
The operating system is unable to get an event resource tag.
Action:
Reboot the server.
POLICY MANAGER-(X-4): Unable to get an AES event tag for the policy manager. There may be a memory problem.
Source:
POLIMGR.NLM
Explanation:
There is a problem in registering for an event.
Action:
Reboot the server or add more memory to the server.
POLICY MANAGER-(X-5): Unable to register policy manager function.
Source:
POLIMGR.NLM
Explanation:
The license service is unable to register with the server operating system.
Action:
Reboot the server.
POLICY MANAGER-(X-6): Unable to get memory to do network connection licensing.
Source:
POLIMGR.NLM
Possible Cause:
The server is low on memory.
Action:
Unload an NLM or add more memory.
POLICY MANAGER-(X-7): License update request challenge response for a server base license failed. Failure occurred on server servername.
Source:
POLIMGR.NLM
Explanation:
The validation of the LicenseUpdateRequest failed.
Possible Cause:
The SERVER.EXE file does not match the license certificate for a server base license. You might have a beta version of SERVER.EXE but a shipping version of the license certificate.
Action:
Get the correct SERVER.EXE file or version or the correct license certificate.
POLICY MANAGER-(X-8): The challenge on a response to license updates on connection licenses failed.
Source:
POLIMGR.NLM
Explanation:
The validation of the LicenseUpdateRequest failed.
Possible Cause:
The SERVER.EXE does not match the license certificate for connection licenses. You might have a beta version of SERVER.EXE but a shipping version of the license certificate.
Action:
Get the correct SERVER.EXE file or version or the correct license certificate.
POLICY MANAGER-(X-9): License validation failed due to lack of memory.
Source:
POLIMGR.NLM
Possible Cause:
The server is low on memory.
Action:
Unload an NLM or add more memory.
POLICY MANAGER-(X-10): License validation failed due to lack of memory.
Source:
POLIMGR.NLM
Possible Cause:
The server is low on memory.
Action:
Unload an NLM or add more memory.
POLICY MANAGER-(X-11): Connection license certificate is not valid.
Source:
POLIMGR.NLM
Possible Cause:
A license certificate is corrupted.
Action:
Reinstall the license certificate.
POLICY MANAGER-(X-12): Unable to get the connection license to complete the license validation.
Source:
POLIMGR.NLM
Possible Cause:
The LSQuery call failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-13): Unable to request a connection license. (Can’t create Challenge) due to a problem on server servername.
Source:
POLIMGR.NLM
Explanation:
There aren’t enough resources to verify consumption of licenses.
Possible Cause:
The operating system might have failed.
Action:
Reboot the server.
Possible Cause:
The server doesn’t have enough memory.
Action:
Add more memory.
POLICY MANAGER-(X-13): Unable to get a connection license. The Challenge Check Response failed on server servername.
Source:
POLIMGR.NLM
Explanation:
The server doesn’t have enough resources to check the challenge.
Possible Cause:
The operating system might have failed.
Action:
Reboot the server.
Possible Cause:
The server doesn’t have enough memory.
Action:
Add more memory.
POLICY MANAGER-(X-15): Unable to obtain a network connection license. Operation will continue. Please contact your network administrator.
Source:
POLIMGR.NLM
Explanation:
A background check for licenses failed in a soft stop environment.
Possible Cause:
Not enough licenses are installed.
Action:
Install additional licenses.
Possible Cause:
Licensing services failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-16): The licensing services are not available for this server. Please make sure the NLSLSP.NLM is loaded.
Source:
POLIMGR.NLM
Explanation:
The licensing service (NLSLSP.NLM) is not running.
Action:
Load NLSLSP.NLM.
Possible Cause:
Licensing services are not installed on the server.
Action:
Run SETUPNLS.NLM for NLS 3.0 or 3.4. Run EZNLS.EXE for NLS 5.0.
POLICY MANAGER-(X-18): The connection license or the activation key for the connection license has become corrupt. Please remove and reinstall the connection license(s).
Source:
POLIMGR.NLM
Explanation:
The activation key for the license certificate is invalid.
Possible Cause:
If the activation key is not embedded (and you had to enter the key manually), you might have incorrectly entered one or more characters.
Action:
Reinstall the license or get an envelope that has the correct activation key.
POLICY MANAGER-(X-19): Unable to get a connection license.
Source:
POLIMGR.NLM
Explanation:
A licensing error occurred while getting a connection license.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-23): Server servername was unable to obtain a valid server base license. Connection to this server is not allowed. Please contact your network administrator.
Source:
POLIMGR.NLM
Explanation:
The server cannot obtain a server base license.
Possible Cause:
The license certificate does not have a server assignment.
Action:
Make a server assignment.
Possible Cause:
A server base license is not installed.
Action:
Install the license.
Possible Cause:
Licensing services failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-24): The NLS licensing services are not available for server servername. Please make sure the NLSLSP.NLM is loaded.
Source:
POLIMGR.NLM
Explanation:
The licensing service (NLSLSP.NLM) is not running.
Action:
Load NLSLSP.NLM.
Possible Cause:
Licensing services are not installed on the server.
Action:
Run SETUPNLS.NLM for NLS 3.0 or 3.4. Run EZNLS.EXE for NLS 5.0.
POLICY MANAGER-(X-26): The server base license or the activation key for the server base license, requested for server servername, is corrupt. Please remove and reinstall the server base license(s).
Source:
POLIMGR.NLM
Explanation:
The activation key for the license certificate is invalid.
Possible Cause:
If the activation key is not embedded (and you had to enter the key manually), you might have incorrectly entered one or more characters.
Action:
Reinstall the license or get an envelope that has the correct activation key.
POLICY MANAGER-(X-27): Unable to get a server base license for server servername.
Source:
POLIMGR.NLM
Possible Cause:
A server base license is not installed.
Action:
Install the license.
Possible Cause:
Licensing services failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-28): Server base license validation for server servername failed due to lack of memory.
Source:
POLIMGR.NLM
Explanation:
The server was unable to allocate memory.
Possible Cause:
The server does not have enough memory.
Action:
Add more memory.
Possible Cause:
The operating system failed.
Action:
Check the operating system.
POLICY MANAGER-(X-29): Server base license validation for server servername failed due to lack of memory.
Source:
POLIMGR.NLM
Explanation:
The server was unable to allocate memory.
Possible Cause:
The server does not have enough memory.
Action:
Add more memory.
Possible Cause:
The operating system failed.
Action:
Check the operating system.
POLICY MANAGER-(X-30): Server base license certificate used to get a license for the server servername is not valid.
Source:
POLIMGR.NLM
Explanation:
The digital signature on the server base license certificate is corrupted or invalid.
Possible Cause:
SERVER.EXE does not match the license certificate for a server base license. You might have a beta version of SERVER.EXE but a shipping version of the license certificate.
Action:
Install the correct SERVER.EXE file or version or the correct license certificate.
POLICY MANAGER-(X-30): Number users failed to obtain a network connection license when connecting to server servername. Operation will continue. The network administrator needs to investigate this problem.
Source:
POLIMGR.NLM
Explanation:
A licensing request failed.
Possible Cause:
No license certificate is installed.
Action:
Install the license certificate.
Possible Cause:
Licensing services failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-31): Unable to get the server base license certificate for server servername to do the license validation.
Source:
POLIMGR.NLM
Explanation:
The LSQuery call failed during validation.
Possible Cause:
Licensing services failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-32): Unable to get a server base license for server servername due to the Check Response failure.
Source:
POLIMGR.NLM
Explanation:
Check Response failed while requesting a server base license.
Possible Cause:
The license certificate is corrupted or an incorrect version.
Action:
Reinstall the certificate.
Action:
Get and install the correct certificate.
Possible Cause:
SERVER.EXE does not match the license certificate.
Action:
Install the correct version of SERVER.EXE.
POLICY MANAGER-(X-45): Unable to register a call-back to the policy manager to load the NLSLSP.NLM.
Source:
POLIMGR.NLM
Explanation:
The server is unable to schedule an asynchronous process to load NLSLSP.NLM.
Possible Cause:
The operating system failed.
Action:
Verify operating system functionality.
POLICY MANAGER-(X-46): Unable to create the connection license Request and Release table.
Source:
POLIMGR.NLM
Possible Cause:
The server is low on memory.
Explanation:
Add more memory.
Possible Cause:
The operating system failed.
Action:
Verify operating system functionality.
POLICY MANAGER-(X-46): Unable to increase the size of the connection license Request and Release table.
Source:
POLIMGR.NLM
Possible Cause:
The server is low on memory.
Explanation:
Add more memory.
Possible Cause:
The operating system failed.
Action:
Verify operating system functionality.
POLICY MANAGER-(X-47): Unable to allocate memory for the policy manger procedures on server servername. The network administrator needs to investigate this problem.
Source:
POLIMGR.NLM
Explanation:
A memory problem has occurred.
Action:
Unload an NLM or add more memory.
POLICY MANAGER-(X-49): Unable to get a connection license. The Challenge Response Check failed due to lack of memory on server servername.
Source:
POLIMGR.NLM
Explanation:
The server was unable to allocate memory.
Possible Cause:
The server does not have enough memory.
Action:
Add more memory.
Possible Cause:
The operating system failed.
Action:
Check the operating system.
POLICY MANAGER-(X-49): Unable to do a license update on the server base license due to lack of memory. Failure occurred on server servername.
Source:
POLIMGR.NLM
Explanation:
The server was unable to allocate memory.
Possible Cause:
The server does not have enough memory.
Action:
Add more memory.
Possible Cause:
The operating system failed.
Action:
Check the operating system.
POLICY MANAGER-(X-49): Unable to do a license update on connection licenses due to lack of memory. Failure occurred on server servername.
Source:
POLIMGR.NLM
Explanation:
An error occurred concerning updating the status of licenses.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-85): Unable to register a Server Down notify event for the policy manager.
Source:
POLIMGR.NLM
Explanation:
NLS is unable to register for an OS event.
Action:
Reboot the server.
POLICY MANAGER-(X-89): Server servername was unable to obtain a valid server base license.
Source:
POLIMGR.NLM
Explanation:
The server base license is corrupted.
Action:
Reinstall the server base license.
POLICY MANAGER-(X-94): The server servername was unable to import an NLS API.
Source:
POLIMGR.NLM
Possible Cause:
LSAPI.NLM is not running.
Action:
Make sure that the NLS libraries (NLSAPI.NLM and LSAPI.NLM) are running on the server.
POLICY MANAGER-(X-95): The server servername is running without a server base license.
Source:
POLIMGR.NLM
Possible Cause:
During the Novell Installation Services installation, the Install without Licenses check box was checked, and no server base license was installed.
Action:
Install a server base license.
POLICY MANAGER-(X-98): Unable to import NLS public symbols on server servername.
Source:
POLIMGR.NLM
Possible Cause:
NLSAPI.NLM is not running.
Action:
Make sure that the NLS libraries (NLSAPI.NLM and LSAPI.NLM) are running on the server.
POLICY MANAGER-(X-99): Unable to request a connection license because there is no connection license policy name. The server base license for server servername probably has not been installed yet.
Source:
POLIMGR.NLM
Explanation:
The server has not obtained a server base license.
Possible Cause:
The server base license is not installed.
Action:
Install the license.
Possible Cause:
The license certificate is corrupted.
Action:
Reinstall the license.
Possible Cause:
Licensing services failed.
Action:
Verify NLS functionality by using NLSTRACE.
POLICY MANAGER-(X-100): WARNING: The evaluation connection license licensename currently in use will expire on date.
Source:
POLIMGR.NLM
Explanation:
An evaluation license is being used.
Action:
Order and install permanent licenses.
POLICY MANAGER-(X-101): Eval license notification failed due to lack of memory.
Source:
POLIMGR.NLM
Possible Cause:
A memory problem occurred.
Action:
Unload an NLM or install additional memory.
POLICY MANAGER-(X-A): Unable to alloc connActionMutex.
Source:
POLIMGR.NLM
Possible Cause:
NLS is unable to request Mutex from the server operating system.
Action:
Reboot the server.
POLICY MANAGER-(X-A): Unable to alloc connLicRequestMutex.
Source:
POLIMGR.NLM
Possible Cause:
NLS is unable to request Mutex from the server operating system.
Action:
Reboot the server.
POLICY MANAGER-(X-A): Unable to alloc serverBaseLicMutex.
Source:
POLIMGR.NLM
Possible Cause:
NLS is unable to request Mutex from the server operating system.
Action:
Reboot the server.