Hello, I have been using SW '06 and building a large assy., then had a hiccup and most of the parts have internal id errors and all the features were lost. I have no PDM software. The files are on a network drive, and most of the parts are used in other assemblies. Anything I can do to at least get the parts back?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
Solidworks '06 internal ID error, part lost all features
- Thread starter greggpost
- Start date
CorBlimeyLimey
Mechanical
Just open the last good backup copy and overwrite the 'corrupt' parts. You did make backup copies, right?
gwubs
Industrial
- Oct 10, 2002
- 290
Are the parts themselves corrupt when you open them seperately? Internal ID numbers in an assembly often refer to parts of the same filename but actually different files being found by the assembly. Do you have files with the same name in other folders?
- Thread starter
- #4
Saving a file in multiple locations is an offense punishable by 40 lashes around here, and probably the root cause of your headaches.
As gwubs said, the internal ID issue is when there are duplicate versions of the same file and the assembly tries to open one that is different from what was originally saved with the assembly.
Where it sounds like you don't have a backup of the assembly you can do a couple of things. One, rebuild the assembly from scratch.
Two, open the assembly and, one by one, find the missing part on the network, open it and then unsuppress it in the assembly. Do a 'Save as', saving the assembly over itself, while going through this process.
Three, find all the missing parts and move them to where they were when you created the assembly. You may very well end up with a bunch of mate errors, but you can deal with them if that happens.
Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog
As gwubs said, the internal ID issue is when there are duplicate versions of the same file and the assembly tries to open one that is different from what was originally saved with the assembly.
Where it sounds like you don't have a backup of the assembly you can do a couple of things. One, rebuild the assembly from scratch.
Two, open the assembly and, one by one, find the missing part on the network, open it and then unsuppress it in the assembly. Do a 'Save as', saving the assembly over itself, while going through this process.
Three, find all the missing parts and move them to where they were when you created the assembly. You may very well end up with a bunch of mate errors, but you can deal with them if that happens.
Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog
- Thread starter
- #7
Thank you to all, I have like 85% in the temp backup location. But when you open an assy, it looks for the parts in the last location, yes? So why would it matter if you have the same part in two different locations? Unfortunatly the company has no PDM software for SW. And why would all the features of the corrupted part file go missing?
Greg,
Pay heed to the good warnings you've been given: Multiple versions of files in different locations is a nightmare.
To answer the question in your last post, when you open an assy SWX looks for the parts in the last location it was pointing to for the particular files. Normally this is just what you want and the files are in the correct directory. HOWEVER, let's say you have just started SWX and opened a few parts in a different location. SWX is now referencing those parts where they are. If you then open an assembly that is looking for those same parts, but was expecting them in a different location, such as the ones the assembly last referred to, then you effectively have thrown things into the blender. The assembly was expecting the parts in one location, but the active session of SWX is overriding that with the parts that are open in another directory.
I do not mean to be harsh, but your comment about not seeing a problem with multiple copies/versions in different locations and why would it matter is an indication that you do not understand the fundamental relationships of the files and the care you must have in dealing with them.
Best advice is to learn how to use the PDM available in SWX (PDMWorks). If you will not or cannot do that then your next best option is to research this forum for threads relating to file management in lieu of a PDM. There has even been a very recent thread related this subject. This forum has great help and advice, but the users are more patient with those who have first done their homework and run through the tutorials and researched the forum before posting their questions.
- - -Updraft
Pay heed to the good warnings you've been given: Multiple versions of files in different locations is a nightmare.
To answer the question in your last post, when you open an assy SWX looks for the parts in the last location it was pointing to for the particular files. Normally this is just what you want and the files are in the correct directory. HOWEVER, let's say you have just started SWX and opened a few parts in a different location. SWX is now referencing those parts where they are. If you then open an assembly that is looking for those same parts, but was expecting them in a different location, such as the ones the assembly last referred to, then you effectively have thrown things into the blender. The assembly was expecting the parts in one location, but the active session of SWX is overriding that with the parts that are open in another directory.
I do not mean to be harsh, but your comment about not seeing a problem with multiple copies/versions in different locations and why would it matter is an indication that you do not understand the fundamental relationships of the files and the care you must have in dealing with them.
Best advice is to learn how to use the PDM available in SWX (PDMWorks). If you will not or cannot do that then your next best option is to research this forum for threads relating to file management in lieu of a PDM. There has even been a very recent thread related this subject. This forum has great help and advice, but the users are more patient with those who have first done their homework and run through the tutorials and researched the forum before posting their questions.
- - -Updraft
- Status
Similar threads
- Question
- Locked
- Question
