1-Visitor

Question

Workspace Corruption

Forum|Forum|13 years ago
February 8, 2013
29 replies
6280 views

Hi all,

I am running WC 10.1 M020 with Creo/Elements Pro M160. Weare having major workspace corruption issues. Some users have to delete their local cache a couple of times a week due to workspace corruption as this seems to be the only thing that will allow them to access their workspace. We also see ProE crash often when trying to synchronize the workspace from the workspace browser.The issues seem prevalent to almost all users but some are worse than others.Is there anything that I can check or do that might help. The issues seem random but are happening daily. Just this week we have probably had the issue 20 times.

Thanks,

Brian

Other

Show previous replies

L

Lohbauer

1-Visitor

Just to confuse matters more, I just had a user, whose auto_upload_on_save is set to automatic,have a workspace blowout that somehow cost him some files and assemblies that were all supposedly uploaded to the server-side workspace.

Has anyone heard of that type of fail? I was under the impression that it was the local cache that was vulnerable. According to my user: he lost data out of his Server side workspace

Jacobs Vehicle Systems

R

RandyJones

20-Turquoise

On 02/12/13 14:11, Bob Lohbauer wrote:
>
> Just to confuse matters more, I just had a user, whose auto_upload_on_save is set to automatic, have a workspace blowout that somehow cost him some files and assemblies that were all supposedly uploaded to the server-side workspace.
>
> Has anyone heard of that type of fail? I was under the impression that it was the local cache that was vulnerable. According to my user: he lost data out of his Server side workspace
>

Keep in mind that only new or checked out items actually upload. Modified but not checked out items do not upload.

> Bob Lohbauer
>
> Windchill Administrator
>
> Jacobs Vehicle Systems
>
>
> -----End Original Message-----

--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

E

egifford

12-Amethyst

Bob,

Considering what Randy stated I just did a little experiment. I have a single component assembly and that component part model in my workspace. The part model is checked out and is modified in session. The assembly model is modified in session, but not checked-out and therefore ineligible for upload.

a) with auto-upload-on-save turned off, save the assembly model. The changes in the assembly and the part are saved to the workspace cache. In the workspace, select both files and attempt a manual upload. The part model uploads because it is eligible and the assembly model does not. Message area in Pro/E states "upload succeeded"

b) same scenario but with auto-upload turned on. From the assembly model, initiate a Save. Both the assembly model and the part model are successfully saved to the workspace cache, but the upload operation fails for BOTH models. The Pro/E message bar states "upload failed" with the assembly model file name listed when in actuality, neither uploaded.

Wondering if scenario b is what your user ran into. I'd have to do more testing but it seems that with upload-on-save, if the save operation includes anything that is ineligible for upload, nothing gets uploaded. This is contrary to how a manual upload from a workspace functions.

This is the kind of scenario that has me hesistant to turn auto-upload on. People may become dependent on it and pay even less attention to the actual status of the items in their workspace.

Erik

J

jfrankovich

12-Amethyst

That is the kind of scenario that kept us from using auto_upload as well. We had users with large workspaces and family tables turning on that option, thinking it was more secure, but in practice it made their overall data less secure as they were less aware of the unsuccessful workspace activities.

I am anxiously awaiting the day (hopefully soon) when non-checked out objects are eligible for upload so we get a better, more secure local workspace.

L

Lohbauer

1-Visitor

Agreed,

Thank you Randy for pointing it out and to Erik for proving it. The second scenario sounds most reasonable. In my case the user had new models that had been successfully uploaded but not checked in. It was one of the new uploaded/ Not checked in files that was lost.

Is it possible for a new file (Never checked in) to be uploaded to the server workspace then be lost to local workspace corruption?

Bob

E

egifford

12-Amethyst

Have to say that sounds a little weird. I've never seen the loss of data that had been uploaded to the server side, but we haven't had that many corruptions (probably just cursed myself by saying that).

In one case of what seemed to be a toasted workspace cache, we accessed the server side from an external browser and checked-in anything we wanted to save. We were going to then blow away the workspace and take the loss on whatever was only in the cache (not uploaded). When we started Pro/E the next time, the workspace suddenly behaved - all the data, even cache-only files, were fine. Very bizarre, but if you run into a corruption it's worth trying.

Back to the "What is the cause?" issue though, I'm thinking overly busy Methodservers or excessive network traffic between user and server may be contributing factors. Correllation isn't necessarily causation, but when we've had corruptions where the cache was truly hosed it has occurred when issues of that nature were present. Thoughts?

M

MikeFoster

10-Marble

Hi Bob,

We try to train our users to look at their Workspace status in order to not lose work.

Here are the three scenarios for objects that are not uploaded:

[cid:image001.jpg@01CE09E0.474CC1A0]
Mike Foster
ATK

L

Lohbauer

1-Visitor

Mike,

Nice graphic, thanks.
I need to reevaluate the auto_upload_on_save Policy.

Bob

D

DanielReid

12-Amethyst

I encourage everyone to vote up that idea for uploading even modified objects that are not checked-out (