AnsweredAssumed Answered

Error Opening an Assembly

Question asked by Peter Kennedy on Jul 5, 2016
Latest reply on Jul 5, 2016 by John Stoltzfus

Like • Show 0 Likes0
Comment • 8

I have a large assembly made of of multiple sub assemblies, and there is one sub assembly that is causing issues when I open the file I get the following error message. There is assemblies within the sub assembly that are missing.

I will suppress the whole sub assembly and then open that sub assembly individually and it opens fine with no issues. I then unsuppress the sub assembly in the main assembly and everything is when it needs to be.

I save everything and then try and re open the main assembly and same error message comes back.

I can't post the files for confidentiality reasons.

Steve Calvert Jul 5, 2016 10:39 AM

Correct Answer

The first thing I do is to check the top level PN references. Are all the sub-assemblies loading from a location that is correct? Perhaps this bad sub isn't loading from where you think it should be loading from and that causes a problem...

Steve C

See the reply in context

No one else had this question

Outcomes

T. Byrne Jul 5, 2016 10:29 AM

Are you using EPDM? If so, try clearing local cache.

Also, check for cyclical issues. Assembly within an assembly as reference, but the inserted assembly is also at a higher level, for instance.

I've caught my engineers using an enveloped assembly as a reference in a subassembly, then using that subassembly withing the assembly they are using as a reference. SolidWorks gets very angry at this.

Actions

Peter Kennedy @ T. Byrne on Jul 5, 2016 10:38 AM

Not using EPDM, everything is local on my machine, no cyclical issues everything is inserted in the proper levels.

Actions

T. Byrne @ Peter Kennedy on Jul 5, 2016 10:40 AM

Sorry, but sounds like simple file corruption. You may want to swallow the confidentiality concerns and send a copy to your VAR to see what they can do, or, delete and recreate the trouble subassembly.

Actions

Steve Calvert Jul 5, 2016 10:39 AM

Steve C

Actions

Peter Kennedy @ Steve Calvert on Jul 5, 2016 11:20 AM

This was exactly it, the references were they were supposed to be however when it was opening they pulling the files from another location which they were corrupt in that folder. Deleted that folder and the model opened with no issues.

Thanks.

Actions

Steve Calvert @ Peter Kennedy on Jul 5, 2016 11:27 AM

I always check the simplest way first. Are the files where you think they should be?

Glad that worked for you.

Steve C

Actions

John Stoltzfus @ Steve Calvert on Jul 5, 2016 11:56 AM

Thanks for the tip - I didn't have that issue in years, but it's good to know.

Actions

John Stoltzfus Jul 5, 2016 11:13 AM

Try these settings in RX

Try this option first

If you have the same results then try this setting

If the assembly opens without the error then save the assembly file and reboot the computer and see if all is ok....

Actions

8 Replies

T. Byrne Jul 5, 2016 10:29 AM
Mark Correct
Correct Answer
Are you using EPDM? If so, try clearing local cache.

Also, check for cyclical issues. Assembly within an assembly as reference, but the inserted assembly is also at a higher level, for instance.

I've caught my engineers using an enveloped assembly as a reference in a subassembly, then using that subassembly withing the assembly they are using as a reference. SolidWorks gets very angry at this.
Like • Show 0 Likes0
Actions
- Peter Kennedy @ T. Byrne on Jul 5, 2016 10:38 AM
  Mark Correct
  Correct Answer
  Not using EPDM, everything is local on my machine, no cyclical issues everything is inserted in the proper levels.
  Like • Show 0 Likes0
  Actions
  - T. Byrne @ Peter Kennedy on Jul 5, 2016 10:40 AM
    Mark Correct
    Correct Answer
    Sorry, but sounds like simple file corruption. You may want to swallow the confidentiality concerns and send a copy to your VAR to see what they can do, or, delete and recreate the trouble subassembly.
    Like • Show 0 Likes0
    Actions
Steve Calvert Jul 5, 2016 10:39 AM
Unmark Correct
Correct Answer
The first thing I do is to check the top level PN references. Are all the sub-assemblies loading from a location that is correct? Perhaps this bad sub isn't loading from where you think it should be loading from and that causes a problem...

Steve C
Like • Show 1 Like1
Actions
- Peter Kennedy @ Steve Calvert on Jul 5, 2016 11:20 AM
  Mark Correct
  Correct Answer
  This was exactly it, the references were they were supposed to be however when it was opening they pulling the files from another location which they were corrupt in that folder. Deleted that folder and the model opened with no issues.
  
  Thanks.
  Like • Show 1 Like1
  Actions
  - Steve Calvert @ Peter Kennedy on Jul 5, 2016 11:27 AM
    Mark Correct
    Correct Answer
    I always check the simplest way first. Are the files where you think they should be?
    
    Glad that worked for you.
    
    Steve C
    Like • Show 1 Like1
    Actions
    - John Stoltzfus @ Steve Calvert on Jul 5, 2016 11:56 AM
      Mark Correct
      Correct Answer
      Thanks for the tip - I didn't have that issue in years, but it's good to know.
      Like • Show 0 Likes0
      Actions
John Stoltzfus Jul 5, 2016 11:13 AM
Mark Correct
Correct Answer
Try these settings in RX

Try this option first

If you have the same results then try this setting

If the assembly opens without the error then save the assembly file and reboot the computer and see if all is ok....
Like • Show 0 Likes0
Actions

Error Opening an Assembly

Outcomes

Related Content

Recommended Content