topic Re: Creo Windchill registered Server not using .srv_mgr_db3.fldx in System Administration

Creo Windchill registered Server not using .srv_mgr_db3.fldx

LawrenceS — Mon, 30 Dec 2024 17:41:04 GMT

While using Creo with Windchill I am trying to run a trail file automatically (just to open the active workspace) after starting up Creo using the following syntax (not both lines work separately):

start "" "c:\my location1\parametric.exe" "c:\my location2\trail.txt"
start "" "c:\my location1\parametric.exe" -i:rpc_input "c:\my location2\trail.txt"

Even though both work, both have a strange side effect where I lose my registered servers and I have to re-register them. What is even more strange is that it not only doesn't modify the .srv_mgr_db3.fldx file, I cannot find a file on my computer (or the network location where my batch file and other config files are stored) that stores the new server info. When I restart Creo my trail file runs, and my workspace refreshes correctly, but it uses my new server registrations and not my old. If I go back to using:

start "" "c:\my location1\parametric.exe"

It starts using my original server registrations. When I use a trail file, where is it storing my registered servers since it is evidently not in the following normal location:

C:\...workspace\PTC\.ssappd\ServerMgr\.srv_mgr_db3.fld

Questions:

In what file are these new registered servers being stored since it is not the .fdlx (in any location even in the userprofile, etc)?
Why is it doing this when I add the trail file?
How do I control the behavior and make sure it continues to use the .srv_mgr_db3.fldx file in my PTC directory?

Environment:

Creo 7.0.11
Windchill 12.0.2.16

Thanks! Lawrence

Re: Creo Windchill registered Server not using .srv_mgr_db3.fldx

MartinHanak — Tue, 31 Dec 2024 16:28:09 GMT

Hi,

maybe following documents help you to solve the problem.

https://www.ptc.com/en/support/article/CS305971

https://www.ptc.com/en/support/article/CS174534

Re: Creo Windchill registered Server not using .srv_mgr_db3.fldx

LawrenceS — Thu, 02 Jan 2025 23:53:06 GMT

Thanks for those articles @MartinHanak. After reviewing I don't think either of those match this particular issue and don't see how they can help. As for the second article, I don't actually get an error message.

Since this post, I have found the file this info is being stored in is a completely different file in the following file

\\workspace\PTC\.Settings\config.fld

It is a very different format than hten .fldx originally mentioned, though contians similar data in xml format. It also sometimes comes with another file:

\\workspace\PTC\.Settings\.do_not_read_config.fld

I am wondering if this is an old method of calling out server info that is no longer used but what I did wasn't accounted for so it forced it into this old methodology. It reminds me of the .ui file vs the old config file that controlled it (cannot remember the name) and sometimes broke if you tried to customize the legacy GUI within the old legacy Creo symbol editing interface.