PDM Server

Registry Keys

If the PDM server has already been deployed, there is only one way to change the hostname used to resolve and connect to the server by clients and thats via the registry.

Update the following registry keys on the server to change the hostname:

HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise
HKEY_CURRENT_USER\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ConisioAdmin\Servers

Then change the registry keys on the clients to change the hostname:

HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\Databases\<vault name>
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SolidWorks\Applications\PDMWorks Enterprise\Databases\<vault name>
HKEY_CURRENT_USER\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ConisioAdmin\Servers
HKEY_CURRENT_USER\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\Vaults\<vault name>

Then double check license server as well as licensing within the administration tool to make sure it is fqdn.

Troubleshooting

The PDM vault by default uses the hostname (not the FQDN) to communicate with the license server. If you are seeing errors in the PDM administration logs that look like the below examples, then you need to add the hostname (solidworks-pdm) to your machines hosts file and point to the internal IP for the license/pdm server 10.0.10.55.

Example Log Messages:

The following database error has occured:
  State:08001,Native:5,Origin:[Microsoft][ODBC Driver 17 for SQL Server]
State:08001,Native:5,Origin:[Microsoft][ODBC Driver 17 for SQL Server]
State:S1T00,Native:0,Origin:[Microsoft][ODBC Driver 17 for SQL Server]

Location:
  Db::mbOpen()
Description:
  Named Pipes Provider: Could not open a connection to SQL Server [5]. 
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
Login timeout expired

The following database error has occured:
  State:08001,Native:26,Origin:[Microsoft][ODBC Driver 17 for SQL Server]
State:08001,Native:26,Origin:[Microsoft][ODBC Driver 17 for SQL Server]
State:08001,Native:10060,Origin:[Microsoft][ODBC Driver 17 for SQL Server]
State:08001,Native:10060,Origin:[Microsoft][ODBC Driver 17 for SQL Server]

Location:
  Db::mbOpen()
Description:
  Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server.
Client unable to establish connection
TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Cannot connect to archive server this error can occur after an unintended restart of the SOLIDWORKS server. The archive server is supposed to start at boot however, there is a chance that it may not actually start. Begin by logging into the SOLIDWORKS server. Next, in the the Windows search bar open Services. Scroll down to find SOLIDWORKS PDM Archive Server. Select and start this service, wait a few moments and then test again.