Some upcoming events are noted below:
[Resolved]: Microsoft has released an Internet Explorer Update (2987107) to resolve this issue.
When trying to Activate Autodesk software, the licensing wizard (lmu.exe) will crash. In fact, you will not be able to even run the product in Trial Mode.
Please check out this article for a possible workaround:
Personally, I have noticed this problem happening with Autodesk 2012, 2013 and 2015 products.
We had a old post that dealt with Revit Updates noted here:
There is also R2 and UR2, the Revit Product Support team mentions the install order and features of it noted here:
Uninstalling Search Protect will solve your AutoCAD Application Error (0xc0000142) & (0xc000000c5) but you also may have Malware installed on your computer, please check out the following blog post to remove them courtesy of our technical guru: David Dembkoski.
One of the customers [Jerilyn Luben] that I was working with gave me this great tip on how to reinstall Windows 7 and the instructions are noted here:
We have received few reports about the issue described below.
Launch Inventor that has not been activated yet on Windows 8.1 and Windows 7.
Accept privacy dialog.
When the try \ activate dialog is presented a crash occurs.
From our investigation we discovered that Microsoft update KB2977629 (Sept 9 2014) has contributed to this problem.
This hotfix is available in Windows 7 and 8.1.
The workaround for activating the product is to remove the hotfix.
Apparently the issue is impacting other Autodesk applications as well.
These Microsoft updates are also affecting AutoCAD and it is noted here:
We have noticed that Internet Explorer 11 has been causing the licensing wizard to crash (lmu.exe). In fact, you will not even be able to run the product in Trial mode. To solve this problem, you need to uninstall Internet Explorer 11 by using the View Installed Updates in the Programs & Features Control Panel.
We want to build your Autodesk Software Up and Ready IQ and we cordially invite you to our first Webinar that is happening this week. For more info, please go here:
You can you can also register here:
We have had some success from the other teams for training via Webinars below:
In this episode of tenacious troubleshooting, we are focused on the -97 error.
1. The easy part is finding what the FlexNet error codes mean. It is noted here:
2. When this error happens on the license server, just look at the server log file to determine what the problem is. You can also check out this blog post for more info as well.
3. In this instance, on the client workstations, when we launched the product, the FlexNet Finder window would keep on looping and the error was 0.0.0.
a. We confirmed that the license server at the site was running the current version of NLM (11.12).
This is also noted in the log file on the license server.
b. We then increased the error messages for licensing by adding this environment variable on the workstation.
c. We finally get the dreaded -97 error message.
In the dialog box, we confirmed that client was looking at the correct server and the Windows Firewall was correctly configured as noted in steps 4-6 in the Quick Start Setting up a License Server blog post.
The client machine indicated that the server was not running. A known issue is having with other 'vendors' on the server along with Autodesk products. The symptom is that the server log file will appear like it is running but it is not actually running. The solution is basically to stop the Autodesk license server and edit the license file and add a port to the license file as noted below:
SERVER TOR2UA13809X0 3CD92B5B4B2E 27001
VENDOR adskflex port=2080
Once the file has been edited, just restart the license server and the software should launch correctly.
For more info on the this issue, please check out the following posts/articles:
Thanks to Sean Couture for confirming this workflow was indeed the problem.
Recently been troubleshooting deployments for Plant Design Suite 2015. There are some issues that we are working on and one of them is the deployment not installing when AutoCAD Plant 3D OE is included in AutoCAD.
The solution is noted in this knowledge article: