Sounds like his Workspace may be Corrupt. There are a few ways to check on this. First, does the event manager "red stop sign" show up at the bottom of the screen indicating a warning or error? If so go to the Event Manager and try to decipher its message. If not, go to the folder location where the cache is saved, this will either be on the local hard drive or a network location depending on how your company has chosen to set it up. Location should look something like this if you are on Release 8 may be different for 9; \PTC\ProENGINEER\Wildfire\.wf\.cache2\"yourwindchillserver". Once you have a window up to monitor the cache, sort it by date with latest on the top. Check to see if there are sid and lid files with timestamps that correlate with the users latest saves. If there are any files starting with tmp_ and multiples of this type of file; the workspace is definitely corrupt. If everything looks ok in the cache area, have the user check in their assembly if possible. At the first screen that comes up, scroll through it and look for anything that could cause the assembly not to upload or check in. If nothing, hit the next or finish button. If it fails to check in the event manager may give you a clue. If this still fails, I have my users back up their work to a Pro/BACKUP folder, create a new Workspace, activate the new Workspace, open the assembly from the Pro/BACKUP folder and once its up Save it to the Workspace. The biggest drawback to this method is dealing with all the file name conflicts if the assembly uses existing files. The previous Workspace should eventually be Deleted and the name of that Workspace should never be reused. Just a side note to all of this; we have found that switching between Workspaces can cause Workspace corruption. Because of this we now make it common practice to exit Pro/E, re-launch, and then switch Workspaces. I don't get nearly the calls of corrupt Workspaces now. Hope this helps. Craig Clough CAD Administrator
