Q100105: How to generate a License Diagnostic file
If you are encountering any problems with your licenses and cannot resolve the problem using the information in Licensing Online User Guide or the Support Portal Licensing Help section then please generate a Diagnostic File from the Foundry Licensing Utility (FLU) and send it to us on a Support ticket.
NOTE: For problems with floating licenses, please generate an FLU Diagnostic file from BOTH the license server and a client machine running the application.
The FLU can create a license diagnostic file for a machine to help with troubleshooting licensing problems. A diagnostic files includes lots of useful information about the licensing setup such as
- The machines hostname, System ID and IP address
- Any license files installed on the machine and whether they are valid or not
- If the server tools are installed
- Server log files and license error log files
- Advanced license setup info such as licensing environment variables and server options files
No personal information is gathered.
Saving a diagnostic file from Foundry Licensing Utility (FLU) 8.0
FLU 8.0 in GUI mode
- Launch the FLU
- Go to the Help tab and click on Create Report in the Diagnostics Report panel
- Click Save Report to write out the diagnostic file to send to support
FLU 8.0 in command line mode
- Open a terminal or command prompt and run one of the following commands:
C:\Program Files\FoundryLicensingUtility\bin\FoundryLicenseUtility.exe -d
or if the FLU was only installed for your user:
- The tool will prompt you to save a text file. Enter Y to save it.
How to Create a Support Ticket
Please then send the file(s) to us, along with a description of the problem you are encountering, by creating a support ticket using the "Create a Ticket" link on the top of the Support Portal Page.
NOTE: The "Create a Ticket" button will only be visible when you are logged in to the Support Portal.
License Troubleshooting Tutorial
For more information about licensing please see the Foundry Licensing Online Help
We're sorry to hear that!Please tell us why.