Previous Contents Index

LIC0055: Warning: The following license servers failed to provide service: name (Timeout error)
name (Name is unknown) name (Failed to respond)

Advanced Server for OpenVMS

Advanced Server for OpenVMS
Guide to Managing Advanced Server Licenses

For the connections that failed due to timeout, it may help to increase the timeout value. The current timeout value is n seconds
Explanation: The named license servers advertised their services on the LAN, but did not respond when asked for services.


User Action: For timeout errors it may be appropriate to increase the timeout period using the method described in the message. For other errors or if the timeout period is already greater than 30 seconds, it may help to restart the named servers.

LIC0057: A NetBIOS CANCEL command failed to cancel a CALL command. Contact the vendor of the network protocol stack on LANAn to see if a fix for this problem is available
Explanation: To provide the fastest possible service, connections to the license server are tried on all network transports at the same time and the first transport to successfully connect is used. The connection attempts on the other transports, if any, are not needed and are canceled. Some network protocol stacks have an error in the way they handle this cancel operation, which causes the cancel to fail (the connection attempt continues). When this happens, the Client Requester program has to wait for those connection attempts to complete. This adds delays to the operation of the Client Requester program.
User Action: This is a problem in the network protocol stack. Check with the vendor of the network protocol stack associated with the LANA number shown to see if they have a newer version of the network protocol stack which fixes this problem.

LIC0058: Warning: license server name failed to respond to a request within the n seconds provided
Explanation: This is a problem in the network protocol stack. Check with the vendor of the network protocol stack associated with the LANA number shown to see if they have a newer version of the network protocol stack that fixes this problem.
User Action: It may be appropriate to increase the timeout period. If the timeout period is already greater than 30 seconds, it may help to restart the named license server.

LIC0060: Warning: The license server name is not available to validate the license it assigned you for product. The license was last validated n days ago date and is still valid
Explanation: One of your licenses has not been validated for over a week. It may be that the license server that provided your license has changed names or has been removed from the network.
User Action: If the license server is supposed to still be in service, it may be appropriate to restart the license server. If the license server has been renamed or removed, delete the PWLICLM.DAT license data file and restart the client. This should allow you to acquire a license from a working license server.

LIC0061: License file %s read failed

LIC0062: License file %s ID not valid

LIC0063: License file %s version number not valid
Explanation: The PWLICLM.DAT license data file has bad data in it. The data will be recovered from the license servers on the network and the file will be rewritten.
User Action: No action required.

LIC0065: Failed to get a valid address for client, datalink error n
Explanation: The DataLink Layer returned an unexpected error code.
User Action: Reinstall the network device driver.

LIC0066: Only one license server name allowed on command line name
Explanation: Any text on the command line that does not start with a "/" character is considered to be a license server name. Only one such name is allowed on the command line.
User Action: Check the command line and try again.

LIC0067: Command line switch actual is ambiguous. Did you want possible?
Explanation: Command line switches can be abbreviated, but enough letters must be provided so that only one possible switch will match. The switch shown was too short and matches the start of two or more possible switches. The message is repeated to show all the possible matches.
User Action: Extend the abbreviation enough to uniquely specify the switch.

LIC0068: Command line switch switch overrides earlier switch switch
Explanation: Some command line switches cannot be used together: "/SHOW," "/PWACCESS," "/NOCONNECTION," and "/SERVERS." The switches shown in the message were both specified on the command line and only the last one specified will take effect.
User Action: Remove extra switches from the command line.

LIC0069: License server server sent a response with bad encryption
Explanation: License requests and responses are encrypted when sent on the network. A checksum is used to test data integrity. The named server sent a response that, after decryption, failed the checksum test. This usually means that the encryption key used by the license server did not match the decryption key used by the Client Requester.
User Action: It may be appropriate to restart the license server.

LIC0071: The date of last validation on the license product is date, but the current date set on this system is date. Check the date setting on this machine and on server
Explanation: Each time a license server validates a license, it provides the current date and time. If the validation date of a license is more than one day ahead of the current date on the client, it means that one or both of the systems have their date set wrong.
User Action: Check and correct the date on the client. If the date on the client is already correct, have the system manager of the license server correct the date on that machine.

LIC0090: DECCORE.VXD is not responding
Explanation: The protected-mode driver is not installed. The protected-mode version of the Client Requester program needs the services provided by DECCORE.VXD and cannot run without it.
User Action: Reinstall the Client Requester program. If that fails, reinstall PATHWORKS.

LIC0091: Could not start Protected Mode Licensing. This version of licensing must be used with Windows for Workgroups, Windows 95, or Windows 98. Use Real Mode Licensing for DOS and Windows 3.x
Explanation: The protected-mode version of the Client Requester program (INSTLICL.DLL) will only work with a protected-mode network. You cannot use INSTLICL.DLL with Windows 3.1 or with Windows for Workgroups and a Basic Redirector.
User Action: Reinstall PATHWORKS.

LIC0092: VNetBIOS is not responding
Explanation: The protected-mode version of the Client Requester program (INSTLICL.DLL) requires the protected-mode NetBIOS driver, VNetBIOS.
User Action: Reinstall the network.

LIC0093: DECLICL.VXD is not responding
Explanation: Reinstall the network.
User Action: Always load the Client Transponder program before the Client Requester program.
Windows for Workgroups: Reconfigure PATHWORKS.
Windows 95 and Windows 98: Remove and reinstall the network service "PATHWORKS Licensing Agent."

License for product_name is in use by another client
Explanation: The license is being used by another client. A client license may be used by only one client at a time. The license has been deleted from this client.
User Action: Run the Client Requester program again to obtain a new license if one is needed.

License for product_name is not valid
Explanation: The license previously obtained by the Client Requester program has been invalidated by the license server.
User Action: Check with your system administrator to determine the reason that your license has been invalidated. You may run the Client Requester program on the client again to obtain a new license if necessary. Note that the Client Requester program does not try to obtain a new license automatically when a license is invalidated.

License for product_name successfully verified
Explanation: The Client Requester program successfully verified the license.
User Action: None required.

License server server-name is not available to satisfy request
Explanation: The Client Requester program could not establish a session with the license server specified.
User Action: Make sure that the license server is running on that node and that it is running the same transports as the client.

License successfully obtained
Explanation: The Client Requester program successfully obtained a license.
User Action: None required.

Scanning network...
Explanation: The Client Requester program queries all license servers on the LAN to determine if the client has already been allocated a license from the license server.
User Action: None required.

Searching for license servers...
Explanation: The Client Requester program must search the LAN for a license server. To shorten this process, you may enter the name of the license server on the command line.
User Action: None required.

Time-out value set to n seconds
Explanation: The time-out default was overridden by a value entered on the command line.
User Action: None required.

Unable to verify license for product_name
Explanation: The Client Requester program failed to verify the license. This may be caused by several reasons:


User Action: The license on the client is assumed to be valid and is loaded in the Client Transponder program. The client should determine if the license server is running and using the same transport, or if a network problem is inhibiting communication.

Verifying license
Explanation: If the Client Requester program detected a previous license stored on the client, it tries to verify the license with the license server from which it was obtained.
User Action: None required.

Appendix B
Server Messages

This appendix explains the event messages that are logged to the license server and License Registrar log files as well as the Event Logger (ADMIN/ANALYZE). It provides the license server messages, an explanation of these messages, and corrective action if appropriate and includes the following topics:

B.1 License Component Log Files

Log files are stored in a directory defined by the PWRK$LOGS logical name. The two types of log files are:

B.1.1 License Processing-Related Log Files

The names of the license processing-related log files are as follows:

B.1.2 License Component Program Log Files

The names of the license component program log files are as follows:

B.2 License Server Events

This section describes events logged to the OpenVMS license server log file (PWRKS$LOGS:PWRK$LICENSE_SERVER_name.LOG). Note that all the messages posted to the log file begin with a date/timestamp.

ALERT_LEVEL_REACHED:
Product = product-name Group = group-name Alert Level = alert-level-number Allocation = number-of-licenses-allocated
Explanation: The number of licenses currently in use for this product exceeds the alert level. If the group-name is <none>, the alert level for all the product's licenses has been exceeded. Otherwise, the alert level for the licenses in the specific group has been exceeded.
User Action: Review the current license distribution. Remove licenses from clients that no longer use the product, redistribute the available product licenses, or add new product licenses.

CLIENT_ADDRESS_CHANGE:
Client Id = client-id-number Old Client Addr = old-address New Client Addr = new-address
Explanation: The current client's address is different from when the license was assigned. Typically, this message indicates a license has been moved from one client to another.
User Action: Make sure that the change of client ID is valid.

CLIENT_ID_CHANGE:
Client Id = client-id-number Old Client ID = old-id New Client ID = new-id Old Client Addr = old-address New Client Addr = new-address
Explanation: The current ID of the client is different from the ID it had when the license was assigned. The client ID is the address of the Ethernet adapter. Typically, this message indicates that a license has been reassigned from one client to another.
User Action: Make sure that the Ethernet address change is valid.

CLIENT_LICENSE_ASSIGNED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name
Explanation: A product license was granted to the client from the group specified.
User Action: None required.

CLIENT_LICENSE_DENIED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name Reason = explanation-string
Explanation: The client's request for assignment of a license could not be processed as requested.
User Action: If the reason is an incorrect product or group, check to be sure the license type exists and reconfigure the client to obtain a valid license. If there are not enough licenses, the administrator must add, reallocate, or remove licenses to create available ones.

CLIENT_LICENSE_INVALID:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name Reason = explanation-string
Explanation: The license presented for verification to the license server by the client is no longer valid.
User Action: If the reason is an incorrect product, group, or license, the data on the client may no longer be valid (for example, the group may have been deleted) and the license may have been revoked. Reboot the client to obtain a valid license. If the license is in use by another client, this may be a case of illegal copying of license data between clients and should be investigated.

CLIENT_LICENSE_RELEASED:
Client ID = client-id-number Client Addr = client-address Product = product-name Group = group-name
Explanation: The system manager released the product license from the specified group.
User Action: None required.

CLIENT_LICENSE_REVOKED:
Client ID = client-id-number Client Addr = client-address Product = product-name Group = group-name Reason = explanation-string
Explanation: The product license from the specified group was revoked or removed. The reason string indicates whether it was due to an action taken by the License Manager, or due to changes in the OpenVMS License Management Facility (LMF) database. This action can explain why a client's license is considered invalid in a later log event.
User Action: You may have to add, reallocate, or remove currently allocated licenses to allow this client to use the file server in the future.

CLIENT_LICENSE_UPGRADE_ON_ASSIGN:
Client Id = client-id-number Client Addr = client-address Transport = transport-name Group = group-name V5 Product = version-5-product-name, for example PWLMDOSCC06.00 Product = product-name, for example, PWLMXXXCA06.00
Explanation: The client requested a PWLMDOSCC06.00 license and the license server has defined the logical so the license server upgraded and assigned the PWLMXXXCA06.00 license. The license returned to the client will be a virtual license. (See the description under Explanation for message, VIRTUAL_CLIENT_LICENSE_RETURNED_ON_ASSIGN.)
User Action: None required.

CLIENT_LICENSE_VALID:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name Reason = explanation-string
Explanation: The license presented for verification to the license server by the client is valid.
User Action: None required.

CLIENT_NOT_LICENSED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Reason = explanation-string
Explanation: The client is not licensed to access the file server. The client does not have a client-based license that grants it the right to access the services provided by the file server and there are no server-based licenses available for the License Registrar to assign to the client to give the client access rights to the file server.
User Action: Either configure the client to acquire a client-based license to access the file server or make server-based licenses available on the file server system which can then be used to license the client.

FATAL_ERROR:
module-name: module-name and explanation-string
Explanation: An irrecoverable error has occurred that will cause the license server to terminate. The message may return the name of the module in which the error occurred and an explanation of the possible cause.
User Action: Notify your Compaq Computer Corporation service representative or local authorized reseller. Please save the log file so that it may be used to help diagnose the problem.

INIT_LOGFILE:
Reason = explanation-string
Explanation: A new version of the log file was created. The reason string indicates whether it was done because the server started, or because of a License Manager request.
User Action: None required.

MESSAGE: message-text
Explanation: The message displayed describes diagnostic log event information.
User Action: None required.

SERVER_STATE_CHANGE:
Old State = previous-state-name New State = new-state-name Reason = explanation-string
Explanation: The license server has been either enabled to serve the client requests or disabled. The reason always indicates that it was at the request of the License Manager.
User Action: None required.

VIRTUAL_CLIENT_LICENSE_RETURNED_ON_ASSIGN:
Client Addr = client-address Group = group-name Product = product-name Virtual Product = virtual-product
Explanation: The license requested by the client was a LAN Manager license, for example, PWLMDOSCC06.00. The license software looks for a higher version of the product than requested either through license version lookup (described in Section 3.3, Controlling License Version Lookup) or license upgrade (described in Section 2.5.1, Upgrading Client Licenses. A license was assigned to that client, for example, PWLMXXXCA06.00. Since the client will only accept a license name in the format of the license requested, the license server returns a "virtual license" to the client that conforms to the original format requested. So the virtual license returned is in the form, PWLMDOSCC07.00. The client will accept it as simply a higher version of the PWLMDOSCC06.00 that it requested.
User Action: None required.

Previous Next Contents Index