
- Solidworks pdm could not connect to the archive server install#
- Solidworks pdm could not connect to the archive server 64 Bit#
- Solidworks pdm could not connect to the archive server software#
- Solidworks pdm could not connect to the archive server windows#
(The client needs to connect to the machine on which the service is running. (Vault may be down)”, try the following:Įnsure that a client can “ping” the Workgroup PDM Server service. If the vault appears to be running, but the client receives the message: “ERROR: Could not login to Workgroup PDM. Report persistent display errors to SolidWorks Technical Support.Ĭlient indicates vault is down or unavailable Users might not see files that exist in the vault if they do not have read permissions for the files and the vault administrator selected Hide projects with no access. If files disappear from the vault view, stop and restart the service. HKey_LOCAL_MACHINESoftwareWow6432NodeSolidWorksSolidWorks PDMWorks WorkgroupClientVaultAdmin PortĪll registry entries must be DWORD types.įiles disappear from the vault view window HKey_LOCAL_MACHINESoftwareWow6432NodeSolidWorksSolidWorks PDMWorks WorkgroupClientData Port HKey_LOCAL_MACHINESoftwareWow6432NodeSolidWorksSolidWorks PDMWorks WorkgroupClientRequest Port

Solidworks pdm could not connect to the archive server 64 Bit#
When a 32 bit version of SolidWorks Explorer is installed on a 64 bit machine, change the following registry entries: HKEY_LOCAL_MACHINESOFTWARESolidWorksSolidWorks PDMWorks WorkgroupClientVaultAdmin Port HKEY_LOCAL_MACHINESOFTWARESolidWorksSolidWorks PDMWorks WorkgroupClientData Port HKEY_LOCAL_MACHINESOFTWARESolidWorksSolidWorks PDMWorks WorkgroupClientRequest Port When SolidWorks Explorer is installed on a 32 bit machine, change the following registry values: Reboot each client computer after making the change. If a port is changed for the vault or VaultAdmin, then the corresponding registry value must be changed for each client in the paths listed below. HKEY_LOCAL_MACHINESOFTWARESolidWorksSolidWorks PDMWorks WorkgroupServerVaultAdmin Port HKEY_LOCAL_MACHINESOFTWARESolidWorksSolidWorks PDMWorks WorkgroupServerData Port HKEY_LOCAL_MACHINESOFTWARESolidWorksSolidWorks PDMWorks WorkgroupServerRequest Port Manually add DWORD registry settings through the following paths for computers running the vault and VaultAdmin: Only a system administrator should reconfigure the registry. Incorrect registry configurations can result in irreversible computer damage. If you create the registry DWORD value called “Request Port,” then the vault (or client) uses that port. For example, the Request Port is set to 40000 in the absence of a key. You must create registry keys for this procedure to work. Each port is stored as a DWORD in the registry.

In Windows, click Start, Run, then type regedit and click OK to access the Registry Editor.

Solidworks pdm could not connect to the archive server windows#
If you think a Workgroup PDM port conflicts with another application, (for example, you cannot check a document in to a project) you can change the default port setting in the Windows Registry Editor.
Solidworks pdm could not connect to the archive server software#
The Workgroup PDM software uses dedicated ports for communication. On the Exceptions tab, make sure PDM-Data Port, PDM-Request Port, and PDM-Vaultadmin Port are selected. To enable Workgroup PDM ports in the firewall setup:
Solidworks pdm could not connect to the archive server install#
If you install Workgroup PDM on a Windows XP system with Service Pack 2, you must enable Workgroup PDM ports in the firewall setup. SolidWorks Workgroup PDM Server Vaultvalidatevaultnextstartup.reg Port conflicts

However, if these options are not set and the Workgroup PDM Server service is not running, you can execute the following file to validate the vault the next time the service starts: The vault administrator can set options on the VaultAdmin Vault Settings tab validate the vault on the next startup or on every startup. Workgroup PDM Server service does not start
