Skip to content
logo Knowledgebase

Sage 200 Extra - Changing the Sage 200 server name

Created on  | Last modified on 


It is sometimes necessary to change the name of the server where Sage 200 Extra is installed.


NOTE: This article applies to Sage 200 Extra 2011 and below only. It is not possible to use Sage 200 Extra 2013 and above on a server when the server name has been changed without uninstalling and reinstalling the software.

This can be required if the customer's IT department are upgrading servers or decide to standardise their naming conventions.

This guide explains how such changes impact on the Sage 200 Extra installation and how to resolve any issues that may be encountered.


Several references to the server name exist throughout various files on the Sage 200 Application Server. Changing the name of the server does not automatically update such files and therefore the referred name contained within them becomes invalid. After changing the name and trying to launch the Sage 200 Client, you will receive the error message 'Exception has been thrown by the target of an invocation'. This is usually followed by another message advising that the 'directory specified for Logon path does not exist'.


  1. The logon path is specified in the SVN4WIN.ini file which is located in the installation directory of the Sage 200 Client. By default, this would be C:\Program Files (x86)\Sage\Sage200.

    Open the file and amend the path to the Logon directory, referred to as 'SVNDIR=', so it now reflects the updated new of the Sage 200 Server. Save the file.


  2. When attempting to open the Sage 200 Client again, you will now be able to enter your login credentials but then receive an error message stating 'Logon failed due to unexpected error'. Note that the error message refers to being unable to resolve the remote name, which still shows as the old server name.


  3. This message is the system reporting an issue locating the web services referred to in the SAAServiceSetting.xml file. Open the file within Notepad - the file is held in the C:\Sage\Logon folder.
  4. Change the URL to the path of the new server name. You should not need to amend any other part of the URL, including the secure prefix https, port number or service name.


  5. Save the file and re-open the Sage 200 Client. A similar error to the previous screen will show - this time referring to being unable to 'establish trust relationship for the SSL/TLS secure channel'. This indicates a problem with the SSL certificate.


  6. When the Sage 200 Application Server is installed, a certificate is created and issued to the server to which it is being installed. As the server name was different at the time of install and we've now changed the server name, the certificate is no longer valid as it was effectively issued to a different server.


    The only options available here are to recreate the SSL certificate or rename the server to match that of the SSL certificate. In this case, we would need to recreate the certificate...

  7. Check the certificate being used by Sage 200 in IIS. Go to Start > Run > type 'inetmgr' > OK. Expand the list of sites in the tree view panel on the left and select Sage 200 App Services. From the Actions panel on the right, choose Bindings > select type 'https' > Edit. The name of the certificate in use shows in the 'SSL Certificate:' box. Click Cancel.

    Do not press OK as this may invalidate the entire web site in IIS.

  8. Select https > Remove > Yes.

    Note: If you have other services installed that use SSL, such as Sage 200 Remote Authorisation and Sage 200 Self Service, these certificates should also be removed as they were issued to the old server name as well.

  9. Insert the Sage 200 installation disc. If the setup program does not run automatically, browse to setup.exe on the root of the disc via Windows Explorer or My Computer. Select Next > Change > untick Sage 200 Application Services > Next > Next > Finish.
  10. Restart the installer. Select Next > Change > tick Sage 200 Application Services > Next > Next > Next > Next > Next > Change.
  11. Return to IIS and check the Server Certificates. You should now see a new certificate which has been issued to the server under it's new name.
  12. Open System Administrator. An error will appear stating it could not connect to the server. 


    This is because System Administrator is still trying to connect to the old server. Select OK. Right click on the instance name in the top left of the window and select 'Connect to Another Server'.

  13. Amend the first part of the URL after the https:// prefix, changing the name of the old server to that of the new server. Leave the rest of the path unchanged and select OK.
  14. Enter your login details and update the properties of each company in the Companies list. You must ensure you have the correct path for the Attachments, Spool and Server details. Use the Test button to confirm the details are correct before saving.

You should now be able to access Sage 200 on the server.


Benefits for your employees above and beyond their payslips

We want to help your business where we can. That's why we are offering Sage Employee Benefits free to Sage customers for the first three months.

Leave your details and we'll call you back