Skip to main content
D
davehaigh13-Aquamarine
13-Aquamarine
March 18, 2013
Question

Cause Found: Creo will not let user register server because of self signed certificate

  • March 18, 2013
  • 6 replies
  • 4618 views
We found the cause, but don't know why. The issue is Creo is reading a config.pro in an area where it shouldn't be looking. We have no idea why it's looking there for a config.pro. Renaming the file fixed the problem.

We found this by going to Support info and looking at the configuration files loaded.
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.

6 replies

B
BenLoosli23-Emerald III
23-Emerald III
March 19, 2013
Is d:\proilink defined as the Home or the Start-In folder?
Does the user have a mapkey running at startup that loads that config.pro file?
Did the user run a mapkey that loads that config.pro?
Any toolkit application running at startup?

Thank you,

Ben H. Loosli
USEC, INC.
D
davehaigh13-AquamarineAuthor
13-Aquamarine
March 19, 2013
Issue solved, but I had no idea Creo would look for a config file where it does.

Here's the issue. It's reading a config from %homedrive%\%homepath%. When did this start?
I confirmed this by placing a config.pro in my homedrive homepath.

This is what the user has set for those two:
homedrive=d:
HOMEPATH=\proilink

I always thought the order was this: Period.

1. Loadpoint\text\config.sup

2. Loadpoint\text\config.pro

3. Startup directory\config.pro


David Haigh
B
BobMonat1-Visitor
1-Visitor
March 19, 2013
I remember the home directory since at least before 1995.

Bob Monat
Jerand Technical Services, Inc.
bob@jerand.com
www.jerand.com
1-317-875-6087


D
dgschaefer21-Topaz II
21-Topaz II
March 19, 2013
Yup, it's been there as long as I've been aware. It's after the loadpoint/text but before the startup directory.

--
D
davehaigh13-AquamarineAuthor
13-Aquamarine
March 19, 2013
Well, according to all the responses I've received, evidently ProE has been like this forever.

Just goes to show I don't know everything. 🙂

Honestly, I've never used a config in the %homedrive%\%homepath%, and not in $HOME when I was on Unix.

I've always set ProE up to start from a single directory.

David Haigh
B
BenLoosli23-Emerald III
23-Emerald III
March 19, 2013
How Pro/ENGINEER Reads Configuration Files at Startup

Pro/ENGINEER reads configuration files automatically from several areas. If a
particular option is present in more than one configuration file, Pro/ENGINEER
applies the most recently loaded/read setting.

At startup, Pro/ENGINEER first reads in a protected system configuration file called
config.sup. It then searches for and reads in configuration files (config.pro,
config.win, menu_def.pro) from the following directories in the following order:

1. loadpoint/text (loadpoint is the Pro/ENGINEER installation directory): Your
system administrator may have put configuration files in this location to support
company standards for windows configuration settings, formats and libraries. Any
user starting Pro/ENGINEER from this loadpoint uses the values in this file.

2. Login directory: This is the home directory for your login ID. Placing your
configuration files here lets you start Pro/ENGINEER from any directory without
having a copy of the files in each directory.

3. Startup directory: This is your current or working directory when you start
Pro/ENGINEER.


Thank you,

Ben H. Loosli
USEC, INC.
Terms & ConditionsAccessibility statement