Safeguard 8.20 Migration

Question

We have recently upgrade our safeguard server to 8.20, and now looking to migrate it. We have fresh install on 8.20 on new server, restored our databases and added the permissions etc for the new server. But when browsing the web service, we select Invoke Test and get the following result

<?xml version="1.0" encoding="UTF-8"?>
<string xmlns="">tempuri.org/.../WebService> <DBAuth>failed</DBAuth> <Error>A database exception occurred.</Error></string>

Struggling to find out where the issue lies, any advice will be greatly appreciated.

This thread was automatically locked due to age.

GlennSen · Answer

Hi Alan, 
 Good Day! 
 
 Follow the steps below to re-register the SafeGuard Enterprise Server and update it with a new Server configuration package: 
 
 Open the SafeGuard Management Center and authenticate with a Master Security Officer 
 Select Tools > Options > Database and make sure the configuration is correct 
 Click OK to close the options 
 Select Tools > Configuration Package Tool 
 On the 'Servers' tab, select the entry for %SGN_SERVER_NAME% and click on 'Remove' 
 Click Close to confirm the changes to the Database 
 Select Tools > Configuration Package Tool 
 On the 'Servers' tab, select 'Add...' 
 Browse to the SafeGuard Servers Certificate located at C:\Program Files (x86)\Sophos\SafeGuard Enterprise\MachCert\%SGN_SERVER_NAME%.cer
 
 Note : Do not use any cached / backed up certificates or any certificates used to establish SSL security between clients and the IIS!

Do not change the server name 
 Click OK and click 'Close' on the 'Configuration Package Tool' to commit the changes to the Database 
 Select Tools > Configuration Package Tool > Server Packages tab 
 Select the entry for %SGN_SERVER_NAME% and click on ' Create configuration package ' 
 Run the msi package to launch the installer and install the new server configuration package
 
 Please note : If a server configuration package is already installed, the installation wizard will only prompt to uninstall the package. In this case, uninstall the package and complete the process. Then execute the server configuration msi again and install it.