I recently had a customer with the following error in the Command Line when launching Civil 3D: “There are currently no palettes to show in the Toolspace window.” Not only are there no palettes, but the Toolspace won’t load at all. So what is going on here?
For my customer, they had previously setup their company-specific Profile (.arg file) from a 32-bit machine. The file was then stored on on a shared location, for new users/machines to grab. The issue came to light on the customer’s new Windows7 64-bit machine.
We took a look at their support paths in the Profile, and found the issue. It’s important to remember that since Civil 3D 2010 is a 32-bit application, it is installed into the \program files (x86) directory. When brining over a Profile from a 32-bit OS, the (x86) folder will be missing. You will need to modify these support paths to represent the change in the OS.
Specific to the Toolspace is the \autodesk shared\axui directory. Without this pointed to the correct folder, the Toolspace won’t load, and you will receive the error message.
Hope this helps!
Subscribe
Twitter