Unexpected demo mode or MGLS EXCLUDE errors in the Installed Options and Suite Configuration dialogs

Document created by andrew_audova on Mar 9, 2012Last modified by andrew_audova on Mar 9, 2012
Version 2Show Document
  • View in full screen mode

(See attached files for sample error messages)

The first step is to make sure you do NOT have the MGLS_INCLUDE_LICENSES or MGLS_EXCLUDE_LICENSES environment variables set. If so, unset them. How to set or edit an environment variable on Windows

IMPORTANT NOTE: The MGLS_INCLUDE_LICENSES and MGLS_EXCLUDE_LICENSES environment variables should ONLY be set inside an invocation (wrapper) script - typically in batch script or VBScript which then invokes the application - otherwise they can be easily forgotten resulting in critical licensing problems due to the restrictions that these variables impose on eligible licenses.


If you are using the PADS Suite Configuration functionality (PADS9.4 introduces functionality to control PADS Suite license consumption):

The PADS Suite Configuration dialog will appear after clicking through the licensing errors (although the list of suite license features may be different):




To turn OFF the PADS Suite Configuration functionality that is restricting which license gets consumed:
  • Uncheck the Control suite license checkout and select from the following list: checkbox and click Apply and OK.

Note: Turning off the PADS Suite Configuration functionality only stops the license restriction functionality, so it does not guarantee that licensing errors will not persist (for example: all licenses could in use).


If you are using some other scripted method that restricts license consumption (for example: VBScript technique for controlling which floating license gets checked out)
  • Try invoking the application via the Desktop or Start Menu shortcut (instead of the script). However, the application may continue to fail in the event that all licenses are in use, or the license server is down.


NOTE: For each Mentor Graphics application -- Do NOT attempt to combine the above techniques for controlling license consumption, otherwise it will more than likely cause licensing errors. However, you can use one approach for application A (example: DxDesigner) and a different approach for application B (example: PADS Layout).