SW assembly not opening part files / suppressing parts

[rmetzger]

Since we've jumped to SW2011 (sp 2.0) we've been having trouble with some assemblies not opening up all the referenced part files. During the process of opening the assembly SW will ask to locate the part file but will not load it when you manually point the assembly to the file. The parts in question are always present in the directory that SW is looking at, named correctly, and not corrupted. The assembly will open without it and show the part as suppressed. You can open the part file in question from the assembly by right mouse clicking on the suppressed part in the tree (opens normally) but the assembly will not allow the part to be unsuppressed. Opening the part in question prior to opening the assembly does not work either as the part still come in suppressed. Redirecting the part in the assembly to another part (even one that is open and showing in the assembly) will not allow it to be unsuppressed.

We've been seeing this quite often in the past few months and it happens on all the machines with no real resolution. any ideas?

 

[JMirisola]

Out of curiosity, have all the parts been converted from your previous version to 2011?

Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog

 

[rmetzger]

Yes - everything has been converted to SW 2011.

As a side note - the only way we've been able to fix the issue when it happens is to delete the part from the assembly and add it back in.

 

[ShaggyPE]

We have seen similar activity in 2010 when parts were renamed (not using SW explorer). In this past this was no big deal as long as the user was okay re-linking it to its assembly and drawing... but it was odd activity that was never there before.

-Dustin
Professional Engineer
Pretty good with SolidWorks

 

[CorBlimeyLimey]

Have not seen this in any version of SW.

Is there a common feature or option (patterns, display states, material, etc)used in the files (or assy's) which exhibit this problem?

 

[CorBlimeyLimey]

Have the parts or assys recently been moved, renamed, copied, ???

Next time it happens can you P&G to a ZIP, and post for testing?

 

[rmetzger]

some are old assemblies that were created in previous versions (exhibiting the problem prior and post being saved as 2011), and some are new assemblies that were created in 2011 only a few months ago. Its very random as to what part has issue and I've not seen a correlation with features, display states, or else yet. The most recent assy had been in the same folder for a while and had not exhibited the problem last week, pack and go created a copy with the same issue on my local machine.

This latest one has a lot of proprietary info in it but when I find a "dumber" one with the issue I'll upload it (or try to create one)