fertaurora.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 OFFLINE#
#SOLIDWORKS PDM COULD NOT CONNECT TO THE ARCHIVE SERVER PROFESSIONAL#

Note: Due to the way PDM identifies and structures the data within the archive, it is split into 16 folders.

Adjust the size of the archive that will reside in each location.

I created a new folder on my D: drive for this purpose Note: The name of the folder may be different on your server.Īfter the dialog box appears, there are a couple of steps you now need to complete. Once open, expand the folder under This Computer select your vault then right click and choose Relocate. Right click the archive server icon and select Open. Check the system tray (by the clock) as in the image above. If, upon launch, a dialogue is not shown it is likely that the application has been minimised. To start the process, launch the Archive Server Configuration application from the start menu of the PDM server. My advice would always be to use built-in drives where possible, since network drives could be affected by bandwidth and although NAS/SAN devices could also be employed here, officially that would not be a supported configuration.Įssentially, if you have multiple drives in your server and the one holding the archive is at capacity, then this is one of the quickest methods for addressing free-space concerns that doesn’t require an entire server move, and it is easy to carry out directly within the archive server configuration tool. This can include drives that are located on the network, as well as those physically attached to the server. The distribution is done from the archive server itself and can be pointed to any directories or drives that the server has access to. Due to the way that the archive is structured, the archive file store can be split up over as many as 16 locations.

#SOLIDWORKS PDM COULD NOT CONNECT TO THE ARCHIVE SERVER OFFLINE#

In the event of a relocation, you should ensure that all users log off or go into offline mode before attempting the move.īy redistributing the archive across multiple hard drives, you can reduce the load on the primary drive. Note: Before taking any steps to relocate, remove or compress data in your archive please ensure that all files have been checked in by the users and that backups have been taken of both the database and archives.

#SOLIDWORKS PDM COULD NOT CONNECT TO THE ARCHIVE SERVER UPDATE#

What you decide to remove/keep will be down to you, but it still surprises me how often I forget to clear my own recycle bin! Choosing the option to also inspect system files can often reveal lots of old Windows update installers taking up GB’s of space on the drive which, in most situations, I would suggest you can probably do away with, now and again. Right click over your ‘full’ hard drive, select Properties then from the general tab click Disk Clean-up. The first thing to do if you run out of disk space is nothing really to do with PDM, it's simply to run the built in disk clean-up tool within Windows Explorer. When this happens there are a couple of things you can do straight away to get you up and running again, but it is probably also worth thinking about what processes and systems you have in place already to ensure you are maximising the space available to you within that setup. The warning message, led to my reviewing the archive server's log file and this quickly identified the problem being a result of the PDM Server running out of disk space.

#SOLIDWORKS PDM COULD NOT CONNECT TO THE ARCHIVE SERVER PROFESSIONAL#

This blog series was prompted by a recent support ticket, logged when a customer found their PDM Professional installation suddenly became unusable.