This message may occur when attempting access a seat of SolidWorks from the SolidWorks License Manager. The message will also include “(66,iActTransactionStartFlxActivateApp()/flxActAppActivationReqCreate() errored[8, 41013, 0])”.
This message can be caused if a user uninstalls the SolidNetWork License (SNL) and does not reboot the the system . Rebooting the system may resolve this issue.
If the above does not resolve this issue, it may be that FLEXnet Licensing Service is not running on the user’s machine.
From the Windows Control Select Administrative Tools.
Right Click on the FLEXnet Licensing service and choose Start
To avoid having this issue reoccur, right click on the FLEXnet Licensing service and choose Properties. In the Properties dialogue box, set the Start-up Type to Automatic.
To have a data card variable display the configuration name of SolidWorks files, set-up the variable as shown below.
The block name mus be set to ”SWCfgProperty”. In the above image the configuration name is being mapped to variable, but other configuration specific properties can be mapped to a variable. The below list identifies these properties and specifies whether they can be set to read/write, or read only.
Attribute: Name – Configuration name (read only)
Attribute: Description - Description (read/write)
Attribute: Comment – Comment (read/write)
Attribute: BOMPartNumber - Document name (read only)
Attribute: BOMUserSpecifiedName - User specified name (read/write)
SolidWorks 2013 has updated the API/script environment to VBA 7 (Visual Basic for Applications), which means that some of the methods used in the default Enterprise PDM SolidWorks task scripts (Convert, Print and Design Checker) need to be updated to be compatible with the new APIs.
Solidworks has provided detailed instructions and the default SolidWorks Enterprise PDM 2013 SP0 based task scripts for comparison. SolidWorks subscription customer can access this information, by logging int the Solidworks Customer Portal at www.solidworks.com and accessing the Knowledgeable. The article can be found by searching S-061260.
For those that have been using SolidWorks Enterprise PDM for a number of years and are updating from version that is number of release back, it may seem surprising that there is no No Red Plus Icon beside Vault in SolidWorks Enterprise PDM Administration. In earlier release with each major release, the archives needed to be updated after the installation SolidWorks Enterprise PDM . In more recent releases this is NOT required as an additional step.
When checking in or transitioning a number of files, you may want to route the files to different states. For instance, you may want to route SolidWorks files to one state and supporting documents to a different state.
Read More »
The information below is available from the Web Server Guide, which can be accessed from the Help file of SolidWorks Enterprise PDM Administration. I have been asked often enough about this aspect of the Web Server set-up, that I believed it was worth breaking it into its own blog article.
Read More »
Recently I ran into an issue where a SolidWorks Task failed. The task was set-up correctly and I was able to run the task on separate machine. On both machines the SolidWorks version and service pack were the same, but each installation was pointing a different vault. On the machine where the Workgroup vault was at the same version and service pack as the SolidWorks, the task worked. On the machine where the task failed, the Workgroup vault was on the same release, but on an older service pack. Once the Workgroup vault was updated to match SolidWorks, the task ran as expected.
It is recommended to always run both the Workgroup vault and Solidworks at the same service pack.
Log-in issues can often be the result of communication issues between the server and the client. A ping test as outlined in my article, Testing Connectivity to Archive Server Using the Ping test, can be used to check for communication issues.
Some log in issues can be a result of the logged in user account, not having full control of the client registry, specifically this key:
Granting the logged in user full control over this key, or one of its parents, should resolve this issue.
Local files can be created in a number of ways:
- If a file is saved to the local vault view while working off-line, it is not added to the vault and will only visible on the computer in which it was created and by the user who created it. By comparison these files will appear in a faded color.
Local files cannot be checked in, nor will other users be able to see the local files.
- If the folder or file is moved, deleted, renamed on a different client, you may have a left over locally cached copy. Clearing the local cache should resolve this issue. Clear Local Cache is available from Tools pull-down in the Local Vault View.
- If the currently logged-in user lacks permission to see the folder/file, and a user with permissions, previously cached the file to the Local Vault View.
- If user setting “Show only local files” is enabled. Please refer the my blog article EPDM – Grey Folders and Files in the local Vault View
Recently I have come across issues with NAS drives being used for the SolidWorks Enterprise PDM Archive. If you are considering using these appliances, please review the below statement, from SolidWorks, first.
Due to the many configurations and wide variety of virtual applications, Network Attached Storage (NAS), and Storage Area Network (SAN) appliances, it is not possible for SolidWorks to replicate all the permutations. SolidWorks therefore cannot certify the use of SolidWorks products operating in a virtual environment and on NAS and SAN devices.
The Enterprise PDM Vault, Workgroup Vault, and SNL license servers may operate without issue in these environments, however such configurations are unsupported.
The use of replication capabilities available with NAS and SAN devises may interfere with the Enterprise PDM Archive server replication.
Virtual environments force SolidWorks, eDrawings, and DraftSight to run in Software OpenGL mode resulting in significant graphics performance degradation
If software issues arise on an installation that utilizes these environments, SolidWorks and the Value Added Reseller will attempt to reproduce the issue on supported environments, and if validated, will pursue a solution.