After installing Autodesk Revit 2017 on a student’s laptop, the software started whining about missing
msvcr100.dll. This was solved by repairing Microsoft Visual C++ Redistributable for Visual Studio 2012 Update 4, both x86 and x64.
I was installing Autodesk Vault Professional 2017 in the wee hours today, and I noticed the Autodesk Network License Manager was installed in
C:\Autodesk\Network License Manager. That’s a bit strange when
C:\Autodesk has until now been a temporary location for extracting the setup files.
I can confirm moving the files to a saner location like
C:\Program Files\Autodesk\Autodesk Network License Manager doesn’t work at all. The NLM simply won’t start and nothing gets logged.
It gets even stranger as one of the LMTOOLS shortcuts wants to run
lmtools.exe from the
C:\Program Files\Autodesk\Autodesk Network License Manager directory, i.e. the old location. Note, this was done on a newly installed Windows Server.
In short: Be very careful when emptying the
If AutoCAD 2015 refuse to install, try to uninstall Microsoft Visual C++ 2012 Redistributable, both 32-bit and 64-bit, and try to reinstall AutoCAD 2015. In one instance was it necessary to uncheck Autodesk ReCap. I really wish there was a simple way to mark only the essential parts necessary for the creation of simple drawings.
If AutoCAD 2015 refuse to run, go through this checklist:
- Check, and if necessary, change the computer name; Autodesk’s products expects only latin letters.
- Remove any traces of previously or currently installed McAfee products. See my blog entry from November 12th.
- Try setting
HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R20.0\ACAD-E001:409\3DGS Configuration\Certification to
- Try setting
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows to
- Try setting
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows to a blank string.
Sometimes McAfee products causes more grief than joy. For some mysterious reason, some, if not all, McAfee products interfer with the handling of VBScript as they register their own .dll file for handling VBScript.
Not all attempts at manually correcting the Windows Registry prove successful.
In most cases McAfee Consumer Product Removal tool are able to remove the last traces of the McAfee products previously or currently installed, enabling Autodesk software to complete their activation ritual.
I’m also pointer fingers at Autodesk for chosing an activation scheme based on Internet Explorer technology, VBScript, and, JScript, where a simpler approach would more than suffice.
A student had recently installed Autodesk Inventor Professional 2014 SP1 on his Dell Inspiron 7520, running Windows 8.1. Inventor refused to run and crashed with a more or less useless crash report.
It turns out that Dell or possibly someone else hadn’t properly installed the driver for the AMD Radeon HD graphics card. Catalyst Control Center was surely missing.
A trip to support.dell.com to download the current driver for the AMD Radeon HD graphics card was required. I ensured that Inventor always run using the high performance graphics card and that power savings are disabled regardless of the charger being used or not.
Inventor Professional 2014 SP1 now runs happy on said student’s Dell Inspiron 7520.
It’s the same story all over again. While preparing installation instructions for Autodesk Inventor Professional 2015, for my students, I came across an error I thought would have been fixed by now. Continue reading Autodesk Inventor Professional 2015: Serious error: VBA failed to initialize properly. Please restart Inventor.
If you receive such an error message from Autodesk Inventor Professional 2014, you might need to reinstall the VBA 7 modules. See http://usa.autodesk.com/adsk/servlet/ps/dl/item/print?siteID=123112&id=21910314&linkID=9242018 for more details.
The short story is to shut down Inventor and reinstall the VBA 7 modules using either
3rdParty\x86\VBA\Vba7.MSI from the installation media or from
A student came by my office today and wondered if I knew how to bring back the usual dialog boxes for file handling in AutoCAD. A quick search using Google revealed the
The solution is to execute the
filedia command, enter
1 (the digit one) as the requested input, hit the enter key, and voilà, normal dialog boxes appear whenever the
saveas commands are executed.