Under Windows 95, Windows 98, and Windows NT, the licensing software components are protected-mode components:

• The client license transponder (CLT) is PNLT32.EXE.
• The client license requester (CLR) is PNLR32.EXE.

The CLR runs on any Windows 95, Windows 98, or Windows NT client computer and requests client-based licenses from the license server. Depending on the networking software on the client computer, you can use the Licensing Agent, as described in the PATHWORKS 32 User's Guide. To specify the licensing parameters, follow these steps:

1. Select Run from the Start menu.
2. Enter PNLCFG.

The field names shown in the Licensing Software Properties dialog box are listed in Table 5-5, Licensing Software Properties:

Table 5-5 Licensing Software Properties

Property Name	Description
Remote License Servers	Specifies license server names. This parameter is required for wide area network (WAN) configurations, where the license server is not in the same local area network (LAN) as the client computer. The named license servers will also be the first servers from which licenses are requested. For more information about configuring clients for wide area network access, refer to Section 5.3, Enabling Wide Area Networking (WAN) Operations.
License Group	Specifies the client's license group. Only licenses assigned to the named group will be used. If not specified, new licenses are requested from the group named "Default."
Select Licenses	Specifies the license PAK names of licenses to be requested, as described in the License Product Name Definition section in this guide. For example, enter: DEC-PWXXDOSAT06.00 DEC-PWLMXXXFP05.00
Timeout	Specifies the maximum time (in seconds) to allow for connecting for each license server request. The default timeout value is 5 seconds. When operations fail due to a timeout condition, an error message is logged.

To obtain a license over a dial-up connection, start the licensing software using the Run selection on the Start menu. Enter the following:

PNLR32

5.3 Enabling Wide Area Networking (WAN) Operations

Client computers outside of the local area network where the license server is running can request a license from the license server in one of the following ways:

• If the local server is acting as a WINS client, the WINS server resolves the license server name. Refer to your Server Administrator's Guide, for more information about how to set up the Advanced Server as a WINS client. This configuration is supported in Microsoft TCP/IP network environments on Windows 95, Windows 98, and Windows NT.
• If the client is using Microsoft TCP/IP, it may have an LMHOST file to map the NetBIOS name to the TCP/IP address, as described below.

This section provides information you need to configure licensing software on client computers that are not in the same local area network with the license server, but must acquire client-based licenses.

When the license server that is to provide client-based licenses is not on the same LAN as the client system, additional setup is required at the client system. The two required steps are:

1. Configure the WAN protocol stack (DECnet or TCP/IP) to map the license server's NetBIOS name (usually the node or host name with the prefix "PWRK$L") to the WAN address of the license server system.
2. Configure the licensing software components with the name of the license server.

In this step, you will give the WAN protocol stack the NetBIOS name of the license server and the WAN address of the license server system. The WAN protocol stack configuration steps depend on which WAN protocol stack is being used. The following sections describe the procedures for the commonly used WAN protocol stacks:

• DECnet
• Microsoft TCP/IP
• TCP/IP for OpenVMS

At the command prompt, issue the following command:

NCP DEFINE REMOTE-ADAPTER-NAME PWRK$Lname NODE decnet-address

For example, the license server system has a DECnet address of 12.345 and the license server name is "ZIPHED":

NCP DEFINE REMOTE-ADAPTER-NAME PWRK$LZIPHED NODE 12.345

5.4.1.2 Configuring Microsoft TCP/IP for WAN Licensing

Search for the file LMHOSTS. If it does not exist, search for the file LMHOSTS.SAM and make a copy in the same directory with the name "LMHOSTS."

Edit LMHOSTS using whatever text editor you like and add the following line:

address PWRK$Lname

For example, the license server system has a TCP/IP address of 12.34.56.78 and the license server name is "ZIPHED":

12.34.56.78 PWRK$LZIPHED

5.4.1.3 Configuring TCP/IP for WAN Licensing

At the command prompt, issue the following command:

INETNAME PWRK$Lname address

For example, the license server system has an IP address of 12.34.56.78 and the license server name is "ZIPHED":

INETNAME PWRK$LZIPHED 12.34.56.78

5.4.2 Configuring the License Server Name

Once the WAN protocol stack has been configured to map the NetBIOS name of the license server to the WAN address of the license server system, configure the licensing software with the NetBIOS name of the license server. The method to use depends on the client platform.

Configuring the License Server Name for DOS or Windows 3.1

Use the NetBIOS name of the license server on the PWLICLM.EXE command line. For example, if the license server name is "ZIPHED," run PWLICLM.EXE as follows:

PWLICLM PWRK$LZIPHED

Configuring the License Server Name for Windows for Workgroups

Edit the SYSTEM.INI file and add the following line to the [DECLICL] section:

LICENSESERVER=PWRK$Lname

For example, if the license server name is "ZIPHED," use the following:

LICENSESERVER=PWRK$LZIPHED

Configuring the License Server Name for Windows 95, Windows 98, or Windows NT

Run the program PNLCFG.EXE and add the license server to the list of "Remote License Servers" in the dialog box.

This appendix explains client licensing messages and describes corrective actions where appropriate and includes the following topics:

• Section A.1, Message that Results from Accessing the Server Without a License, describes the system error message you receive when you attempt to access the file server without a license.
• Section A.2, Messages That Result from Running the License Programs, describes the messages you receive when you run the Client Transponder or Client Requester programs.

In many of the messages, the user action involves running the Client Transponder or Client Requester programs.

If your client cannot obtain a client-based license, one of the following reasons may apply:

• The license server is not configured or running.
• The file server is not started.
• The file server is not configured or is incorrectly configured for the transport being used by the client.
• Required PAKs are not loaded and registered.
• There are no available licenses in the file server.

To prepare the license server:

1. Ensure that it is running and properly configured and that the client-based PAKs are registered and loaded in the LMF on the same system.
2. Ensure that licenses are available in the License Manager by reallocating or adding new ones.
3. Use the License Manager to check all occurrences of the server. These occurrences need a preceding qualifier: license server or file server, or file server and print server.
4. After preparing the license server, run the Client Requester program again.

If you access a file server without a license, you may be denied access or receive restricted access. You may receive the following message:

System Error 71: The network request was not accepted; or DOS error 58 has occurred.

For Windows NT, you may receive the following message:

System Error 71: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.

Explanation

1. If you have the Alerter service loaded, you may receive the following message:

   Connection attempt denied; server failed to authenticate a license for client

   
   Additionally, log entries in the event logger (ADMIN/ANALYZE) or Windows NT registry might reflect the denial or restriction of access to the server based on license authorization. See Section B.4, Event Logger (ADMIN/ANALYZE) Messages, for further details.

If you are denied access to a server:

• Verify that you have a client-based license, by executing the Client Requester program with a /SHOW switch, or ensure that you have sufficient server-based license capacity.
• If you do not have a client-based license, run the Client Requester program to acquire one, or register and load additional server-based license PAKs on your server system.

The following messages may be displayed on the client screen when you run the Client Transponder or Client Requester programs. If you get any of these messages, you may not have a license.

LIC0001: Unrecognized argument argument-passed
Explanation: The command line contains one or more arguments that are misspelled or incorrectly formatted.
User Action: Check the command line arguments.

LIC0002: Incompatible license versions
Explanation: Unexpected error from the Client Transponder program.
User Action: Update the Client Transponder program.

LIC0003: WARNING: The environment variable PCSA is not defined, but the PATHWORKS network scheduler (SCH) has been loaded
Explanation: Every PATHWORKS for DOS and Windows client should have the PCSA environment variable set to point to the directory where PATHWORKS is installed. The current client has the PATHWORKS network scheduler loaded, but does not have the PCSA environment variable set, so it appears to be an incorrectly configured PATHWORKS client.
User Action: Reinstall PATHWORKS on the client.

LIC0004: Not enough memory available for Client Transponder
Explanation: The Client Transponder program was unable to allocate memory for its internal buffers.
User Action: Unload any terminate-and-stay-resident applications (TSRs) already loaded and run the Client Transponder program again.

LIC0007: Unable to release excess memory
Explanation: The Client Requester program or Client Transponder program could not release memory that is not needed by the Client Transponder program.
User Action: Try running the Client Requester program from the DOS prompt. If memory management software is installed, try removing it and run the program again. Remove any TSRs from memory that can prevent DOS from freeing up memory.

LIC0008: Network software not loaded or problem configuring network
Explanation: The network is not running.
User Action: Be sure the network starts correctly before running the Client Transponder or Client Requester programs. If the problem persists, reinstall your network software.

LIC0009: All network sockets are currently in use
Explanation: The Client Requester program could not establish a connection with a license server because all network sessions are in use.
User Action: Configure the network software to allow more NetBIOS sessions.

LIC0010: License transponder already resident in memory
Explanation: An attempt was made to load the Client Transponder program, but it is already resident.
User Action: None required.

LIC0011: PATHWORKS transport client Client Transponder for platform (filename), is not in memory
Explanation: The Client Requester program was unable to contact the Client Transponder program.
User Action: Reinstall PATHWORKS on the client.

LIC0012: Unable to read license information in file drive:filename
Explanation: A read error occurred while reading the specified file. The Client Requester program will scan the network to recreate the license information.
User Action: None required.

LIC0013: No License servers are available to satisfy request
Explanation: The Client Requester program could not contact any license servers.
User Action: If there is a license server on the same LAN as the client, then there may be a problem in the network between the two, or they may not share a network protocol. If the license server is not on the same LAN as the client, such as when the client is a dial-up client or at a branch office, be sure to specify the name of the license server in the Client Requester program setup information. See Section 5.3, Enabling Wide Area Networking (WAN) Operations, for WAN setup.

LIC0014: Invalid time-out value specified n
Explanation: The timeout value entered on the Client Requester program command line is not number or is less than 1.
User Action: Use a numeric value of 1 or greater.

LIC0015: WARNING: The environment variable PWTPL is not defined. Since the license configuration template file cannot be found, the required licenses type will default to "Combined Client and Server" (CCS) and some information about this PATHWORKS client may be incorrect
Explanation: On a PATHWORKS for DOS and Windows client, the PWTPL environment variable should point to the license configuration template file. The system appears to be a PATHWORKS client, but the PWTPL environment variable is not set.
User Action: Reinstall PATHWORKS on the client.

LIC0016: Unable to open license configuration template file file
Explanation: The PWTPL environment variable is set, but the file it points to does not exist.
User Action: Reinstall PATHWORKS on the client.

LIC0017: Network name not set
Explanation: The LAN Manager Client Requester and Client Transponder programs must have the NetBIOS name set before execution.
User Action: Reinstall the network on the client.

LIC0018: Invalid path specified path. (Maximum length is 244 characters)
Explanation: The /NEEDED: (or /FILE:) command line switches either include no value or a value that exceeds the DOS limit.
User Action: Use a valid path.

LIC0019: Invalid license server specified server. (Maximum length is 47 characters)
Explanation: The license server node name cannot be longer than 47 characters.
User Action: Enter a valid license server name. Usually this is the node name (or cluster alias) of the system running the license server.

LIC0020: Invalid group specified group. (Maximum length is 20 characters)
Explanation: The group specified on the command line is illegal; the length cannot exceed 20 characters.
User Action: Use a legal license group name.

LIC0021: License server could not provide a license of type license type, assigned to license group groupname
Explanation: The license server specified in the setup information was unable to supply one or more of the licenses needed.
User Action: Check the server name, license type and license group for typographical errors. If the data is correct, check that all required WAN setup has been done. Check that the specified server has licenses of the needed type and group available.

LIC0022: Could not add license name to local tables
Explanation: The local NetBIOS name table is full.
User Action: Increase the size of the local name table and restart the network.

LIC0023: Could not retrieve station address
Explanation: The program could not retrieve the station address from the NetBIOS interface.
User Action: Ensure the network has started properly.

LIC0024: Could not post receive buffer
Explanation: The license program tried to post an asynchronous receive buffer and failed.
User Action: Increase the number of Network Control Blocks (NCBs) allowed.

LIC0025: Unexpected status code 0xhh from transponder
Explanation: The Client Transponder program returned a value that is not a known status code.
User Action: Check the version of the Client Transponder program.

LIC0026: License transponder is not loaded
Explanation: The Client Transponder program is not loaded. It must be loaded before the Client Requester program is loaded.
User Action: Run the Client Transponder program, then run the Client Requester program again.

LIC0027: Warning: could not post listen
Explanation: The license program tried to post an asynchronous listen and failed.
User Action: None. To make this warning less likely to occur, increase the number of simultaneous commands allowed.

LIC0028: Could not connect to license server node-name
Explanation: The program tried to connect to a license server on the specified node and failed.
User Action: Check to make sure that the license server is running on that node. For WAN connections, see Section 5.3, Enabling Wide Area Networking (WAN) Operations.

LIC0029: Could not shut down NetBIOS session
Explanation: The program tried to shut down a communication session with a license server that may already have been closed.
User Action: None required.

LIC0030: Could not send request to server node-name
Explanation: The program tried to send a request to the server and failed. This could be due to a session disconnect between the Client Requester program and the license server.
User Action: If no license was obtained, run the Client Requester program again. If the problem persists, notify your system or network administrator.

LIC0031: Could not post any listen commands
Explanation: The license program tried to post a number of asynchronous listen commands and failed.
User Action: The program exited because it could not post any listen commands. To make this less likely to occur, increase the number of simultaneous commands allowed.

LIC0032: Incompatible license records
Explanation: The Client Requester program could not load the license information into the Client Transponder program because the license records are incompatible.
User Action: Run compatible versions of the Client Requester and Client Transponder programs.

LIC0033: Not enough memory available for Client Transponder
Explanation: The Client Requester program could not load the license information into the Client Transponder program because there was not enough memory allocated by the Client Transponder program when it was loaded.
User Action: Load the Client Transponder program using the /L: switch, increasing the number of license slots allocated by the program from the default of 1 to the number of licenses to be requested by the Client Requester program.

LIC0034: Warning: The data file filename was created by a different version of the Client Requester program. Automatic update done
Explanation: The record format of the PWLICxx.DAT file was changed after PATHWORKS Version 5.1 for DOS and Windows. The old file cannot be used by the new Client Requester program, but the data will be recovered from the license servers on the network and the data file will be updated automatically.
User Action: No action required

LIC0035: Unable to write license information to file path. Unable to write license information to file path. The list of current licenses could not be saved. This will mean a slightly greater delay the next time you run the Client Requester program. Before then, please make sure the disk is write enabled and has at least count free bytes of disk space
Explanation: The license data file could not be created or could not be written.
User Action: Make sure that the disk is write enabled and contains at least count free bytes of disk space, and then run the Client Requester program again.

LIC0036: Not enough memory available to run program
Explanation: The Client Requester program requires about 100Kb memory.
User Action: Make sure that enough memory is available to run the program.

LIC0037: License server returned invalid license
Explanation: The license returned from the license server is not the one requested. The Client Requester program tries to release the invalid license.
User Action: At this point the client is unlicensed. Check to make sure that you have a license by running the Client Requester program with the /SHOW switch. This lists the licenses that the client has obtained from the license server. You may have to execute the Client Requester program again to obtain a license.

LIC0038: Unable to open user-supplied license file file-name
Explanation: The license override file supplied on the command line could not be opened.
User Action: Make sure that the path supplied is correct or that the license file is in the DOS PATH.

LIC0039: WARNING DECnet Wide Area Network not supported with this configuration. Check if node is defined in the DECnet database
Explanation: The Client Requester program tried to add the remote adapter name of the license server to the DECnet network database.
User Action: None, if the license server is on the same LAN as the client. If the license server is not on the same LAN as the client, make sure that the node name of the license server is defined in the DECnet network database.

LIC0040: Unable to communicate over network, increase number of simultaneous commands allowed by transport and number of sessions allowed by transport
Explanation: The license program could not communicate over the network.
User Action: The program exited because it could not post any listen commands. To make this less likely to occur, increase the number of simultaneous commands allowed.

LIC0041: Unable to obtain a license for product_name
Explanation: The Client Requester program could not obtain a license for product_name. Possible reasons for this are:

• The license server is beyond a router (is outside the LAN) and the WAN has not been set up.
• No license server on the LAN has the specific license being requested, possibly due to a typographical error in the requested license type or license group name.
• The specified license group either does not exist or has not been assigned any licenses of the specified type.
• A license server with the correct licenses installed exists, but is unable to communicate over the network.

• For license servers outside the LAN, see Section 5.4, Obtaining Client-Based Licenses Over WANs, for WAN setup instructions.
• If the license is being requested by name, check that the first three letters match the Producer code of the Product Authorization Key (PAK) and that the remaining letters match the Product code of the PAK.
• Check the spelling of the license group name against the spelling at the license server. Check that licenses of the requested type are assigned to the group.
• Check that the license server and the client share a network transport protocol (NetBEUI, DECnet, or TCP/IP). It may help to restart the license server.

LIC0042: Path location already specified
Explanation: You specified the /I:path switch more than once on the Client Requester program command line.
User Action: Enter the command again, specifying the switch only once.

LIC0043 License server is not available
Explanation: A license server name was specified, but that license server is not reachable.
User Action: Check the spelling of the license server name. If any other error occurred, check user actions for those messages. It may help to restart the license server.

LIC0044: Unable to obtain a license for product_name.
Explanation: See message LIC0041.
User Action: See message LIC0041.

LIC0045: NetBIOS Name Claim failed on LANAn; The name name is already in the local name table. Probably an earlier use of the Client Requester program did not complete correctly. Restart the system at your earliest convenience
Explanation: The Client Requester program needs a unique network name for use on the network. The name it uses is the client's node name with an "L" in place of the last character. This name was already in use by another program. Usually this means that the Client Requester program failed to release the name the last time it was run.
User Action: Restart the client to try again with an empty name table.

LIC0046: NetBIOS Name Claim failed on LANAn; the local name table is full. Configure to allow more names
Explanation: The Client Requester program needs a unique network name for use on the network. The name table for one of the network protocol stacks was already full so the new name could not be assigned.
User Action: Configure the network protocol stack using LANAn to allow for more names in its table.

LIC0047: NetBIOS Name Claim failed on LANAn; Your name name is being used by another node!
Explanation: The Client Requester program needs a unique network name for use on the network. The name it uses is the client's node name with an "L" in place of the last character. This name was already in use by another system. Usually this means that your NetBIOS name is not unique on the network.
User Action: Reinstall the network using a unique name.

LIC0048: NetBIOS Name Claim failed on LANAn; Network interface is too busy to handle the request
Explanation: General network error.
User Action: Restart the system.

LIC0049: NetBIOS Name Claim failed on LANAn; Too many pending commands. Try to configure to allow more
Explanation: The network protocol stack on LANAn has run out of table space it uses to keep track of pending operations.
User Action: Configure the network protocol stack for a larger table size.

LIC 0050: NetBIOS Name Claim failed on LANAn; Unexpected NetBIOS return code 0xhh.
Explanation: The Client Requester program needs a unique network name for use on the network. The network protocol stack on LANAn could not assign the name for some unknown reason.
User Action: Restart the system. If the problem persists, reinstall the network protocol stack.

Previous

Next

Contents

Index