Up and Ready

Quick Start: Tips and Tricks for the Autodesk Network License manager [lmtools.exe]

I have collected all the tips and tricks that I know of for the Autodesk Network License Manager  [lmtools.exe] as a Quick Start guide.  

1.  My personal favourite:  Edit > Clear Window...

Video:  Quick-Setup-lmtools

2.  Don't use the default name when creating service...

http://upandready.typepad.com/up_and_ready/2011/06/general-licensing-dont-use-the-default-name-when-configuring-lmtools.html

3.  Some additional check boxes in lmtools.exe and what they do...

http://upandready.typepad.com/up_and_ready/2011/06/general-licensing-additional-settings-in-lmtools.html

4.  Getting the status of license files that are really long...

http://upandready.typepad.com/up_and_ready/2012/05/general-licensing-getting-the-server-status-with-long-license-files.html

5.  Setting up more than 1 service in lmtools.exe

http://upandready.typepad.com/up_and_ready/2013/11/configuring-network-license-manager-lmtoolsexe-for-more-than-one-product.html

6. Appending the Debug log file the EASY way

http://upandready.typepad.com/up_and_ready/2015/01/the-easiest-way-to-append-the-results-of-a-log-file-in-lmtoolsexe.html

7. How do a update license file on server without access to server? 

http://upandready.typepad.com/up_and_ready/2015/07/how-do-a-update-license-file-on-server-without-access-to-server.html

AutoCAD Family: Configuration file may be locked by another process or have been set Read Only (.cfg, .bak).

If you get this error when running AutoCAD 2013 or AutoCAD 2012 on Windows 7, please check out the workaround below:

Configuration file may be locked by another process or have been set Read Only (.cfg, .bak).
File:  C:\Program Files\Autodesk\AutoCAD 2013\acad2013.cfg
Please correct this problem and press Retry or press Cancel to exit the application

Video:   Acad2013.cfg Error

If you create a deployment and select the Support Content to go in:  Program Install Folder, you will get the error message above.

Video:   Autocad-2013-deployment-error

Windows 7 will not allow the writing of files in the Program Files folder. The config file cannot be written there.  The result is an error message and AutoCAD crashing upon launch. This is not a problem for Windows XP.

Legacy AutoCAD CAD Managers have typically deployed the Support Content to the Program install folder.   With Windows 7, User Access Control [UAC] will block the proper installation and configuration of AutoCAD.  This error will still happen if you attempt to run AutoCAD in an Administrator account.

NOTE:  You need to use the default setting:  User local profile folders and the installation of AutocAD 2012/2013 via a deployment will work as expected.

General Licensing: Getting the server status with long license files

If you have a license file that is really long, you will notice that there is a limit on how much can be displayed when doing a Perform Status Enquiry.   Please check out these 2 workarounds:

1.  Use the Individual Feature Option in lmtools.exe

A.  Use www.licenseparser.com to check the license and to search for the Feature Code to use in lmtools.exe.

B.  In lmtools.exe > Server Status Tab, before you click on the Perform Status Enquiry button, enter the Feature Code in the Individual Feature Option.

Video:  Lmtools-feature-only

2.  Go old school and do it via Command Prompt.  The basic syntax is:

"C:\Program Files\Autodesk Network License Manager\lmutil.exe" lmstat -a -c "C:\path\of\license\file\sample.lic" > C:\results.txt

"C:\Program Files\Autodesk Network License Manager\lmutil.exe" lmstat -a -c @SERVERNAME

In this video demo, I dragged the lmutil.exe and the license file [-t1.lic-] into the command prompt because I hate typing:

Video:   Lmtools-command-line

Inventor Family: Hanging on the splash screen

We recently got a case that came into Product Support in which Inventor 2013 was hanging at the splash screen on Windows 7/XP.   The culprit was a Microsoft KB2633171.  Once you uninstall the update, the software would function properly.

It was a bit of luck to solve the problem.  Basically, we had to find out the last working day the Autodesk software ran and then we checked for programs and updates that were installed on that day.

If you google KB2633171, you will notice some interesting effects of this KB patch.

Thanks to Jeffry Asbury for sharing this tip with the community.

AutoCAD 2013 for Mac: WHIP failed to initialize

If you are getting this error when launching AutoCAD LT 2013 or AutoCAD 2013:

WHIP failed to initialize.

This error indicates that you have an older graphics card/hardware that doesn't support AutoCAD.  For more information on what is supported, please check out these reference posts:

http://usa.autodesk.com/autocad/system-requirements/

http://support.apple.com/kb/HT3246

NOTE:  This will also affect the App Store and Autodesk versions of AutoCAD LT 2013.

Cool: The AutodeskCare Customer Service Blog

We [-the Systems team-] can help you install it, they [-the Customer Service team-] can help you license it. Meet some of the faces on the Customer Service team via there new blog:

http://autode.sk/IlWtTu

So, don't be bashful. Drop by our Twitter home or AutodeskCare blog, say "hi", follow us and then tell all your friends and colleagues about Autodesk's new customer care channel. We'll leave the light on for you! :)

BTW, we have been escalating cases to them and vice versa in order to help the customer [-you-] a bit faster.

General Installation: dlumd32.dll & DisplayLink Core Software

Product Support has been getting a lot of cases based off of this software causing the installer to not work.  It applies to ALL Autodesk products because the install framework is the same for ALL products.

This was caused by dlumd32.dll and the problem was resolved by uninstalling DisplayLink Core Software.

Reference: 

http://upandready.typepad.com/up_and_ready/2012/04/inventor-lt-suite-2013-installation-wizard-hangs-and-submits-an-autodesk-error-report.html

Epilogue

To resolve this issue, please use the latest driver [6.2 M2] from Display Link.  I received some feedback and guidance  from Dan Ellis from Display Link to close the loop on this problem.

Inventor Family: An Autodesk product failed to send the required value for SERIALNUM.

I am only posting this to share with the community.  After researching our Discussions Groups, QA and various technical gurus within Autodesk, there are 2 solutions to this problem.

An Autodesk product failed to send the required value for SERIALNUM.

1.  Toggle off .NET 3.5.1, reboot your computer, toggle back on .NET 3.5.1 and reboot your computer again. Then try to run Autodesk Inventor.  In Windows 7, this option can be found in Programs and Features > Turn Windows Features on or off.

2.   Backup, reformat and re-install your operating system.  Here is another deadly issue with a hail mary type of solution:

http://upandready.typepad.com/up_and_ready/2011/09/error-unable-to-run-autocad.html

Epilogue I

We recently got workaround solution for this problem!  You will need to create a new user account on the system and see if you can start your Inventor in that new account.  You may also reset your own account in Windows 7 as well.

1.  To reset a user account, you will need to copy your account profile on a network/backup drive then delete it.

C:\Users\YOUR-ACCOUNT-NAME

2.  Delete the User Profile in System Properties and log back in as yourself.

Epilogue II

You can also try to use a previous Windows Restore point to go back in time. You will then choose a date that you last recall when Autodesk Inventor was last working.

Thanks to Dan Kerby for sharing this tip with the community. 

General Licensing: Getting an Activation Code Manually

In some instances, you will need to activate your product manually.  In order to get to this stage, you will need to:

1.  Try to activate the product automatically following the wizard.
2.  Close the wizard and try to Activate again and choose "I have an activation code from Autodesk".
3.  Gather the following information:  Product, Serial Number, Product Key, Request Code.
4.  You should be able to run the product for 30 days while you are waiting for the Activation Code.
5.  You will then contact the Registration and Activation Team and  provide them the following information:  Product, Serial Number, Product Key, Request Code and they will email you an activation code.

Here is the process to get the required information (steps 1-5):   

Video:    Manual-Activation

If you have Subscription, log a case and submit all the information noted in the wizard.

Product:
Serial Number:
Product Key:
Request Code:

You can also call the following number:

 

1-866-681-4359 - Option 1 (English) -  Option 1

You can request an Activation Code online via an online chat.  The instructions are here:

http://knowledge.autodesk.com/contactus

Select the options noted in the Screencast:

http://autode.sk/1gts1fF

Reference:

http://upandready.typepad.com/up_and_ready/2012/01/cool-one-step-licensing-assistance-is-live.html

Autodesk Design Review 2012: Microsoft Visual C++ 2010 x86/x64 Redistributable

Autodesk 2012 products were released in 2011 and the Microsoft Visual C++ 2010 x86/x64 Redistributable version at the time was 10.0.30319.

If  your computer had the component installed previously, Microsoft Windows update would have auto-magically updated it to 10.0.40219.

The problem is the Design Review 2012 installation framework is looking for 10.0.30319 or older and when it sees 10.0.40219, the install will fail.  This also happens with Autodesk Takeoff which is in the Building Design Suite Ultimate.

The only solution is to uninstall Microsoft Visual C++ 2010 x86/x64 Redistributable 10.0.40219 before installing Design Review 2012.   Design Review 2012 will function with either version of the distributable so you can run an Windows Update afterward installing it.

Reference: 

http://upandready.typepad.com/up_and_ready/2012/01/autodesk-suites-building-design-suite-ultimate-will-not-install-with-autodesk-quantity-takeoff.html

Thanks to Johan Stadler for sharing this solution/tip with the community.