Matthew West

SolidWorks Support Monthly FAQ - December 2010

Blog Post created by Matthew West Employee on Dec 10, 2010

This month’s edition of SolidWorks Support Monthly FAQ covers a few of the most common questions and issues handled by the support team over the past month, as well as recent updates to the SolidWorks Knowledge Base.


Top questions and issues

1.     Can the 2011 SolidNetWork (SNL) License Manager provide licenses for older SolidWorks versions?


The 2011 SNL License Manager can provide licenses for SolidWorks 2011, 2010, 2009, 2008, 2007, 2006, 2005, and 2004.



2.     Why do I receive an “Activation Count Exceeded” error when activating the 2011 SolidWorks SNL Manager on the same server that a 2010 SNL Manager was activated on?


This problem is being investigated by development as SPR 581747.  The current workaround is:


  • Uninstall the 2011 SNL Manager (deleting its Program Files installation folder as well)
  • Reinstall the 2010 SNL Manager
  • Run the 2010 SNL Manager and transfer the activation
  • Uninstall the 2010 SNL Manager (deleting its Program Files installation folder as well)
  • Reinstall the 2011 SNL Manager to activate
  • Activate the 2011 SNL Manager


3.     How can I accurately measure the memory usage of SolidWorks?

Having the correct memory usage info is valuable when investigating performance issues or trying to determine if you've outgrown a 32-bit environment. For a 32-bit environment, the default memory limit for an application is 2GB.  If tracking memory use with the method below shows that SolidWorks (sldworks.exe) is frequently hitting the 2GB limit, or is always operating near that limit, consider moving to a 64-bit operating system and 64-bit SolidWorks to avoid application terminations due to insufficient memory.


To find out more, please click here


4.     How long will SolidWorks support Windows XP?

Microsoft officially retired the Windows® XP operating system in April of 2009. SolidWorks 2011 will continue to support Windows XP (32 and 64 bit versions), excluding operating system-related issues or fixes. This level of support will continue through at least one release following SolidWorks 2011. After that, in conjunction with Microsoft’s support policies, only the Windows Vista® and Windows 7 (32 and 64 bit versions) operating systems will be supported.


The SolidWorks operating system support plan outlined above will also apply to the SolidWorks Simulation and SolidWorks Enterprise PDM product lines. Refer to Knowledge Base Solution ID#S-012513 or the SolidWorks Release notes for the latest on this.



New Knowledge Base articles


1.     S-051869 - How does the SolidWorks Rx graphics card check work?

You can now determine whether your graphics card is supported and your driver is up to date by using the Diagnostics tab in SolidWorks Rx.  If your driver is out of date, a new Download driver button allows you to download the latest SolidWorks certified driver. SolidWorks Diagnostic graphics card check connects to our database of certified graphics card and compares PC system, video device, display driver, operating system and release of SolidWorks.


To go to this KB Solution, please click here


2.     S-052165 - After upgrading to SolidWorks 2011, when opening assemblies some of the custom parts OR parts saved out of Toolbox folders are replaced with the standard Toolbox parts. What could be the reason?

A new option was introduced in SolidWorks 2011 under Tools->Options -> System Options -> Hole Wizard/Toolbox: Make this folder the default search location for toolbox components.


When this option is checked, SolidWorks will look for the files only in the Toolbox location that has been defined under the HoleWizard/Toolbox path if you open any assembly that contains some custom parts, or some toolbox  copied parts (even though the parts are located in the same folder of  assembly). The parts will be replaced with native Toolbox parts from the Toolbox folder. Prior to introducing this option, Toolbox files would be inserted from the Toolbox file location when added to an assembly but did not always open from the same location later. This caused confusion in some environments.


Solution S-02518 in the SolidWorks Knowledge Base elaborates on this case.  The new option ensures that files always open from the specified Toolbox location. If you frequently use copied Toolbox parts that exist outside of the Toolbox folders, then this option may be interfering with your setup. Uncheck the option to restore the SolidWorks 2010 behavior.


To go to this KB Solution, please click here




Thanks for reading this month’s SolidWorks Support Monthly FAQ. If you need additional help with these issues or any others, please contact your SolidWorks Value Added Reseller.