Skip navigation
All Places > Licensing and Installation > Blog

What does this license error message mean?

 

There are two messages which regularly we get asked to explain.  They are similar, but refer to different areas of licensing, and have different solutions.

 

 

FLEXlm version of the vendor daemon is too old

 

This means that the tool you are trying to run requires a newer version of software on your license server.

 

You can check which version you are running with the command "lmutil lmstat".  It should show v11.11 for BOTH lmgrd and mgcld.

 

If the version you are running is not the latest (v11.11), then update it using the instructions in technote mg66951.

 

 

License server does not support this version of this feature

 

This means that your license file does not include the correct version of license to run this version of the tool.

 

The version number appears as the 4th entry on each INCREMENT line in your license file:

 

     INCREMENT wgascentl2 mgcld <version> <expiry_date>

 

For example the license below has the version 2014.120:

 

     INCREMENT wgascentl2 mgcld 2014.120 31-mar-2015 ...

 

If you have a current support contract, ensure that you are using the latest license file available from Supportnet.  This should have a license with a newer version number.

 

If you do not have a support contract, you will be restricted to older versions of software.  For example, a license with version 2012.120 will only enable you to use software released in 2012 and earlier.  To use later versions, please contact Mentor Graphics Support.

The first time the Registrator runs (during the VX install) it prompts for the local WDIR folder location, and the value entered is stored into the WDIR_<product_root> environment variable. For example, PADS VX product root is "PADSVX.1.1" and therefore the variable name is WDIR_PADSVX_1_1 (replace periods/full-stops with underscores). The value of this variable becomes the "WDIR" once the applications launch (see TechNote MG586180 on SupportNet for more details).

When the Registrator next runs (launched from the Start Menu or via the Release Switcher) the WDIR prompt is populated based on the WDIR_<product name> environment variable. If you change the value, the variable is updated. Do NOT attempt to update the WDIR environment variable in the system area, as it will be over-written by the WDIR_<product_root> environment variable (e.g. WDIR_PADSVX_1 for PADS VX.1) as soon as the application launches.

While you can edit the WDIR_<product_root> environment variable in the system area , the recommended way to change the WDIR is to run the Release Switcher or Registrator.

Refer to the screen-shot below to see the relationship between the WDIR_<product root> variable and the WDIR prompt in the Registrator.

PADSVX0_WDIR.png

 

Related TechNotes:

 

Setting (and silencing) the WDIR variable (on SupportNet)

VX installation did not set environment variables, is this expected?

Sometimes users are running applications that are older than you would like or maybe you're just curious. Either way, you can gain insight into the application versions users are running by looking at the usage status of your license server with lmstat. The lmstat command shows not only the version of the license checked out but the version of the license the application requested. The requested version can be used to find who is running older versions. For example:

 

$ lmutil lmstat -f msimviewer -c 1717@server

lmstat - Copyright (c) 1989-2013 Flexera Software LLC. All Rights Reserved.

Flexible License Manager status on Fri 9/26/2014 15:26

 

License server status: 1717@server

    License file(s) on server: /opt/mgls/mgcld.txt:

 

     server: license server UP (MASTER) v11.11

 

Vendor daemon status (on server):

 

     mgcld: UP v11.11

Feature usage info:

 

Users of msimviewer:  (Total of 25 licenses issued;  Total of 1 license in use)

 

  "msimviewer" v2015.070, vendor: mgcld

  floating license

 

    user host 141.31.25.46:013453_1 (v2011.05) (server/1717 25360), start Fri 9/26 15:26

 

 

The license version (aka Exact Access Date or EAD), made bold for the example, usually corresponds to the release date of the application but you can check the application's release notes on SupportNet for confirmation. Better yet, find the user running the application and confirm the version they're running. You may want to point them to the latest release.

A useful but often overlooked feature in the InfoHub documentation system is the custom tab that allows you to provide access to your own documentation from the InfoHub.

 

Using the custom tab, you can provide links to important documents or create document groups. Here is an example of how I used the custom tab to provide quick access to some Mentor web sites I refer to often. I also created a group of links for some of the Mentor Graphics Communities sites that I visit:

 

custtab.jpg

 

Getting started is easy. Open the InfoHub, and look for the Custom Tab link at the bottom of the page:

 

custtab2.jpg

That's it for this week! Come back next week for another licensing and infrastructure tip.

 

-K

CCleaner version 4.17 of has now been released. In version 4.17 they have concentrated on improving browser support with the addition of Google Chrome and Opera GPU Cache cleaning. This version has improved Firefox and Google Chrome Startup item detection as well as Firefox Aurora cleaning.

Changes in v4.17 include:
Added Google Chrome and Opera GPU cache cleaning
Improved Google Chrome and Opera Download History cleaning
Improved Firefox Aurora Session cleaning
Improved Firefox and Google Chrome Startup items detection
Added PhotoScape, BlueStacks and ManyCam cleaning
Improved AntiVir Desktop and Wondershare cleaning
Minor GUI Improvements
Minor bug fixes

Download location: https://www.piriform.com/CCLEANER

What's new in Mentor License Utility (MLU) v3.0?

MLU version 3.0 (BETA) introduces many new and exciting functions. To name just a few:

  • Install licenses directly from SupportNet
    • From within the main MLU program but also from a new system tray applet!
    • Schedule a new license check (automated, runs in the system tray) for every 1, 3, 6, or 12 months!
    • See further below for screen-shot and demos
  • New "Server Services" tab for quick access to license manager info (mgcld daemon only)
  • New "Install Licenses" tab for quick access to license install and downloads

 

See further below for sample screen-shots.

 

For download and more details (including videos) refer to the following TechNote on SupportNet:

http://supportnet.mentor.com/portal?do=reference.technote&id=MG586631

 

 

Install Licenses (main) tab:

mlu_main.png

 

Install licenses from SupportNet:

MLU_InstallLicense.png

 

Server Services tab:

mlu_services.png

 

Client Environment tab (was the default display in MLU v2.x):

mlu_client.png

 

MLU Updater (system tray applet):

MLU_updater_menu.png

 

New licenses on SupportNet have been found and are ready for installation:

MLU_updater_newLicenses.png

One thing that's always been lacking in Windows is a good interface for creating or editing your environment variables, especially when it comes to PATH:

 

2014-08-22_141706.png

 

Se what I mean?

 

Fortunately, there's a great free utility called Rapid Environment Editor that not only makes it easier to edit variables, it will also tell you where you have bad values. Check it out:

 

2014-08-22_142055.png

 

It highlighted my Path in red to tell me there was a problem and when I expand Path, it shows the problematic entries. Brilliant!

 

I can delete these and save my environment with a cleaner PATH variable.

 

Feel free to give REE a try - http://www.rapidee.com

 

Guy

Those of you who frequent the Mentor Graphics Community have provided a tremendous benefit to the community at large; providing solutions and sharing your experiences for the benefit of others. By coming here and actively participating you have made the community what it is, and what we hoped it would become.

 

However, there are times where opening a service request with customer support is necessary. For those so entitled, this Tip of the Week gives you the top 5 things to include in a service request that will make the handling of your issue go as smoothly as possible.  Here is the list, in no particular order of importance.

 

1.       Product and Version Information

 

P        Providing this is key for a CAE to know where to start looking for a resolution to your issue. It helps them to quickly zero in on known issues in particular versions of software and find their solutions, provide you with information about patched versions, etc. The Product field is also used by our automated systems to route service requests to the right people who are the subject matter experts. Being as accurate as possible helps avoid any mis routing of service requests to the wrong support team, and the resulting delay as the request is re-routed.

 

2.       Platform and OS Information

 

      For much the same reason stated above, having accurate platform, OS and architecture information helps a CAE get to the root cause more efficiently. When they know what you have, a CAE can easily eliminate possible causes that don't apply to your platform, OS, or architecture.

3.      

            Error Messages and Log Files

 

      The error message is the first thing a CAE will analyze in the process of troubleshooting your issue. A complete and accurate error message, if one is presented, is the lead that can crack the case wide open. If no error message appears that is also an important clue, and you should point that out. Recording them word-for word, exactly as they appear, is important because subtle differences may give the error message a different meaning. Adding screen captures to your service requests is a perfectly acceptable way of providing this information. Log files that contain error messages, design path names, etc. are always welcome and should be included, especially if known to contain relevant data.

4.      

           Contact Information

 

      Your SupportNet profile allows you to set a preference for how contact with you is made (phone or e-mail). By default, no preference is set. In that case, CAEs use their own discretion to decide how to make contact with you. If you have a preference, setting it in your SupportNet profile avoids a situation where you are waiting for your phone to ring but the solution has been in your inbox the whole time. Accurate contact information is vital to avoid delays. Best practice is to review this information any time you open a Service Request.

 

      It's pretty common for the person opening the Service Request to be assisting another user at their desk, or perhaps in the data center working on the problem. In that case you should provide alternate contact information if needed, and specify the date/times when you can be contacted there. The most conspicuous place to put this information is in the symptoms field.

      

           Provide a Summary of Self-Solve Attempts

 

      If the CAE knows what you've already tried to solve the problem yourself  (TechNote procedures you followed, for example) it will help them focus their inquiries on the results you had instead of starting at square one.  CAEs read the details in your service request before they make contact as a rule. So for example, if they read in your service request that you reinstalled the software and there were no installation errors, they can assume for the moment that it’s not an installation problem and start troubleshooting elsewhere when they engage you.

 

 

This tip is written with Service Requests in mind, but also applies when posting in the community as well. Those who read your post may be more inclined to respond if they have enough information to form an opinion.

In Oracle nomanclature, patch 10404530 refers to the base 11.2.0.3 install. Using the term 'patch' may cause confusion but that is how Oracle refers to their software.

Oracle base version 11.2.0.3.0 automatically contains the patch 10404530 data. The ‘patch’ is a full install, despite the reference.

With the release of PADS VX.0, the Aladdin USB (9-) hardware key is now the only supported dongle. We began dongle discontinuations a few years ago and they have trickled out release by release. The PADS VX.0 is a major release and customers using older dongles who wish to run the latest version will need to request a replacement key.

 

Please see our Hardware Key (Dongle) Discontinuations and Replacement FAQ for more information.

 

Customers running older releases can continue to run with the older dongles provided they are on a supported platform.

Now that PADS VX.0 is available for download on SupportNet, here are some key links to determine if your license file will run the release, and what else you need to know to get up and running successfully:

 

Which PADS Flow release am I entitled to use?

 

Download the latest copy of your site's license file (on SupportNet)

 

PADS VX.0: Learn more about licensing and infrastructure changes (on SupportNet)

 

PADS Installation and Licensing FAQ  (on SupportNet)

With the MSL v2014_1 release, we now have a 100% 64-bit MGLS for Linux x64. This means that for your Mentor license server, you no longer have to load 32-bit OS compatibility libraries to run MGLS.

 

You can download the latest MGLS for Linux x64 from SupportNet.

Mentor Graphics products built on 32-bit Linux platforms can run on a 64-bit OS, but they still require 32-bit runtime libraries. On RHEL 6 the 32-bit libraries are not included with the media, but they are available using the same methods used to update the OS software.

 

The default configuration for yum only updates and installs 64-bit packages, unless you specify the 32-bit packages you want. If you configure the multilib policy, you can update and install 32-bit packages automatically whenever the 64-bit packages are updated.

 

Set the configuration option multilib_policy=all in /etc/yum.conf. This enables the multilib policy as a system-wide policy.

 

Ken Foster

Mentor Graphics Customer Support

The main application tree is now version specific, ‘VNPI_94’, and the executable directory is now generically named, ‘edir’. For example: C:\MentorGraphics\Valor\VNPI_94\edir

The 'edir' directory is also the new location of the 'env' file.

With this version a new installation structure was implemented. Instead of installing in the traditional ‘eXX’ directory, a new directory structure starting with by default “VNPI_94” will be created (following version will adhere to this naming convention). Within this directory a generically named directory ‘edir’ will now contain the version specific executable. The VALOR_EDIR variable will then refer to this new ‘edir’ directory location.

With the vacation season approaching fast, can I recommend some interesting articles on Mentor's blog pages.

 

Alternatively, you could take a look while waiting for software to load (as this is the Licensing / Installation community!)

 

The range of topics never ceases to amaze me. Recent topics have included:

 

  • Turning on a red signal - which is normal practice in USA, but illegal in the UK.
  • Internet connected ECG monitors - probably required by any passengers in a car making an illegal turn.
  • Wireless recharging of electric busses - safer for everyone on the road.
  • How to heat your home office for 8p (14 cents) a day - if it is too dangerous to go out.

 

Take a look at http://www.mentor.com/blogs/   I'm sure there will be something that will interest you.