This month’s edition of SolidWorks Support News 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. SolidWorks Early Visibility Period for SolidWorks 2011 SP4
The Early Visibility (EV) release of SolidWorks 2011 SP4 is coming soon, targeted for availability the week of May 23rd. This upcoming Early Visibility period will be the most extensive EV period (3 weeks compared to typical 2 weeks) of all SolidWorks 2011 Service Packs. The Early Visibility (EV) program provides you with an opportunity to review and test a Service Pack before general release. Take advantage of this opportunity to review SolidWorks 2011 SP4 prior to the full release. Additional information, including sign up instructions, is available at http://www.solidworks.com/sw/support/EarlyVisibility.html.
2. Is a beta program planned for SolidWorks 2012 this summer?
The SolidWorks beta program is returning this summer. Stayed tuned for additional information with further details over the upcoming weeks. The beta program is an excellent opportunity to preview new functionality in the upcoming SolidWorks 2012 release, to interact with SolidWorks technical staff, influence which new functionalities are considered, and a chance to prepare your organization for the latest improvements in the software.
3. After upgrading the operating system from 32 bit to 64 bit, SolidWorks displays low resource notifications and becomes very sluggish at times. Shouldn’t a 64 bit operating system resolve this?
There are other system resource and performance bottlenecks that exist with 64-bit operating systems that can impact SolidWorks. The amount of physical RAM installed on the computer is a resource worth investigating. In some cases, additional RAM may be needed to resolve the low resource notification. Even though 64-bit-capable applications like SolidWorks x64 can leverage 8 TB of virtual memory, a large part of SolidWorks' (and any other application for that matter) performance and responsiveness is driven by the amount of physical RAM installed. If there is not enough physical RAM, then any additional memory needs to be accessed from the page file located on the hard drive, which is typically much slower than accessing RAM. This may not have been an issue for users who previously had Windows XP 32-bit installed with 4 GB of RAM because of the default 2GB virtual memory (2-3GB with 3/GB switch) architectural limit inherent with 32 bit. Now that these limits are increased on 64-bit, there is the potential for memory intensive applications such as SolidWorks to address more memory than is available in RAM. This can occur very frequently on 64-bit computers running SolidWorks x64 with just 2-4 GB of RAM installed.
To find out more, please go to S-052388
Desktop Resources (User Objects and GDI objects) are also system resources that do have a finite limit and can also impact SolidWorks.
To find out more, please go to S-048683
New Knowledge Base articles
1. What is the solution for SPR#487453 (thumbnail previews of SolidWorks files not updating in Windows Explorer)?
The source of this problem is SolidWorks' shell extension caching. This is enabled by default and is intended to improve performance of thumbnail and icon display inside Windows® Explorer.
In Windows XP, this problem will be seen when viewing Thumbnails inside of Windows Explorer. In Windows Vista® / Windows 7, this problem will be seen when viewing Small Icons, List, Details, and Tiles inside of Windows Explorer.
Beginning with SolidWorks 2011, if a user is experiencing the symptoms of SPR #487453, thumbnail caching can be disabled to resolve this issue. One of the attached registry files can be applied to one's computer to disable thumbnail caching. To find out more, please go to S-055085
Note: A correction for the issue described in SPR#487453 has been targeted for SolidWorks 2011 SP4.
2. What are the most common errors received when testing replication connections in the SolidWorks Enterprise PDM administration tool?
The attached PDF in Solution S-055138 describes what the most common replication test connections errors are, along with specific actions that can be taken to resolve them.
The errors below are covered in this document:
- Failed to connect to target server using address <System Name> on port 3030 from client!
- The target server cannot download from the source server!
- Failed to send test data to target server from client!
To find out more, please go to S-055138
3) Why is the “individual installation” option grayed out (not selectable) when running the SolidWorks Installation Manager?
There are two possible causes for this. The first is that a newer version of the same major release is installed. The second cause of this is that the DVD being used or the downloaded Installation Manager does not match the system architecture.
To find out more, please go to S-054679
Thanks for reading this month’s SolidWorks Support News. If you need additional help with these issues or any others, please contact your SolidWorks Value Added Reseller.
The SolidWorks Support Team