macPT
Mechanical
- Oct 22, 2002
- 607
Hi all!
I'm working on a design that was started in SW2004, continued with SW2005 SP1.1 and now with SP3.0.
I opened the top level assembly and the had the message: "SW encountered an error opening the document. Please contact your local SW support representative for help in troubleshooting this problem."
You can only imagine the panic...
But then I realised that no data was corrupted. After Ctrl+Q I was able to work, but SW would soon crash with the very informative "SW has terminated due to ab unhandled error... bla...bla...bla".
In two PC's with SP1.1 no problem was found (even after saving with SP3.0). After upgrading another PC to SP3.0, the same error ocourred.
After some hours of investigation, the problem was found in a subassembly, in a component pattern of several parts.
Supressing this pattern, fixed error. Creating a new pattern fixed the error. Editing the problematic pattern had
no results, except the fact of having erroneous behaviour with different selections.
Apparently nothing wrong was found in the earlier pattern and the working pattern is (apparently) equal. SW2004 and 2005SP1.1 never complained. So what could be causing the error? Mistery...
Regards
I'm working on a design that was started in SW2004, continued with SW2005 SP1.1 and now with SP3.0.
I opened the top level assembly and the had the message: "SW encountered an error opening the document. Please contact your local SW support representative for help in troubleshooting this problem."
You can only imagine the panic...
But then I realised that no data was corrupted. After Ctrl+Q I was able to work, but SW would soon crash with the very informative "SW has terminated due to ab unhandled error... bla...bla...bla".
In two PC's with SP1.1 no problem was found (even after saving with SP3.0). After upgrading another PC to SP3.0, the same error ocourred.
After some hours of investigation, the problem was found in a subassembly, in a component pattern of several parts.
Supressing this pattern, fixed error. Creating a new pattern fixed the error. Editing the problematic pattern had
no results, except the fact of having erroneous behaviour with different selections.
Apparently nothing wrong was found in the earlier pattern and the working pattern is (apparently) equal. SW2004 and 2005SP1.1 never complained. So what could be causing the error? Mistery...
Regards