Pro/E ignoring config.pro in user's home/profile folder

[gchampoux]

As part of our custom Pro/E launch batch file, it creates a config.pro in the user's profile folder with certain settings.
(C:\Documents and Settings\<user id=">\config.pro)
This is one of the places that Pro/E (Wildfire 3) looks for config.pro when launched.

However, for one user, this config.pro file is being ignored as if it did not exist.
This is confirmed through: Help > Technical Support Info, which lists all config.pro files that are read.

This only known difference between this one user and others is that he uses a laptop.
He is on Windows XP SP3 like all other 32-bit users here.

Has anyone ever seen this behavior?

Gerry Champoux
Lead Engineer
Information Technology

Williams International
2280 E. West Maple Road
Walled Lake, MI 48390-3828

(248) 960-2816

(248) 960-2607

-

<u>www.williams-int.com</u>

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[lwh]

Some things to check:

Are You using Active Directory ? - so maybe the actual home directory is a server folder.

Check the environment variables in ProE's system window. Where does ProE see the home directory?

What about user privileges?

[gchampoux]

Yes, we do use active directory.

However, all users have their profile (home) on the local PC, including the laptop user that is having this problem.

I checked the environment variables.

This sparked my memory of a user that had this same problem years ago.

I recall that the user hada missingor deviant environment variable.

I was expecting to findthe samehere, but did not.

The home directory variables (HOMEPATH & USERPROFILE) were present, correctly defined, and consistent with all other PC's.

The user's privileges is the same as all other users.
He has full access to his profile folder and all files therein, including the config.pro file.

[jellis]

Gerry....perhaps you've already found the solution but if not perhaps this might be helpful? Run the 'set home' from a command window and check to make sure that HOMEDRIVE and HOMEPATH points to the location where the HOMESHARE from theAD account is mapped.

Regards, Jim

[gchampoux]

Thanks to all that replied, and special thanks to Jim for the clue we needed.
When executing "set home" we noticed that the user had HOMESHARE defined, which should not have been there.
And on top of that, it was pointing to a nonexistent share on a server.
We looked up the user's account (active directory) and found that this nonexistent path was set as his remote home folder.
We have no idea as to why it was set up this way.
Because the share did not exist, Windows XP was smart enough to default back to the normal home folder on the local drive, but Pro/E did not.
After we disabled the remote home folder option, all was well.

[lwh]

That depends:

If You want global settings for all users, put it in the <proe-install>/text folder.

User-specific settings are best in the working directory. That file should only contain changes wrto the global settings.

If You have different user settings, copy the file to the working directory before starting ProE. (Remember, ProE will add an index when local changes are made.)

[lwh]

Sorry. How did that get here???