You see error -2146232060 when attempting to configure your ACT database using the following steps:

  1. In the Configuration Manager console, navigate to
    System Center Configuration Manager / Site Database / Computer Management / Application Compatibility Toolkit Connector/ Application Compatibility Toolkit Server
  2. To open the properties of the ACT server right-click the ACT server in the results pane and select Properties. Alternatively you can select Configure ACT Server in the Actions pane or click the Actions menu and select Configure ACT Server.
  3. To specify the Microsoft SQL server that contains the ACT database type the name of the server and click the Connect button. Alternatively, you can click the drop down and select Browse for more to open the Select Server dialog box. Select the server you want to use and click OK.
  4. Specify the ACT Database to connect to using the drop down and selecting the database.
  5. To close the ACT Configuration properties dialog box, click OK.

configure act server properties

configure act server properties

At this point you receive the following error:

Check Connection

Cannot connect to COMPUTERNAME.

[-2146232060] Windows NT user or group ‘DOMAIN COMPUTERNAME$’ not found. Check the name again.

‘DOMAIN COMPUTERNAME $’ is not a valid login or you do not have permission.

check connection -2146232060

check connection -2146232060

Microsoft will not be releasing a fix but the following modified script can be used to configure ACT connector to work with ACT 5.5 install, just change XXXX in the script as per the comments.

Server = "XXXXXX"    '<- Name of ConfigMgr server where ACT Connector is installed
SiteCode = "XXX"    '<- Three letter side code of ConfigMgr server where ACT Connector is installed
ActServer = "XXXXXX"    '<- Name of SQL server where ACT is installed
ActDatabase = "XXXX"    '<- Name of ACT database on SQL server (set during ACT install)
MachineAcct = ""    '<- Machine Account (Optional parameter)!  If the ACT is installed on different
'   server than the ACT Connector, then provide the machine account name the ACTC
'    provider runs under (domainmachineaccount$) where the machine account name is
'    the ConfigMgr server where the ACT Connector is installed.

Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\" & Server & "rootsmssite_" & SiteCode)
Set wbemObjectSet = objWMIService.InstancesOf("SMS_ActConfig")

If LCase(Server) = LCase(ActServer) Then
MachineAcct = ""
End If

For Each wbemObject In wbemObjectSet
wbemObject.Server = ActServer
wbemObject.Database = ActDatabase
If MachineAcct = "" Then
wbemObject.AddLinkedServer ActServer, ActDatabase
wbemObject.AddLinkedServer ActServer, ActDatabase, MachineAcct
End If

If Err.Number = 0 Then
msgbox "Success"
msgbox "Failure " & Err.Number
End If

The original script can be found here Support for ACT 5.5 with the ACT Connector


Soren Hermansen · May 26, 2010 at 5:48 pm

Excellent info.

The script gave me an ‘unspecified error’ in the .addlinkedserver line until I added the SCCM-server’s machine account to the local administrators on the ACT Server. Now it is running.

Tone · May 26, 2010 at 8:47 pm

Glad you got it working – did you try the optional parameter?

Soren Hermansen · May 27, 2010 at 9:23 am

Yes, we have ACT on a different server so I had to use the optional parameter.

Thanks again.

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *