I recently updated to Solidworks 2017. As soon as I did, I noticed that any assembly that I have virtual components in give an error upon loading that the files are not found. However, when I open the same file in Solidworks 2016, the components show up fine.
Has anyone else had this issue?
It was modeled in SW2016 SP5.0. I currently have SW2017 SP3 loaded, I’m downloading SP4.1 currently. What makes it even stranger is this: In the assembly that I am looking at, sw2017 specifies the missing part as ” C:\Users\jeff.kucmierz\AppData\Local\Temp\swx6708\VC~~\ASE Conveyor Section\ASE Conveyor Belt^ASE Conveyor Section.sldprt”. If I have the assembly open in SW2016, I can find the file in the directory “C:\Users\jeff.kucmierz\AppData\Local\Temp\swx7248\VC~~\ASE Conveyor Section\ASE Conveyor Belt^ASE Conveyor Section.sldprt”. I then copied the directory swx7248 and its contents and renamed it to sw6708, which I figured should have solved the issue. It didn’t. However, if, after doing so, I open the part first in sw2017, save it, close it, then try and open the assembly, it works fine.
Are you sure the part is still virtual? When you go to File, Fine References In Folder should say "<save internal to assembly>" for your sldprt. If it does not then your part is no longer virtual.
The part is still virtual.
Virtual components created in SW 2017 work fine in SW 2017. Not sure about components from SW 2016. We have skipping both 15 & 16 versions.
What kind of error are you getting? Is the part showing as suppressed, or something else?
The part is showing as suppressed.
If you still have access to SW2016 you might need to open it there, save the Virtual Part out as an independent Part, close the Assembly, open it in SW2017, and then Browse to the Part (or have it open before opening the Assembly). If that works you can make it Virtual again.
While I have done that with the assembly in question, this has occurred on other assemblies that have virtual components. I should not have to do this on every assembly I have virtual components in.
If you go to component properties, what do you see in the Model Document Path? Also if you right click on the component do you see Save Part (in External File)?
Jeff Kucmierz wrote:
While I have done that with the assembly in question, this has occurred on other assemblies that have virtual components. I should not have to do this on every assembly I have virtual components in.
You're right. I never said otherwise. I was just trying to help you solve a problem.
We have not seen this error since converting from 2016 to 2017. We use virtual parts pretty much on every design.
I would say it is something local to your machine and Solidworks.
If you are seeing it multiple places I would assume a setting or path has changed maybe.???
Just strictly guesswork on my part.
Hope you find an answer.
This week, I upgraded from 2016 SP5 to 2018 SP1, and experienced same issue described above by OP.
One key common detail here is that both of the file locations prompted for (his and mine) are in [User]\AppData\local\temp ...
Among other recommendations for performing a clean install, instructions include clearing or deleting those files with Maintenance tab in Solidworks Rx.
i.e., I did this to myself!
It does not affect every virtual component, but appears relatively random. However, our use of virtual components is widespread, so that something is virtual in just about every assembly we create.
I can cope a handful of these issues, but really hope that our legacy data is not universally messed up. Here's what I can cynically expect: The detailed customizations of these components, for example mixed profile weldments with trim/extends and cuts and mount holes applied, will need to be reproduced tediously from reverse engineered production documents. This will happen randomly, and unpredictably add rework time which should not be necessary.
Every single virtual component is saved internal to assembly. That's what makes it virtual. How this data can be misplaced during upgrade transition is baffling and frustrating to me.
(Here I was about to shout praises of enhanced performance and stability upon upgrading. I am a habitual observer of system resources so that I can watch how this workstation is handling what I'm demanding of it. It was clearly evident to me that 2018 uses less than HALF of the RAM which was consumed by 2016 SP5 in the same large assembly and its drawing.)
I am merely adding to the topic, as it is not limited to 2016 to 2017 upgrade. I am not seeking same answers found above. I've been through what others have already suggested. Work is already being redone, as its reference has been destroyed. Dead topic is updated. Maybe this can help inform someone else.
I even met the same bug in case of one SWX version 2017 and 2018. I renamed assembly with virtual subassembly and virtual parts and virtual parts inside it several times after this I saved assy and closed it.
After opening assy I received the message that virtual parts or subassies are missing. The path was something like this C:\Users\Igor\AppData\Local\Temp\swx292. I don`t know why SW use this temporary path if it keeps them inside assy file.
Auto saving is switched off.
From what service pack of SW2016 to what service pack of SW2017. I just created a simple assembly consisting of virtual components only in SW2016 SP5.0 and it opened just fine in SW2017 SP4.1 Was your assembly with virtual components created in SW2016? We had issues with virtual components in SW2014.