cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X

Inactive Worspace

MikeMarcoux
12-Amethyst

Inactive Worspace

We've been experiencing an odd issue with workspaces not activating.  We are currently using Creo3 M070, WC 10.2 M030-CPS09


When Creo 3 initially fires up, what ever workspace you are in is inactive by default.  Selecting "activate" from the -Pick an Action- menu does not activate the workspace.  There are only two solutions which we have found as a work around. 


  1. Switch to a different worksapce, and then switch back to the workspace you want, or
  2. Switch the browser to Chrome.  (this issue is specific only to IE)


We logged a ticket with support, and were able to reproduce the issue in the Webex, but PTC was not able to reproduce it on their end, so they closed it.  Their suggestion was to migrate to M100 or use Chrome.  Unfortunately, one of our clients who is in M100 is now having the issue as well. 


Has anyone else experience this, or does anyone have any insight?  We're a bit perplexed. 

ACCEPTED SOLUTION

Accepted Solutions
TomU
23-Emerald IV
(To:MikeMarcoux)

We occasionally run into something similar.  The short term fix is usually to restart Creo and/or delete and recreate the workspace.  The long term fix seems to be to delete and then recreate the entire local cache.

View solution in original post

2 REPLIES 2
TomU
23-Emerald IV
(To:MikeMarcoux)

We occasionally run into something similar.  The short term fix is usually to restart Creo and/or delete and recreate the workspace.  The long term fix seems to be to delete and then recreate the entire local cache.

MikeMarcoux
12-Amethyst
(To:TomU)

That seems to be the answer.  We, and our client, have to delete and recreate the local cache in order for this problem to go away.  They just upgrade to M100 from M070 today, and this issue just occurred today.  We updated to M070 from M050 when this started on our end. 

Announcements


Top Tags