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:
- S-057076 - What is the difference between the SolidWorks 2011 Toolbox Folder Structure and the SolidWorks 2012 Toolbox folder structure?
In the SolidWorks 2011 version if you drill into a browser folder from a SolidWorks 2011 Toolbox, you'll see that there are only two folder levels and the last contains every single part file in that category. For example, if in Windows Explorer you browse to the Browser->Ansi Inch->Washers folder, within the “Washers” category you see every single washer.
In the 2012 version we are introducing a third level folder.
- S-057065 - In SolidWorks 2012, is the Toolbox still dependent on the Access database (swbrowser.mdb) for information?
In SolidWorks 2012, the Toolbox no longer depends on the Access database (Please note that Hole Wizard will continue to use this Access database as its source of information).
The data stored in various tables in the database such as sizes, lengths, drive types, part numbers, and properties, will now be stored in each part file.
- 'Error 1935. An error occurred during installation of assembly component' message appears when attempting to deploy SolidWorks Enterprise PDM 2012 SP0 via an administrative .msi image.
This issue has been identified in SolidWorks Enterprise PDM SP0 in SPR#628286 and has been corrected for SolidWorks Enterprise PDM SP1.
New Knowledge Base articles:
- S-057402 - What could cause the Enterprise PDM API to return empty variable values from a Bill Of Materials (BOM) when using Enterprise PDM 2011 SP5 or 2012 SP0?
If you are using an API add-in to read BOM variable values via the IEdmBomCell::GetVar method, and the installed Enterprise PDM version is 2011 SP5 or 2012 SP0 then it is likely that the method returns an empty string instead of the proper value.
The problem has been corrected in Enterprise PDM 2012 SP1 and a hotfix for 2011 SP5 and 2012 SP0 can be found in the Knowledge Base Solution.
- S-057107 - How is a symbolic link (MKLINK) folder used to have Enterprise PDM cold storage move files to a network share folder?
Currently when using Cold Storage in Enterprise PDM to move files from the vault archive, the output folder must be a local folder on the archive server. Cold storing to a network share is not supported (SPR# 405191).
If the archive server is running on Windows 7, Windows Vista or Windows Server 2008, you could use the MKLINK command to create a Symbolic Link to a network share. A symbolic link is essentially a folder shortcut available to the file system, where the target can be another folder or even a network share. Define the symbolic link folder in the cold storage schema and the archive server service will output files to that folder, believing it is a local folder where in reality it creates the files in the linked target folder instead.
- S-057107 - What could be the reason a grey "local" file or folder remains in the Enterprise PDM local file vault view (cache) after you rename, move or delete the file or folder?
A grey folder indicates you are viewing a "local" copy of a folder that is found in the local vault view cache but not present in the file vault. Files that are only present in the local cache but not the vault also show up with a dimmed grey icon and their status column shows <Local File>.
There are several normal reasons you may see the folder or files as local:
- If the folder or file is moved, deleted, renamed on a different client, you may have a left over locally cached copy. See KB solution S-043537.
- If currently logged in user lacks permission to see the folder/file, and a user with more permission previously cached it.
- If folder/file failed adding to the vault, or was added in offline mode.
- If user setting "Show only local files" is enabled.
If you are moving, renaming or deleting folders or files locally then the local folder/file should normally be removed. If it however is left behind as a local copy it usually means the removal of the local folder/file fails, most likely because there is some other process still holding on to it.
- S-055316 - How is it determined which SQL server version is installed on the server hosting the Enterprise PDM file vault database?
It is very useful when troubleshooting Enterprise SQL issues to know the exact version of SQL you are working on. This KB solution contains information explaining how to obtain the SQL version used and then check this version number to identify the exact release.
- S-057276 - What could cause Enterprise PDM 2010 and newer to hang when adding, editing datacards, changing state, checking in or previewing certain DWG files containing Multileader annotation entities?
When Enterprise PDM processes DWG files it will use a file format plugin called the 2DEditorPlugin.dll. This plugin will in turn use DWG API calls to read block/attribute information, extract thumbnails and XRefs between DWG files. When previewing DWG files, the plugin will normally use the installed eDrawings to preview the file.
- Why do I get different stress results when I change the size of the solid mesh? Are the results incorrect?
This can be due to insufficient mesh density or due to so called singularities. With solid elements we recommend at least two layers of second order elements across any cross section of any solid body. Please also mesh any fillet surface with at least two layers of elements.Stress peaks at restrained faces and sharp corners which change with increased mesh density are due singularities. Singularities can be resolved by decreasing the level of idealization locally. For example adding a small filled at a sharp internal corner will help, even if it is a very small one. To overcome the problem at a restrained face, include a section of the restraining geometry and add a fillet.
To find out more, refer to the following KB solutions: S-027232, S-042775, S-052477, S-035431.
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.
On behalf of the SolidWorks Technical Support team, we wish everyone Happy Holidays and a great New Year.
The SolidWorks Support Team