Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X
Utilizing the same configuration files and settings: If I start Creo without the trail file being automatically run and run it manually it works perfectly.
Server Management - Without Trail File Ran Automatically
If I start Creo with the same trail file being run automatically the saved server is no longer shown. The trail file seems to run correctly as the second blank tab is opened successfully.
Server Management - With Trail File Ran Automatically
Not sure what is causing this.
Trail file is very simple as it just opens a second blank tab currently.
~ Activate `main_dlg_cur` `EMBED_BROWSER_SMARTAB_LAYOUT_buttons_lay_ph.pshNewPage_inside` 1
~ Activate `main_dlg_cur` `EMBED_BROWSER_SMARTAB_LAYOUT_buttons_lay_ph.page_0` 1
~ Trail `UI Desktop` `UI Desktop` `SmartTabs` \
`selectButton main_dlg_cur@EMBED_BROWSER_SMARTAB_LAYOUT_buttons_lay page_0 0`
The shortcut target is set to the following:
"C:\<INSTALL_PATH>\Parametric\bin\parametric.exe" "C:\<INSTALL_PATH>\StartupTrail.txt"
Thoughts on what is causing this
Solved! Go to Solution.
You have automatically started the trail and there is only <No Server> in the "Server Management" window.
After that, just register (add) your wt-server manually again in the "Server Management".
Then restart Creo with your trail file.
Server registration will be kept.
The trail breaks wt-authentification process.
You should start with the trail and register the server again.
It will force Creo to remember server status.
And then restart with the trail.
So trail file would set the website, then register the server each time? Wouldn't this remove user's workspaces? Or am I not understanding the suggestion.
Appreciate the help.
You have automatically started the trail and there is only <No Server> in the "Server Management" window.
After that, just register (add) your wt-server manually again in the "Server Management".
Then restart Creo with your trail file.
Server registration will be kept.
Just had to re-register the server which caused no issues on any users workstations.
Thanks for all the assistance.