Lost or Corrupted Local Workspaces

[ptc-72646]

Wildfire3 M230 PDMLink 9.1 M040 (VMWare windows server farm)

We're seeing an increase in workspace errors. A method server bounces and the Pro/E users authenticated to that server become disconnected. What happens is that when people reconnect their workspaces are entirely unavailable or worse (i.e. upon reconnection, Pro/E just blow out) Workarounds like creating new workspaces in a stand alone IE window or copying or prying open local cache files are hit and miss at best. Anyone know of settings or other work arounds for these issues?

Thanks,

Raymond Ford
Manager, Integrated Eng & Mfg Systems
Solar Turbines Inc.

[ptc-72646]

A question was asked... "When does the happen? Does the problem occur as soon as they re-connect to the server, or is it when they try to make the workspaces online (after being offline.)"

It's a good question. What we've found was this:

We'll it's funny... You can reconnect and Pro/E tells you you're "on-line" but it's really not. Something like creating another workspace actually forces the connection. Then when you try to open your "working" workpsace it either won't open or it blows out of Pro/E.

Raymond Ford
Manager, Integrated Eng & Mfg Systems
Solar Turbines Inc.
San Diego, CA 92186-5376