CREO2 config.fld

[bbenitez]

Hello all



I have a CREO2 F010 - Windchill Intralink10.0 M030 problem.

CREO2 cannot remember the Windchill server for some reason.

The info is kept in a config.fld file in the startup folder

CREO2 doesn't read the config.fld file - CREO1 does ???







Anthony R. Benitez

Senior Mechanical Designer - Supervisor

Applied Research Laboratories - The University of Texas at Austin

-




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.

[BrianMartin]

Hi Anthony...

The default is yes which automatically remembers the primary Windchill server. But if this option has been toggled off, this could cause your problem.

Please write back and let us know if this helped or not.

Thanks!

-Brian

[jellis]

This issue stems from interaction between Creo 2 and Toolkit functions. OOTB Creo 2 creates a 'active_server_config.fld' file. If you have any protk options in your config.pro then Creo 2 creates the 'config.fld' file the first time you registerthe WC10 server. The very next time you launch Creo 2 with a protk option another file called 'do_not_remember_server.fld' is created and Creo 2 will not connect to WC.

We havecase 10895855opened and there is areference to PTC article CS61022.

Our workaround was to look for that "do_not_remember'file at launch and then either Rename or Delete.

Regards, Jim

[bbenitez]

Hello All -



Just a reminder this is a CREO2 F010 / Windchill INTRALINK 10.0 M030
problem.

Primarily - a CREO2 F010 bug that prevents registration of the WC Server at
launch (user must manually register the server).

Works fine in earlier builds, and CREO1.



I also have an open case 10910083 with PTC - and a new one that seeks to
solve the underlying issue of Platform2.9 not installing correctly. If
Platform 2.9 installed itself as it should, this problem would not occur.
We roll out CREO2 & WC on Friday for our users - so we had to do something
since PTC has, as of yet, not been able to provide a workaround.



I took the cue from Mr. Ellis and identified the guilty file and came up
with a DOS (LOL - yeah, still using DOS, eh?!) .BAT file to delete the
offending file before launch. The .Bat file is copied below for those who
are interested. Win7 solution, it will change for XP users, etc. and may be
different depending where Parametric.exe is located on your workstation.





Del
"c:\Users\%username%\AppData\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings\
.do_not_read_config.fld"



"C:\Program Files\Creo 2.0\Parametric\bin\parametric.exe"



Make sure the batch file starts in the Startup Folder for CREO, if in My
Documents, make a shortcut to your desktop.

And I have it set to run minimized to the tray.



Enjoy!





Anthony R. Benitez

Senior Mechanical Designer - Supervisor

Applied Research Laboratories - The University of Texas at Austin

-

_____