Service connection tool in offline mode fails to prepare the usage cab if the site database runs on a named instance with a custom port

Applies to: System Center Configuration Manager (current branch)


Consider the following scenario:

  • You use Microsoft System Center Configuration Manager current branch in your environment.
  • You use a named instance of Microsoft SQL Server for the site database of the central administration site or the stand-alone primary site.
  • The named instance of SQL Server uses a custom port. 

In this scenario, when you use the service connection tool to put your usage data into a .cab file, the following error message is logged in the ServiceConnectionTool.log file:


This issue occurs because the service connection tool still tries to connect to the default port (1433).


To fix the issue, follow these steps before you use the service connection tool:

  1. On the computer that hosts the service connection point, open Registry Editor, and then locate the following registry subkey:

  2. Right-click SQL Server Name, and then click Modify.
  3. Add ,<port number> to Value data, and then click OK. For example, if the SQL server name is and the port number is 1367, the new value data becomes,1367.
  4. Close Registry Editor.

After you complete the connect and import steps, restore the value data of SQL Server Name under registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_DMP_UPLOADER to the original value.