This month’s edition of SolidWorks Support News covers the most common questions and issues handled by the support team, as well as recent updates to the SolidWorks Knowledge Base.
1. Windows XP Retirement, SolidWorks 2013 and Windows XP -
If you have not yet already moved to Windows 7, we strongly encourage you to upgrade to Windows 7 now and be ready to take advantage of the new capabilities coming very soon to SolidWorks 2013. SolidWorks 2013 will not install on Windows XP. Additional information will be available during the SolidWorks 2013 Beta Program this summer
Other variations of the error may be the following:
- "The entitlement information received from the Installation Manager server is corrupt;"
- "A Serial Number could not be verified because of a temporary problem connecting to the server"
First, please verify that you have an Internet connection. If you have an Internet connection the most likely explanation for this is excessive volume or traffic connecting to the SolidWorks entitlement servers.
This may also be an indication of peak download traffic on the SolidWorks servers. During the first few days after a new service pack or major version is released, download traffic may be at a peak at the time you are attempting to accessing the download. If this occurs, please be patient and try the download \ install \ upgrade again later.
3. S-058787 - What causes $PRP custom property title block annotations to not show updated values in the Enterprise PDM 2012 SP2 preview or eDrawings® 2012 SP2 unless
a drawing (slddrw) is opened and resaved in SolidWorks?
If eDrawings 2012 SP2 is installed and you try to preview a SolidWorks drawing that has title block annotations using $PRP links to the drawing custom properties, the property values that are updated outside SolidWorks will not show as updated in eDrawings 2012 SP2 unless the drawing is opened and resaved. Values are updated outside of SolidWorks, for example if using the Enterprise PDM workflow or data cards to update values in a Windows Explorer file vault view.
This problem is a regression in eDrawings 2012 SP2 and has been reported under SPR 639609. It has been corrected in eDrawings 2012 SP3.
The problem affects the annotations both when previewing drawings in the Enterprise PDM preview tab, and opening them in eDrawings standalone application.
Note that if you are not using eDrawings 2012 SP2 to view or preview the drawing, but still see the issue, it is likely that the SolidWorks Document Manager API is not correctly installed on the system. Document Manager is a prerequisite in order for eDrawings to see updated $PRP custom propert values. Document Manager is automatically installed when installing the thick Enterprise PDM client types.
First confirm that you are using eDrawings 2012 SP2. Start eDrawings and select Help, About. The version should read 126.96.36.199. You can perform either workaround A or B, depending on the end user's needs.
A: Uninstall eDrawings 2012 SP2 and install an older or newer version where problem is not present.
B: Use attached eDrawings 2012 SP2 hot fix.
1. Reboot system if EPDM has been in use.
2. Run hot fix:
64-bit OS: HotFix_x64_639609.exe
32-bit OS: HotFix_639609.exe
Manual install instructions:
If the automatic hot fix install does not work or if you need to distribute the fix via other methods, refer to attached SPR639609_Hotfix_ManualInstallInstructions.txt.
4. S-058681 What’s the basic difference between SolidWorks Plastics Professional and SolidWorks Plastics Premium?
SolidWorks Plastics Professional is targeted at part designers and allows for the filling analysis of a single part with one or more injection locations and any plastics material from the Simpoe database. Results include a fill time plot, pressures, temperatures, weld lines, air traps, and much more. It also includes an automated report generator that allows users to easily communicate their findings to other members of a design-to-manufacturing team.
SolidWorks Plastics Premium is targeted at mold designers and mold makers and contains everything in the Professional version but also allows for the analysis of multi-cavity and family mold layouts, the packing phase of the injection molding process and sprues, runners, and gates.
5. S-058853 - What causes new Toolbox parts created using the "create parts" option in SolidWorks 2012 Toolbox to remain as local files in the file vault view and are not
automatically checked in?
When Toolbox is configured for "Create parts" and Toolbox is hosted in an Enterprise PDM file vault, it is possible that SolidWorks 2012 fails to add the newly created parts to the file vault automatically. The Enterprise PDM integration in Toolbox should normally add such files to the file vault when inserted from toolbox.
This happens because of the following SolidWorks 2012 regression issue:
SPR 643798 "Toolbox ignores 'When accessing Toolbox use permissions from' in EPDM when 'Create Parts' (Copied Parts) setting is used *2012 regression*"
If you are using a SolidWorks version affected by this problem, use the following workaround:
- Make sure that the Toolbox setting in the Enterprise PDM Administration tool for "When accessing toolbox use permissions from" is set to "<Logged in User>". (see attached CreateParts_1.jpg)
- Make sure each user that uses toolbox to create parts has "add file" folder and workflow permission to the "Create parts" output folder.
- If the created parts remain local and are not added automatically to the vault, make sure the user setting (right-click user(s), Settings) for "Adding files" page contains "sldprt" in the list of file extensions. (See attached CreateParts_2.jpg)
With these settings; the created parts will automatically add to the vault, but you will have to manually check them in as this is not done automatically. Normally you would check in the newly created parts when you check in the assembly you inserted the part into.
- S-058882 - How do you create an Enterprise PDM Dispatch action that writes (updates) the file version to a data card field when file is checked in?
In order to update a file data card variable when file is checked in you need to trigger the dispatch action on the "check in" condition with setting "before check out change has occurred". See attached DispatchCheckinAction_1.jpg.
If you trigger the action "after" the check in has happened, the file will be read-only and you will get an error trying to update the data card variable.
To write the version of the checked in file (i.e. the version that is created during check in), use the "set card variable" command and then use the "Add" method to wite current version + 1 (current version of the file is the version that is checked out, the next version will be the checked in version). See attached DispatchCheckinAction_2.jpg.
Attached is a Dispatch action example that updates a variable called "Version" when files are checked in. Before importing the action, create a variable "Version" and put it on the data card of files that should update.
Note that this action will only trigger when local file is modified, if no changes are made to the file the check in will trigger an undo-check in command and the dispatch action will not trigger.
Also note that the check in action will not trigger when you perform a change state that updates variable values in the file. To write the version of the file that change state creates, add a "set variable" transition action using the %NextVersion% transition variable. See attached DispatchCheckinAction_3.jpg.
2. S-058704 - When a thermal resistance contact set is defined, why does the mesh in the area of the contact set sometimes appear compatible and other time incompatible?
The mesh in the region of the thermal resistance contact set can depend on any of the following:
- Mesher type (curvature based mesher will typically generate only an incompatible mesh in the region while the standard mesher MAY generate a compatible looking one).
- Whether a split line is defined between the entities of interest to exactly define the projecting areas involved in the thermal resistance (if there is no split line, the mesh will most likely appear incompatible).
- The presence of a global bonded component contact condition and whether it is set to compatible or incompatible.
- SolidWorks version in which the geometry was created.
- SolidWorks version in which the study was created.
Most importantly, please note that the actual formulation used by the solver is always incompatible in the sense that nodes are never merged in the region where a thermal resistance contact set is defined. This is because thermal resistance contact can only be either node to surface or surface to surface. Neither of these contact element types (node to surface and surface to surface) actually uses merged nodes. The node to surface type uses nodes from one set of entities and projects them onto element sub-surfaces on the other set (not directly to nodes on the other set). Surface to surface uses element sub-surfaces between both sets. So in actuality whether the mesh appears compatible or incompatible should not have a significant effect on the results – a sufficiently good element density and proper definition of split lines will have much more of an influence on result quality. Please note that in a case where the mesh does appear compatible, it's just because the nodes are coincident (overlapping). They are not actually merged.
In summary, the user should ensure the following:
- The mesh within the entities defined for the thermal resistance contact sets has sufficiently small elements (do a mesh convergence study on an isolated area of interest to find the optimal element sizes).
- Split lines are defined to exactly identify the areas participating in the thermal resistance.
Please see attached a simple model with several studies defined showing the results are almost identical regardless of the compatible/incompatible appearance of the mesh.
3. S-058966 - Is there an installation log created for the SolidWorks Plastics installation? Where is it found?
There are up to three setup (installation) files created. These can be found in the installation directory. For an installation using the default directory, these are:
"C:\Program Files\SolidWorks Plastics x64 Edition\SolidWorks Plastics Setup Log.txt"
"C:\Program Files\SolidWorks Plastics x64 Edition\SolidWorks Plastics x64 Edition Setup Log.txt"
The files can include vcredist_x86, vcredist_x64, and either SolidWorks Plastics Setup Log (32-bit install) or SolidWorks Plastics x64 Edition Setup Log (64-bit install). The Setup Log will always be present but the vcredist may not be present if that component is previously installed.
4. S-058765 - When creating a Simulation or SimulationXpress (SimXpress) Report, a “Processing image” pop up window appears periodically and report generation takes a very long time. Why is this happening?
This is most likely due to the SolidWorks Export Options > File Format > TIF/PSD/JPG settings which affect how images are captured in SolidWorks as well as Simulation reports. To check if this is the problem, do the following:
1) Go to File > Save As
2) Select Tif (*.tif) for Save as type, then click Options
3) If the “Print capture” option is currently selected, change it to “Screen capture” and click OK
4) Click Cancel in the Save As dialog (the changes you made to Export Options will be saved regardless of whether you click Save or Cancel in this window)
5) Try generating/publishing a report again
Please refer to the SolidWorks Help topic “TIFF, Photoshop, and JPEG Export Options” for additional information on these SolidWorks settings.
Screenshots are also attached to the Knowledge Base Solution as a reference.
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.