Community Page
- www.solidsmack.com/ Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
- 2 Years, 800 Posts and a Fab New Look.
- 4 Ways to Share Content Stinkin’ Quick, The Best and How They’ll Totally Advance CAD/PLM
- PTC/USER - SolidSmack on the Scene, Crispy and Cleeeeean.
- Yes You Can! Graphic Design for Print and Web Using SolidWorks
- Eeny, Meeny, What Comes Next? High End CAD on OS X.
-
Recent Comments
- Smacktastic! Congrats, Josh. I think all that sweat and hard work will pay off.
- Thanks a lot..this article will useful for me for reducing features by using 3D sketches.
- wow!! now i can draw a bunch of sketches and create really sweep geometry in Solid Works...thanks for your help..thanks a lot
- You should add one additional arguement into this command: Part.CompConfigProperties4 2, 0, True, "config1", False It should be: Part.CompConfigProperties4 2, 0, True, True,...
- WOW..Such a Great resource for all of us Web designers...You Rock Man !!
SolidSmack
SolidWorks 3D CAD Technology Design Blog
Seriously, this feature needs to be turned off.
In lieu of that, here’s some ways that can often times help you get around that wonderfully obscure message.
First of all, I have no idea what causes that message to come up. Maybe one of you SolidWorks wizzes do. From the d ... Continue reading »
In lieu of that, here’s some ways that can often times help you get around that wonderfully obscure message.
First of all, I have no idea what causes that message to come up. Maybe one of you SolidWorks wizzes do. From the d ... Continue reading »
1 year ago
1 year ago
Great tips! I have been running into this periodically since 2007.
1 year ago
Hey, I've got to ask you. Are you running some kind of modified Windows XP theme or Vista? The reason I ask is the close icon in your image looks much different from the norm.
Best Regards,
Ricky Jordan
http://www.rickyjordan.com
1 year ago
I'm running an optimized windows them called CrystalXP. It looks nice but also reduces RAM consumption.
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
Thanks Martin
1 year ago
Good luck
1 year ago
Closing and reopening the assembly file without closing SolidWorks or the part files will solve the problem but any changes made to the assembly before closing, of course, it will be lost. I am generally working with a small assemblies of 10 or 12 parts with 5 or 6 assembly configurations.
Today a light bulb went on in my head and confirmed what I have been suspecting for some time now. I have noticed that sometimes if I am moving or selecting something with my optical mouse, the failed to save message pops up right then and there even though I was not manually saving at the time. I suspect that when an auto save occurs coinciding with certain kinds of mouse activity, somehow the OS can't cope with those simultaneous commands. After one of the mouse-induced spaz sessions occurs, the assembly cannot be saved anymore while the parts still can.
I am running Windows XP Professional X64 Edition and the X64 version of SolidWorks.
I don't have a solution but I am curious to learn if anyone else has noticed the mouse and auto save connection. In earlier versions of SolidWorks with Windows XP 32 bit OS on a different computer and mouse I encountered total freeze-ups of the computer when moving the mouse and selecting on the fly without holding the mouse completely stationary. Both of these mouse induced problems only happen once in a while; anywhere from once a week to a couple times a day.
1 year ago
1 year ago
1 year ago
1 year ago
@JB man, that sounds weird, although would be the first time hardware affected software, but I've never noticed optical mouse conflicts. Could possible be a conflict with mouse driver and SolidWorks??
11 months ago
I have found this error or related error on two occasions.
1) Working on a network run by a samba server. The temporary files that SW creates are not handled well by SAMBA and for some reason when you go to open the file, the leftover temporary files show as real files and "ACCESS TO AN UNNAMED FILE..." turns up. If you happen to open an assembly which accesses these file, then "Failed to Save Document" comes on. Working on a local drive corrected this problem (PDMWorks was implemented with Windows XP)
2) Memory being chewed by SoliDWorks stops the ability to say and can sometimes be fixed if you free some memory and go through the steps that a few of you have mentioned - change configs rebuild, etc then try to save again.
My 2c
11 months ago
9 months ago
I have been using solidworks since 97 and its been getting worse with every release....more and more issues happen during a normal session of detailing than I care to mention, load another service pack....end up with more issues. this really sucks, maybe the programmers should start getting these comments on a regular basis then something will happen, lower the price if it not going to work correctly out of the box!!!!!dis appointed
9 months ago
I am still very tired of havingthese issues on a daily basis, as most people trying to get things done on a quick time line.
9 months ago
9 months ago
Rebuild EVERY SINGLE configuration seems to work for me. Only rebuilding a few of the configurations does not work usually.
Also check out: http://gxsc.typepad.com/graphics_systems_solidn...
7 months ago
7 months ago
7 months ago
5 months ago
5 months ago
http://blog.alignex.com/mechanical-technical-bl...
3 months ago
3 months ago
1 month ago
1 month ago