Sometimes, after you move the Plastic SCM server from one machine to a new one, you will find that some of the xlinks you were using are not accessible anymore; it's because they keep targeting the old server IP/name.
That scenario usually happens because the xlinks were created by not using the "relative" option (which is the default one BTW). If you want to know when to use relative xlinks and the differences with absolute xlinks, please see our guide: https://www.plasticscm.com/documentation/xlinks/plastic-scm-version-control-xlinks-guide.shtml#Chapter5:RelativeXlinks
How can I access the unreachable xlinks content?
You need to let the Plastic SCM client know that all the network requests using the old server name/IP are no longer valid and you want to redirect them to a new address. This can be easily done using the 'serveralias.conf' file. The 'serveralias.conf" file format is pretty simple:
Notice that you can configure this once at the global configuration area and apply the same configuration for all the clients. This will save a lot of time. Click this link for more information: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide.shtml#Globalfileconfiguration
How can you prevent the problem?
There are two main ways to prevent this issue from happening:
- Always use a well known network name for the Plastic SCM server machine. If the name stays the same during hardware changes, the Plastic SCM client will not be aware of the changes.
- If the xlink is targeting a local repository, it doesn't make sense to use an absolute xlink; use a relative one instead.