BUGS in solidworks premium 2018!
I tried several times to use save bodies'' while ''creating assembly'', the error message pops up.
please suggest, thanks
Two reasons for this error:
1. Your File path is more than 255 characters in path name (including extension)
2. No write permission for SOLIDWORKS installation directory.
get rid of the dashes.
hmm?.. dashes are legal.
Hrmm....I notice that the path you are saving to and the path that come up in the error window don't match.
Therefore, I suspect that this might be a template issue:
Check here and make sure that these are set to valid templates:
Also check here:
You are probably correct, but shouldn't he get a "useful' warning? I think that warning belongs over at Your favorite Solidworks error messages
It's the path, not the file name, that's invalid.
That path is a program file directory and you probably don't have permissions for a direct write into it.
And for good reasons.
Save your SW project files in a "regular" folder and you shouldn't see any error message.
If you notice, the OP isn't saving in the file that is listed.
This is why I think that maybe he doesn't have valid templates listed and it is trying to do something with the templates and failing.
I have been wrong before though.....
I missed that there's no file name in the error dialog, just an extension.
You think it's an undefined template that SW is struggling to write?
Kevin Chandler wrote: Hello, I missed that there's no file name in the error dialog, just an extension.You think it's an undefined template that SW is struggling to write? Kevin
Kevin Chandler wrote:
I think that, possibly, the OP recently migrated to Solidworks 2018 and has yet to update his template references or that the carryover templates from SW 20XX are having issues upgrading or corrupt. Can anyone confirm that this action (that the OP is doing) will automatically upgrade a template that is from a previous version if it hasn't been upgraded? Or would they have to open the template and re save it before this action?
There are a few ways to test this:
Check the template references and make sure that they point to actual template locations.
Use a different command that automatically grabs a template (like the mirror command in assembly) and see if you get the same error (although you might not, because that would be for a part template and not an assembly template).
There are probably more ways..
I Just crashed into this issue. Having just moved to a new machine, I thought the file locations perhaps weren't correct, but they were.
Having gone to 2018 upon the machine upgrade and reading your remarks about template locations, checked these which were also correct. Still get the problem.
So I opened my assembly and part templates and saved them. Problem solved. Obviously hadn't updated the template files so even though they were in the correct location and working fine through creating parts and assemblies, Save bodies didn't seem to like the 2017 template files.
I recall having a similar problem with 2015. If I remember correctly, it was because I didn't have correct permissions
Its definitely the same error I had. I've remembered some more details...
My old laptop died and I bought a new one without an OS. I had my old win 7 pro serial but no installation, so used a win 7 home edition install. I then ran intothis problem, my VAR told me the home edition was not supported but we managed to fix it by creating some kind of super administrator account and then using this account to give my logon the relevant permissions
my solidworks 2018 premium just installed on windows 10 together with solidworks simulation premium and flow simulation.
so far, it is just around one month to use the new system.
It is crazy! it is happened again when filling the split part file name.
..sw has a bad habit of recalling past paths..and it seems like your sw folders are write protected?
the working sw folder is full controled by user/administer
Just FYI, since this is still happening in SW2019, and not everyone has write permission to C:\Program Files\Solidworks. As a work around, you can create a dummy part and/or assembly, and do a save-as into the directory that you want to save to. That allows the feature to work.I don't know the root cause. Could be some sort of template corruption, or it could just be a bug, but people don't notice it often since they either run SW as admin, or have already saved a file to a write-able directory in their current solidworks session before trying to do Save Bodies or a Split. There's noise of this on this forum for probably the past 10 years, and several SPRs that seems to align with it. E.g., 755521 or 914683.
Retrieving data ...