Regarding the error "FATAL ERROR: Invalid Configuration path/filename:
C:\Documents & Settings\User\Local Settings\Application Data\Autodesk\ADT
2005\ENU", it probably has to do with the placement of the acad2004.cfg or
acad2005.cfg file. We're using AutoCAD 2004, and have seen the same error
message before. Rather than allow AutoCAD to create and reference the cfg
file within the windows profiles area, repath it to a benign folder, where
everyone has rights. You can repath it using the /c switch on the program
startup property of your desktop autocad icon.
For example:
C:\somepath\acad.exe /c c:\temp
For example, we installed AutoCAD 2004 to a C:\R2004 folder, so our AutoCAD
icons have the following command line argument:
C:\R2004\acad.exe /c c:\r2004\support
Everyone has rights to the C:\R2004\Support folder, so no more random
crashes with the "invalid configuration path/filename problem". By the way,
if the acad200X.cfg does not already exist in whatever path you specify,
it'll be created on the fly. Why therefore, AutoCAD disallows setting the
path in the Options dialog box is a mystery to me, when the file isn't
really critical and will be created on the fly, and instead forces the
arcane usage of a command line switch... go figure.
--
Mark McDonough
Sasaki Associates
http://www.sasaki.com
wrote in message news:4853739@discussion.autodesk.com...
Once upon a time there was a netwrok ADT 2005 install that worked like a
champ. Lately however, this install has been feeling rather sickly. She
works fine on the actual install part, but then when you log in as a user
and launch (using a shortcut that references the office standard ARG) she
faints with "FATAL ERROR: Invalid Configuration path/filename: C:\Documents
& Settings\User\Local Settings\Application Data\Autodesk\ADT 2005\ENU"
Now, I have searched the KB, and the only reference I find is for R2004, and
it says to make sure the newest SP is installed, which it is in this case,
as it is part of the initial install. I have also heard that the issue is
with permissions to the network resources that Acad is using (office
standard customization and menus, etc). I have set that entire share to ALL
Users have Modify rights, but no luck.
One thing to note, the server has been upgraded to Windows 2003 since the
last AutoCAD install, and the new IT Manager has done some tinkering with
Group Policy as well.
So, has anyone seen this with 2005? Any ideas what causes it and how to fix
it? And does the issue exist in 2006?
best,
Gordon