Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
Ever since we've updated Creo 2.0 to build M110, we have been finding that Creo always opens in the workspace that they were last in before they were updated regardless of which workspace they were in when they last used Creo. Furthermore if the workspace is deleted then it is recreated on startup and Creo opens in it.. This seems to happen to everyone regardless of what build they were
I haven't been able to find out anything about this either here or at PTC. Has anyone else experienced this?
We're on Windchill (Pro/Intralink) 10.1 M040, Creo 2.0 M110 (updating older builds ranging from M030 to M100).
David:
I believe this is the problem..
I deactivated it on this build for the first time so I wouldn't have to go around updating everybody's creoagent..
I'll tweak it and confirm to the list.
Thanks for the quick response.
In Reply to David Haigh:
Perhaps you have disabled the creo agent????
This is from my Creo Admin 102 talk, PTC Live 2013
Disabling the creoagent causes Creo to forget the last workspace used. The work around is to replace the
\.Settings\active_server_config.fld with \.Settings\config.fld in your startup
script. Like this:
* Del "%USERPROFILE%\creo_2_home\cache\PDMLink_cache\PTC\ProENGINEER\.Settings\active_server_config.fld"
* Echo f|xcopy "%USERPROFILE%\creo_2_home\cache\PDMLink_cache\PTC\ProENGINEER \.Settings\config.fld"
"%USERPROFILE%\creo_2_home\cache\PDMLink_cache\PTC\ProENGINEER \.Settings\active_server_config.fld"
David Haigh
There were two solutions to this problem which was caused by me disabling Creoagent (three if you include installing the latest Creoagent :-)):
Both worked and taking the path of least resistance, I elected to use the latter. Hopefully there won't be any unintended consequences 🙂
In Reply to Andrew Mansfield:
Ever since we've updated Creo 2.0 to build M110, we have been finding that Creo always opens in the workspace that they were last in before they were updated regardless of which workspace they were in when they last used Creo. Furthermore if the workspace is deleted then it is recreated on startup and Creo opens in it.. This seems to happen to everyone regardless of what build they were
I haven't been able to find out anything about this either here or at PTC. Has anyone else experienced this?
We're on Windchill (Pro/Intralink) 10.1 M040, Creo 2.0 M110 (updating older builds ranging from M030 to M100).