IBM Support

License Troubleshooting Guide

Question & Answer


License Troubleshooting Guide


If you have problems setting up your DOORS licensing, there are a few things you can try which may help you to resolve the problem and which will at least help you to gather the information that support will require from you if you need to contact support.

As license servers are the most complicated to set up, this guide concentrates on troubleshooting problems in client/server license setups.

  • Do you receive a license error when you try and run DOORS? If so, what is it?
  • Do you have a license server or a standalone license? A server license will contain a server line that will be similar to the following:
    SERVER servername 0090271323da 19353
  • If the License file is a server license, check the server name and the Mac Address, Disk Volume Serial Number, or IP Address. Make sure these parameters are correct for this machine (select Start > Program files > Teleleogic > DOORS 7.0 > Tools > License Utility > System Settings tab).
  • In the License file (license.dat) check the Daemon path (note it should be using the 8.3 naming convention). Example:
    DAEMON telelogic C:\progra~1\telelo~1\doors7\bin\telelogic.exe

Environment Variable

  • Check the Environment variable. On NT, Windows 2000 and Windows XP, ensure that the LM_LICENSE_FILE variable is under the System Variable section.
  • In order to set the environment variable in the System Variable section, you must be logged in as the Administrator of the local machine (NT, Windows 2000, XP) when you complete the license set up procedure.
  • This variable will either take the form of a physical path to the license file OR port@host i.e. 19353@ servermachine. Where '19353' is the default port used and 'servermachine' is the name of the license server.
  • This environment variable has to be set on both the license server machine and all DOORS client machines that connect to the license server.

Windows 2000/XP

To access the environment variables on a Windows 2000 or XP machine, on the desktop right click on the My Computer Icon. On the popup menu select Properties. Now select the Advanced Tab. On this tab select the Environment button.

Windows NT
To access the environment variables on a Windows NT 4.0 machine, on the desktop right click on the My Computer Icon. On the popup menu select Properties. Now select the Environment Tab.
Note: The license file variable can point to more than one server. Entries will be separated by a semicolon.

Flexlm License Utility

The flexlm utility (installed with either a license server OR standalone installation (can be found at Start > Program files > Telelogic > DOORS > DOORS Tools > License Utility) is a tool that helps determine what, if any, license errors there are and it provides useful diagnostics as to where the problem lies.

Things to check using the Flexlm License Utility:

  • Select Start > Programs > Telelogic > DOORS 7.0 > Tools > License Utility
  • Then select the Service/License File tab
  • If you have a license server, ensure that the 'Configuration Using Services' radio button is selected.
  • Note that the tab options available will change when you have selected this radio button.
  • 'Server diagnostics' allows the diagnosis of problems when users are unable to checkout licenses.
  • To do this on the License utility tool select the 'Server Diagnostics' tab and click the 'Perform Diagnostics' button.
  • If the features in this license are correct and the licenses can be checked out, this utility should report that 'This license can be checked out'.
  • If the license cannot be checked out, record the error message that is given and contact your local Telelogic DOORS Support department.
  • Select the 'Server Status' tab
  • Click on the 'Perform Status Enquiry' button.
  • If the license server is up and running, the server status will report that both the license server and vendor daemon (in this case 'telelogic') are both UP.
  • If an error message is reported after performing a status enquiry, please record the message and contact your local Telelogic DOORS Support department.
  • If the license server has not started click on the 'Start/Stop/Reread' tab and click on the 'Start Server' button.
  • If the license server does not start it is always useful to try starting the service from a command prompt.
  • To do this, open a command prompt, navigate to your flex directory, type the following: (from the DoorsHome\doors\flex dir)
    lmgrd -app -c c:\progra~1\telelo~1\doors~7\lib\license.dat
  • You will either be able to start the service or will get a more detailed error message. If you receive an error, you should then report this to local Telelogic DOORS support team.

Other things to check with server licenses

  • Make sure you have upgraded the license server to Flex v8 for DOORS 7. The relevant installation of DOORS will install the correct versions of the license server.
  • Make sure the client can ping the server and that the server can ping the client.
  • If a client is trying to connect to a license server, use telnet to test the connectivity to the license server. Select start -> run. Type telnet servername portnumber . An example would be telnet DOORSserver 19353
  • Make sure you are logged on as the Local Machine Administrator when running license setup.
  • The debug log file (Telelogicflex.log) captures license errors and is a useful tool in diagnosing license problems. This can viewed while running the license utility.  Select the "Config services" tab and select the "View Log" button.  The default location for this file is in DOORSHOME\flex directory. If the file is not already present you can manually create it.

[{"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Business Unit":{"code":"BU005","label":"IoT"},"Component":"General Information","Platform":[{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.3","Edition":""}]

Historical Number


Document Information

Modified date:
16 June 2018