Been running across this error for several releases, all the way back to 2005. Usually it occurs when specific tools (such as the AEC Callout command, that creates sections, elevations, etc.) are not properly registered when the program is installed. Some users have success fixing this using a repair, but I didn't...and here's why I think that happened.
- ALWAYS install Autodesk products as an administrator. A quick way to do this is instead of just double clicking on the setup.exe file, right click on it and choose "Run as Administrator". Even though I've got admin rights on my Win7 notebook, it doesn't always work - so this guarantees it's installed with the correct rights.
- ALSO - use a CUSTOM install - to do this in 2012, you have to pick the AutoCAD MEP 2012 install package on the new installer - this expands the window to give you your options. I always do a custom install, adding Express Tools, and more importantly, the AutoCAD Architecture profile - that way I have all of the AutoCAD Architecture tools.
After wiping out my initial, "typical" install, and reinstalling, everything works fine...even an old dawg like me needs the shock collar once in a while...
Happy CAD'ing!
David B.
5 comments:
David, I can tell you exactly usually causes this, and how to fix it without resorting to a re-installation.
This typically happens when a user restores the "AutoCAD" profile, which changes this value in the registry:
HKCU\Software\Autodesk\AutoCAD\R18.2\ACAD-A006:409\Profiles\[ProfileName]\ General\RegisteredToolsPath.
It should point to \Support\RegisteredTools in your Roamable Root Folder (e.g. C:\Users\[Useraname]\AppData\Roaming\Autodesk\MEP 2012\enu\)
When you use the plain AutoCAD profile, it changes the folder location to \RegisteredTools-AutoCAD. Change it back to the \RegisteredTools folder and you should be fine.
Also make sure the RegisteredTools folder has both AcTpTools.atc, ADTStockTools.atc, and MEP Stock Tools.atc. These three XML files tell MEP which .DLL and .ARX modules are used which make the Tool System work.
The RegisteredTools-AutoCAD folder only contains the AcTpTools.atc file, which is why no MEP tools work in the Tool System.
David, I can tell you exactly usually causes this, and how to fix it without resorting to a re-installation.
This typically happens when a user restores the "AutoCAD" profile, which changes this value in the registry:
HKCU\Software\Autodesk\AutoCAD\R18.2\ACAD-A006:409\Profiles\[ProfileName]\ General\RegisteredToolsPath.
It should point to \Support\RegisteredTools in your Roamable Root Folder (e.g. C:\Users\[Useraname]\AppData\Roaming\Autodesk\MEP 2012\enu\)
When you use the plain AutoCAD profile, it changes the folder location to \RegisteredTools-AutoCAD. Change it back to the \RegisteredTools folder and you should be fine.
Also make sure the RegisteredTools folder has both AcTpTools.atc, ADTStockTools.atc, and MEP Stock Tools.atc. These three XML files tell MEP which .DLL and .ARX modules are used which make the Tool System work.
The RegisteredTools-AutoCAD folder only contains the AcTpTools.atc file, which is why no MEP tools work in the Tool System.
I acutally wound up with more that just the tool palette error - my install also didn't include the content builder and catalog editor tools - which was weird, especially since I was using a "run as administrator" install with full rights to all the folders...this install just was weird, and wound up copying a lot of tools over from 2011 to get it work - which it does pretty well now.
Didn't I always used to tell my clients, wait for the first SP? Man....can't follow my own advice...
in xp my regestry entry for "RegisteredToolsPath" was pointing to "C:\Program Files\Autodesk\AutoCAD Mechanical 2012\Support\ToolPalette\RegisteredTools" when it should have been point to "C:\Program Files\Autodesk\AutoCAD Mechanical 2012\UserDataCache\Support\ToolPalette\RegisteredTools" this simple change cleared the error, thanks so much for the post.
Matthew: Brilliant! I checked the paths in the registry and they were set correctly. But, there were a few .atc files missing from the folder!
After popping those .atc files in, everything is working splendidly. Thanks! That was a real head-scratcher for awhile.
Post a Comment