Troubleshooting Corrupt Assemblies

Problem

When a file is corrupted, SolidWorks will usually give an error message, "SolidWorks encountered an error opening the document".  If this is happening in an assembly, the source of the corruption can be the assembly itself or one of the components within that assembly.  

Solution

The steps below can help narrow down the source of corruption:

  1. Go to File->Open and select the assembly, but do not open the file yet.
  2. Under the configurations dropdown, select <Advanced> and click Open.

    open file configurations advanced mode
     
  3. In the Configure Document dialogue box, select "New configuration showing assembly structure only" and enter a configuration name.

    Configure Document window open new configuration showing assembly structure only
  4. Click OK, and the entire assembly will open up with all the components suppressed.
     
  5. If the error message mentioned above appears immediately, there is likely an issue with the assembly file itself, and it needs to be remade.  If not, please continue with the steps below.
     
  6. Unsuppress components one at a time, going down the list.  If the error message appears after unsuppressing a particular component, the corruption is likely related to that file.  
     
    • If that particular component opens up by itself, without any issue, delete and reinsert it into the assembly.
    • If that component opens by itself, with an error, it should be remade or submitted for review with technical support.

      Unsupress components in SOLIDWORKS context menu

For further technical support, please contact Hawk Ridge Systems at 877.266.4469 for the U.S. or 866.587.6803 for Canada and support@hawkridgesys.com

Was this article helpful?
8 out of 8 found this helpful

Articles in this section

Comments

1 comment
Date Votes
  • Also worth mentioning under this title is when an assembly has been diagnosed as corrupt without an error message. These can be issues where the assembly is not working correctly and there is no usage issue that can be seen. In such a case, the solution may be to do the following:
    1. Open a new "blank" assembly
    2. Insert the problematic assembly as a sub-assembly into this new assembly
    3. Right-click on the sub-assembly and select Dissolve Sub-Assembly

    1

Please sign in to leave a comment.