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

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

WORKSPACE FILE ERROR

ptc-2250450
1-Visitor

WORKSPACE FILE ERROR

I have a user who has been getting this error randomly and it takes him 10 to 15 times to log into intralink when he does get in and opens one of his workspaces intralink crashes and he gives himthe following error. Error attached as a jpeg.

Any help would be greatly appreciated

Dale


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
2 REPLIES 2

Dale

Looks like workspace corruption. Try renaming the .proi directory to something like .proi_old. Relaunch Intralink and see if that cures the crashing problem. This will be a fresh Intralink directory so all of the workspaces are gone and the files located in them. If this cures the issue then you will need to find out if there was anything needed in the old .proi folder. If there is some major work that needs to be recovered, then you will probably have to send that .proi contents to PTC. Over time these .proi folders get to a point of corruption. There is a log file associated to each .proi folder that usually causes issues as it grows over time and that can be compacted, but that only buys some time before you have to create a new .proi folder.

Good Luck

Eric Mills

Design and Project manager

http://www.rapidoconsulting.com

eric.mills@rapidoconsulting.com

Thanks to all who replied, We were able to delete all workspaces and all temp files (i.e .proi,trail and .framelogs) and then deleted the Local.ddb file. Things seem to be back to normal

Again, Thank You All

Announcements
NEW Creo+ Topics: Real-time Collaboration


Top Tags