Hello to all,
Welcome to this new edition of the SolidWorks Support Monthly FAQ. The news this month consist in the release of 2013 SP4.0 and the 2014 Beta program.
SolidWorks 2014 Beta program
The beta phase of SolidWorks 2014 has already started!
Visit the 2014 Beta site and click "Sign Up" to be part of the program. You can also keep updated on the latest Beta News and be part of the beta community on the SolidWorks 2014 Beta Forum.
Participating in the 2014 Beta Program is an excellent opportunity to learn about the new functionality and how it can help your design process before SolidWorks 2014 is released. You can also check that new features correspond exactly to you needs and if not help us fine tune them thanks to your feedback.
What's more, the SolidWorks 2014 Beta Program includes 28 individual contests where you can show off your SolidWorks skills and get points and valuable prizes for testing the software: official 2014 Beta Tester t-shirts and Amazon gift cards.
Together we can make the 2014 Beta Program the most successful ever!
If you have any questions please post them on the forum.
Service Pack News
Service Pack 4.0 of version 2013 has been in EV for three weeks now, so some of you may have already tested it. It should be officially released anytime now. It fixes many issues and increases performance, but it also adds some usability improvements. They will improve your experience working with SolidWorks. Here is a short list of such enhancements:
• SPR 686824 : Option to 'Enable Cell drop down lists' can now be changed after the design table is created.
• SPR 659016 : Existing SolidWorks sensors (mass, measurement, etc) will now correctly appear in Design Study Constraints or Goals
• SPR 687527: The performance of the Change State dialog has been improved. It should open much faster.
To get the full list of fixed SPRs in any service pack of version, log in the Customer Portal and click on Fixed SPR list in My Support:
Noteworthy Solutions from the SolidWorks Knowledge Base
What could cause the history dialog to be completely empty (shows no history entries) for a file in an Enterprise PDM 2013 SP0, SP1 and SP2 file vault??
If you have a file data card with many "Version Free" type card variables and the variable names are using long names or many version free variable values are updated at the same time - it is possible that the history dialog fails to list any file history for an updated file. See below for how the empty dialog appears.
This is a problem that affects Enterprise PDM 2013 SP0, SP1 and SP2 and was reported under SPR 690066.
To identify if the file that you are seeing an empty history dialog is affected by this SPR and to get a workaround, see Solution ID: S-063147.
Note: This problem was addressed in Enterprise PDM 2013 SP3, upgrade to that version or higher.
Can SolidWorks Explorer 2013 and SolidWorks Workgroup PDM 2013 VaultAdmin be installed on a Microsoft Windows Server 2003 machine?
No, SolidWorks Explorer 2013 and SolidWorks Workgroup PDM 2013 VaultAdmin are not supported on Microsoft Windows Server 2003.
For more details, see Solution ID:
What is the correct reinstallation procedure of SolidWorks® with prerequisites for Windows® 8?
This procedure comprises several solutions: S-031198, s-046201 and S-047790 (if working with PDM).
A pdf document comprising all this information and solutions is attached to Solution ID: S-063228.
What could be the reason if defeature preview is not shown in few SolidWorks assemblies?
One of the reasons could be that you are using 'Windows 7 Basic or Windows Classic' theme.
Verify the theme on Windows 7. If the theme is set to 'Windows 7 Basic or Windows Classic', the defeature preview of assembly may appears blank. It is always better to use an Aero theme.
See Solution ID: S-063344 to learn how to change the theme.
When will SolidWorks Composer be supported on Windows® 8 operating system?
SolidWorks Composer is currently expected to be supported on Windows 8 operating system from SolidWorks Composer 2014 release onwards ( Solution ID: S-063343).
What could cause a crashing issue when using simulation where the file ‘MSHTML.dll’ is found in the Application Event logs?
In a few separate occasions it was found that the MSHTML.dll file was corrupted. To correct the issue it was found that running a Windows update and uninstalling Internet Explorer 10 or 9 corrected the issue. This is because the "mshtml.dll" is one of the important DLL related to Internet Explorer.
For the full procedure, see Solution ID: S-062904.
How to define a surface body (shell) thickness variable parameter in a Design Study
The illustrated procedure is given in a PDF attachment to Solution ID: S-063041.
That’s it for this month. Thanks for reading this edition of SolidWorks Support News. If you need additional help with these issues or any others, please contact your SolidWorks Value Added Reseller.
Also, comments and suggestions are welcome. You can enter them below.