This edition of SolidWorks Support News covers the most common questions and issues by the support team, as well as recent updates to the SolidWorks Knowledge Base.
Top Questions and Issues:
1. My.SolidWorks is now available!
My.SolidWorks is a new community experience that helps you connect, discover and share everything SolidWorks. My.SolidWorks can be accessed by anyone at http://my.solidworks.com.
2) SolidWorks 2013 SP3 is available for download from the Customer Portal as of April 10th, 2013.
3) S-062340 - What can cause one of the following license errors to display when starting up SolidWorks Composer, "Cannot find license file" or "No such feature exists"?
The "Cannot find license file" error can be seen on machines that have never had a SolidWorks product activated.
The "No such feature exists" error can be seen on machines that already have a SolidWorks product activated, or that had a SolidWorks product activated at one time
Some known reasons for this are:
- You've installed without entering a SolidWorks Composer serial number. Uninstall and reinstall Composer WITH a serial number to resolve this.
- You've installed with an SNL serial number, but have not specified an SNL server to connect to. Use the client-side SNL manager to add a proper SNL server (Start > All Programs > SolidWorks 2013 > SolidWorks Composer 2013 > SolidWorks Tools > SolidNetWork License Manager)
4) S-062526 - How does Enterprise PDM handle Windows user login where same user exist in multiple locations (for example as both a local and as a domain user)?
When using Windows login type in an Enterprise PDM file vault it is only the Windows login name (profile name) that is stored in the file vault database. The user password is managed by the Windows server, either the local Windows server hosting the archive server service or the Windows Active Directory server. The domain tag is also not part of the username in the file vault.
This means that in order to log in to a file vault, the Windows login name must match the name of the user in the vault and the Windows server must accept the credentials.
The login name must also exist as an explicitly added user or part of a local or domain group added to the Windows login settings on the archive server.
In most cases, the Windows user will only exist in one location (either as local user on the archive server or as user on AD server). Entering the login name and password will log you in to the vault.
If the same user login exists on both the local server and on the Active Directory server, EPDM will try to log in with the local user credentials first before trying the AD credentials. That means that if the passwords differ, it is possible that the user ends up logging in with a seemingly “old” password because the local account is used primarily. Same could happen if the user login exists in multiple domains that the archive server has access to.
The archive server will store which domain or system name the most recent successful login was using in the vault registry key "UserCache". See example in attached PDF.
5) S-062414 - Why do I get an error showing "Error reading the file c:\xxx\export.cex" when trying to import or open an Enterprise PDM export file (.cex) in the administration tool?
The most likely reason is that you are trying to import at .cex file that was exported in a newer major version of Enterprise PDM. For example the export file was created in Enterprise PDM 2013 SP2 and you are trying to open it with a client running Enterprise PDM 2012 SP4.
The .cex format is in most cases not forwards compatible, meaning that you cannot import a file created with a newer major version of EPDM. It should however be possible to import .cex files created with older versions. Export files created with different service packs of same major version should be compatible (for example EPDM 2012 SP5 .cex imported to a 2012 SP3 setup).
If you are sure that the versions are compatible, and you still get an error opening the .cex file, the file is likely bad. Try getting a new export file from the source system.
New Knowledge Base Articles:
1) S-062477 - Why is it that the "Delayed in State" workflow notifications do not generate when using a non-english language Enterprise PDM 2013 file vault?
Enterprise PDM 2013 introduces a new type of workflow notification that can be assigned on states to send a reminder notification to a recipient if a file has been in a state for longer than a specified number of days.
When using a file vault created with English language, the delayed in state notification will generate for files that have triggered the notification.
If using a file vault created with a language other than English, the workflow delay notifications will not generate, even if files have been in the state for longer than specified number of days.
This could happen when the file vault is missing the proper notification templates to generate the delayed in state notification from.
When a file vault is created, or upgraded, the default notification template from c:\program files\solidworks enterprise pdm will be imported to the vault database. The notification template is named NotificationMsgTemplate_XX.csv where XX represents the language..
In an English language vault using Enterprise 2013 there should be 23 notification templates. You can see this by viewing the database table “NotificationMsgTemplate”. Types 700, 701 and 702 are used for workflow delay notifications.
In a file vault created or upgraded with a non-English language however, the localized notification template files are missing the correct workflow delay notifications. The NotificationMsgTemplate table will only contain 20 templates (Type 700, 701 and 702 are missing).
This problem is affecting Enterprise PDM 2013 SP0-SP2 and is reported under SPR 695477.
Another symptom of this problem is that the Task success notification in a non-english language file vault may show parts of the delayed in state notification in the bottom of the notification.
To correct the problem in a non-English EPDM 2013 SP0-SP2 file vault you need to import the fixed notification templates that contains the missing notification types. See details in attached zip within KB Solution S-062477.
2) S-062366 - Why can I not use face selections as reference geometry when defining loads in SimulationXpress?
In SimulationXpress you can only select planes as reference geometry, not faces.
3) S-062627 - Does the Augmented Reality (AR) functionality within eDrawings Viewer for iPad work on the first generation iPad?
The first generation iPad is not suitable for the usage of the Augmented Reality in eDrawings App due to the lack of cameras.
Note: For additional information on the augmented reality functionality, see http://blogs.solidworks.com/solidworksblog/2013/02/augmented-reality-in-edrawings.html
4) S-062687 -What can cause the dimension value of an entity in a DWG to be less precise (not exactly the same) as the dimension value to the same entity in SolidWorks after exporting to DWG?
In order to obtain the exact precision, please increase the image resolution of the drawing and referenced component document to high before exporting to DWG.
1) Open Part
2) Go to Tools, Options, Document Properties, Image Quality
3) Increase the "Shaded and Draft quality HLR/HLV resolution" and "Wireframe and High Quality HLR/HLV resolution" to high.
4) Press Ctrl-Q
5) Open Drawing and repeat steps 2-4
If increasing the image resolution in the drawing and referenced component does not resolve the issue, please report this to your local SolidWorks Reseller.
5) S-062654 -Why do some symbols have red dots on connections?
The difference has to do with what options are set for each symbol's property.
Select a symbol to edit from the Symbol Library and click the symbol name to see the symbol properties listed below it. Under Options, there is a check box item 'Display connection points:'. If it is checked, the symbol will show the red dots. If it is unchecked, it will not.
6) S-062346 - Can you edit the size of symbols in Electrical 2D?
Yes. Both existing symbols in the symbol library as well as imported custom symbols can be scaled through the symbol manager.
1. From the symbols manager (found under the library tab of the Ribbon Menu), right click the symbol that needs to be edited and select open
2. In the graphics zone, select the symbol from top left to bottom right
3. From the Ribbon Menu, select the drawing tab
4. Select Scale from the Edit section
5. Follow the prompts in the Side Panel to choose base point coordinates
6. Next enter the desired scale factor and use the check box option to include or exclude the attributes in the scale
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.