goglfamily.blogg.se - Solidworks pdm could not connect to the archive server

#Solidworks pdm could not connect to the archive server update
#Solidworks pdm could not connect to the archive server windows

Next we need to update the client registry Update each client that has a file vault view attached to the renamed server In a replicated environment, ONLY update the server that was renamed.Ĥ. Only update the ArchiveServerName, for each of these tables. Open the SQL Management Studio, Expand the Tables folder, for your vault and edit the tables ArchiveServers and SystemInfo using the RMB, then edit top 200 rows Once the server is renamed, we need to update the tables in SQL. If you right click on the vault in the admin tool and go to properties you can select ‘block logins’Ģ: Rename the server (there are a number of ways this can be done, including via the ‘my computer’ area among others).ģ. Next you need to ensure that during the rename operation no one can access the PDM vault. Please contact us in this case.įirstly ensure you have a recent backup of the archive and the SQL database. Note, if the machine also hosts the SQL Server there is a separate process to follow. This is also detailed in the KB at the Solidworks customer Portal. Remove the read-only status from each captured master part, assembly or drawing experiencing this issue.If you want to rename SOLIDWORKS PDM Archive Server, follow the steps detailed below.

Ensure the settings (in particular the External References) in the topic Info: SOLIDWORKS System Options have been applied on the machine experiencing the error.SOLIDWORKS System Options are preventing the file from being saved.Ensure the existing files are overwritten.In the Save As dialog, opt to Include all Referenced Components.Open each captured master part, assembly or drawing (experiencing this issue) in SOLIDWORKS and choose File > Save As.Sometimes the meta-data within a SOLIDWORKS file can become corrupt. Corrupt SOLIDWORKS document (part, assembly or drawing) files or out of date internal references.This message could be displayed in a Model Generation report or the DriveWorks Autopilot log. SOLIDWORKS reported that the document could not be saved due to the following problem codeswGenericSaveError, swReadOnlySaveError If a module or component that SOLIDWORKS relies on is at fault, the offending dll will be listed. Select the first Application Error in the list and read the information given in the General tab below.Įnsure the selected error does relate to SOLIDWORKS (the information will mention SOLIDWORKS.exe as the faulting application.The events will be displayed in date order (recent first). Scroll through the list of Application events until any Errors are displayed.

#Solidworks pdm could not connect to the archive server windows

Select Application from the Windows Logs section.

Click the Event Viewer App in the search results to launch.

Type Event Viewer in the Windows Search bar.

If ucrtbase.dll is listed as a faulting module:Īttempt a repair or reinstall of the Microsoft Visual C++ installations using Windows Add or remove programs app.

Check the Event Viewer for more detail on the error.

However, for faulty modules or components (that SOLIDWORKS relies on):

As a last resort, a repair of the SOLIDWORKS installation should fix any errors directly attributed to SOLIDWORKS.

Faulty installs of SOLIDWORKS or some of the required components.

Monitor the performance and if the error persists, half this value again. When a Specification results in a large amount of models being generated, start with a number of models that represents approximately half the models that will be generated.įor example if the total number of parts, assemblies and drawings generated per specification is 45, set the value to be 22.