4.1. Getting Additional License Debug Information

Use the following suggestions to display or generate additional error messages and debugging information.

  • View the licdebug file. The licdebug file is generated when you run an Ansys, Inc. application and resides in the .ansys subdirectory under the directory specified by the TEMP environment variable (Windows) or in the $HOME directory (Linux). The licdebug filename will vary depending on the product but will follow the format licdebug.<product>.242.out. For example:

    If a licdebug file already exists and is dated today, the information is appended. If it is dated before today, the existing file will be renamed with a .old extension and a new file will be started.

    • Mechanical APDL (Ansys): licdebug.ANS_SOLVER.242.out

    • Ansys Workbench: licdebug.ANS_WB.242.out

    • Mechanical: licdebug.MECH.242.out

    • Ansys Fluent: licdebug.FLUENT_SOLVER.242.out

    • Ansys Polyflow: licdebug.POLYFLOW.242.out

    • Ansys CFX-Pre: licdebug.CFX_PRE.242.out

    • Ansys CFX Solver: licdebug.CFX_SOLVER.242.out

    • Ansys CFD-Post: licdebug.CFD_POST.242.out.

    • Ansys ICEM CFD (includes AI*Environment): licdebug.ICEM_AM.242.out

    • Ansys Icepak: licdebug.ICE_PAK.242.out

    • Ansys LS-DYNA: licdebug.DYNA_SOLVER.242.out

    • Connection functionality: licdebug.ANS_PM.242.out

    Note:  The license debug file names include the current release of the application. Because not all applications are updated with each release, it is possible to have lic\debug file names that are appended with older release numbers. For example, it is possible to be running Ansys Release 16.1 but still have a product license debug log file name include 160 as in licedbug.POLYFLOW.160.out.

    The directory specified by the TEMP environment variable may be hidden on your system. To view the directory and file, click My Computer. Choose Tools from the menu, and then click Folder options. Click the View tab and select Show hidden files and folders. Click OK.

If after following these suggestions, the resulting debug information does not make sense, try these suggestions:

  • Confirm that the license manager was restarted or the license file was reread after any changes were made to the license file. If you did not make any changes to the license file for the server, check the date/time that it was last changed. Get the relevant path information from the debug output. Also, confirm that the same path is being used.

  • Try restarting the license manager and then attempt to run again. See if the same situation occurs.

  • If you installed a new license file but are not seeing it even after restarting the license manager, confirm that the correct license file is being used to start the license manager. In this case, neither the client application nor the license manager is using the changed file. Also confirm that if site or user license preferences were set, the preferences were updated with the new license information.

  • If the ansyslmd.lic file is at the end of the path and it is a license file that uses the license manager daemon/service, then confirm that the license manager is started with the same path as the ansyslmd.lic file's path. The license manager could be looking at one file in the client application but the license manager daemon/service was started with another file.