Top Mistakes Made Moving SOLIDWORKS PDM Server Components

Moving SOLIDWORKS PDM Server components from one server to another (either as part of an upgrade or in itself) can be a daunting task. We recommend reaching out to our services team, as they will be able to efficiently and promptly perform this task for you. 

If you would instead like to continue with a DIY approach, the PDM Installation Guide Moving Server Components will provide you with the steps required to accomplish this. To avoid having delays during the process, this article explains the common mistakes made during the procedure. 

Top User Mistakes

I will address each of these common mistakes below: 

• Not checking the system requirements in the new server for the new PDM installation (if upgrading PDM as part of the move). 
• Not keeping an accurate record of your SQL sa password for your current PDM system
• Keeping the old server (or services) running while using the newly moved PDM system. 
• Failing to update the archive folders path in the new server’s registry keys
• Failing to inspect/update all registry keys in the new server 
• Not verifying the server move prior to continuing upgrading the client machines
• Not reactivating the license for a newly upgraded SolidNetWork License (SNL) Server installation (if also moving the SNL server) 
• Failing to load the archive server settings imported from the old server

Checking System Requirements in the New Server

It is common to move SOLIDWORKS PDM server components to a new server as part of the upgrade process. Given that a PDM upgrade may require an updated Operative System (OS) and/or SQL Server version, it is often preferred to move PDM to a new server with the upgraded system requirements. Make sure to not only pay attention to the SQL version but also the service pack. This is often an overlooked little detail that will save you time during the move/upgrade process (e.g. SOLIDWORKS PDM 2020 requires at least SQL 2014 sp3). As a reference, see the SOLIDWORKS and SW Data management system requirements

SQL sa password 

In order to start the process of moving your PDM server components to a new server you will need to obtain backups of the current PDM system; more specifically the file vault database and the ConisioMasterDb. Ensure you have access to the system administrator account (sa) which has by default full access to all databases on the SQL server or, alternatively, a login account with at least db_owner access to the databases. Relying on the windows authentication mode to access the databases and obtain a backup may prove risky if the logged-in Windows user account is not a member of the local Administrator’s group or if the account doesn’t have sufficient access rights. 

Failing to inspect/update Registry keys related to PDM in the new Server 

Although the archive server settings backup imported from the old server will restore the registry keys needed for the system to function properly there are still a few keys that will need to be updated manually; namely: 

HKEY_LOCAL_MACHINE > SOFTWARE > SOLIDWORKS > Applications > PDMWorksEnterprise > MailService

HKEY_LOCAL_MACHINE\SOFTWARE\SOLIDWORKS\Applications\PDMWorks Enterprise\ArchiveServer\Computers\local\Archives

HKEY_LOCAL_MACHINE\SOFTWARE\SOLIDWORKS\Applications\PDMWorks Enterprise\ArchiveServer\Vaults\vaultname 

HKEY_LOCAL_MACHINE\SOFTWARE\SOLIDWORKS\Applications\PDMWorks Enterprise\ArchiveServer\Vaults\vaultname\ArchiveTable

There are values in these keys that need to match the restored file vault database changes as well as the new archive folders location. Make sure to carefully inspect these keys to match the updated values.

Not verifying the server move prior to continuing upgrading the client machines 

Before you continue further upgrading the client machines verify the server move:

• Log in as the Admin user and view the file vault listing.
• Make sure that the archive server fully works by adding a text file, checking it in, and deleting it. 

If these steps fail, most likely the paths to the file vault archive folder specified in the registry keys are incorrect.

SolidNetWork License (SNL) Server 

As part of the process of moving server components you may or may not need to also move the (SNL) Server. If it does indeed need to be moved, make sure to reactivate the license on the new server.

Failing to load the archive server settings imported from the old server

During the configuring of the moved archive server loading the archive server settings, backup is often overlooked. Keep in mind this backup will restore registry key settings needed for the system to work properly. A common symptom of failing to perform this step is missing registry keys in the new server and/or not being able to find the vault in the administration tool.

Recommendations 

Perform the steps on a test environment prior to running the actual operation on the production vault (rehearse the steps). You will need to upgrade the SNL server (remember, it is backward compatible, so it can still be used by your current system after being upgraded), and point the test environment to the upgraded SNL. This will allow you a chance to run the test upgrade without affecting your production vault. If upgrading the SNL or pointing the test environment to it is not an option you may request a temp license that would allow you to test with.

If using a test environment is not possible the next best thing to do is to go over the steps prior to the upgrade.

If you are planning to upgrade the PDM system at the same time you move the components you will need to follow the section: Upgrading SOLIDWORKS PDM In addition to the instructions found in the section: Moving Server Components to Another System.

Lastly, if you are not familiar with the PDM system all too well and/or you would rather not spend the time moving it to a new server you can contact our PDM Services Department to set up an appointment and obtain a quote. They’ll be happy to schedule a time to take care of this for you. 

Learn More about SOLIDWORKS PDM

SOLIDWORKS PDM Web2 Guide: Server Setup, Accounts, Application Pools & Testing

Option File – A Great Solution for Managing Your SNL(s)

SOLIDWORKS PDM – Complete Guide to Client Installation

SOLIDWORKS PDM – Guide to PDM Standard Backups

Fixing SOLIDWORKS PDM Error Message: The Program and the File Vault are of Incompatible Versions

VIEW ALL SOLIDWORKS PDM ARTICLES