Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
Hi everybody,
one of our designers has a new workstation with Creo 2.0 M160 (server windchill 10.2). When starting Creo on the new pc he always has the first workspace in the workspace-list active. Seems like Creo doesn´t save the change of the active workspace.
E.g. list of workspaces:
- "workspace 1"
- "workspace 2"
- "workspace 3"
Starting Creo => "workspace 1" is active
Changing active workspace to "workspace 3"
Restart Creo => "workspace 1" is active
While working in Creo there is no other problem (access rights, server connection, ...)
Any suggestions?
Best Regards,
Benjamin
Solved! Go to Solution.
Hi,
I found the problem.
Our additional software creates if necessary a new .wf-directory (client-cache) in the user folder (%appdata%). The problem was caused by trying to create the subfolder .settings in .wf (%appdata%/.wf/.settings/). Sometimes after cleaning the client-cache (.wf folder) the software could not create this folder (it will instead create a file called .settings). This folder keeps the server settings (and other setting stuff). Without this folder, Creo could not store the settings.
Create the .settings folder saved the problem 8until next clien-cache-cleanup).
Best Regards,
Benjamin
Sounds like Creo Agent either isn't running or is the wrong version. When you launch Creo, does "creoagent.exe" show up in the list of Processes in the Windows Task Manager?
Yes it shows up. In fact we´re using a additional software StartupTools to store (and load) our settings on a server. Our support told us to add a parameter to the StartupTools-settings, so now it works for one user (me). Other user using the pc have differenz problems. I assume something with the acccess rights on the server folder.
Have to concat the IT
Hi,
I found the problem.
Our additional software creates if necessary a new .wf-directory (client-cache) in the user folder (%appdata%). The problem was caused by trying to create the subfolder .settings in .wf (%appdata%/.wf/.settings/). Sometimes after cleaning the client-cache (.wf folder) the software could not create this folder (it will instead create a file called .settings). This folder keeps the server settings (and other setting stuff). Without this folder, Creo could not store the settings.
Create the .settings folder saved the problem 8until next clien-cache-cleanup).
Best Regards,
Benjamin