Support for ACT 5.5 with the ACT Connector

Support for ACT 5.5 with the ACT Connector

  • Comments 9
  • Likes

TipMicrosoft released a new version of ACT, version 5.5. This version changed the database schema which prevents configuring the ACT database from the ACT Connector administrator console. If you upgrade an existing ACT installation to 5.5 which has already been configured in the ACT connector, no additional steps are required.

Using this documented workaround ACT 5.5 is supported by Microsoft with the System Center Configuration Manager 2007 ACT Connector.

Symptoms

You will see the following error when attempting to configure your ACT database:

Cannot connect to SERVERNAME.

[-2146232060] Invalid object name ‘ACT_Databases’.

An update will not be released to fix this issue at this time, but the following workaround is available:

Workaround

The following script can be used to configure ACT connector to work with ACT 5.5 install.

Syntax

ActConfig.vbs [Server] [Site code] [ACT Server] [ACT database] {Machine Account}

  • [Server] – Name of server where the SMS provider is installed
  • [Site Code] – Three letter side code of ConfigMgr server where ACT Connector is installed
  • [ACT Server] – Name of SQL server where ACT is installed
  • [ACT Database] – Name of ACT database on SQL server (set during ACT install)
  • {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 (domain\machinaccount$) where the machine account name is the ConfigMgr server where the ACT Connector is installed.

ActConfig.vbs

Server = Wscript.Arguments.Item(0)
SiteCode = Wscript.Arguments.Item(1)
ActServer = Wscript.Arguments.Item(2)
ActDatabase = Wscript.Arguments.Item(3)

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

'domain\smsserver$
If LCase(Server) = LCase(ActServer) Then
MachineAcct = ""
Else
MachineAcct = Wscript.Arguments.Item(4)
End If
For Each wbemObject In wbemObjectSet
wbemObject.Server = ActServer
wbemObject.Database = ActDatabase
wbemObject.Put_
If MachineAcct = "" Then
wbemObject.AddLinkedServer ActServer, ActDatabase
Else
wbemObject.AddLinkedServer ActServer, ActDatabase, MachineAcct
End If
Next

Levi Stevens | Program Manager

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Oops...

    I'm not sure but I think you've made a typo somewhere in the script.

    MachienAcct = "" -> MachineAcct = ""

  • 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.

  • Sorry, that was a typo but it should be fixed now.  Sorry for the trouble.

  • I just wanted to get one thing updated here. The server where we run this script (and the one that we specify in this command) needs to be the one where we have the SMS Provider installed and not necessarily the one where we have the ACT connector installed.

  • I have Installed ACT 5.6 on a server. Created a Collection Package.  Deployed the package.  Clients are successfully updating the ACT Server database.  SCCM 2007 R3 is installed on another server.  Installed the Act Connector on SCCM Server.  Used the script to configure the ACT server on the SCCM server but I am unable to see any information in SCCM when i click on Application Compatibility Toolkit Connector.  

    Am I doing something wrong?

    Any ideas on what I might have done wrong.  Your help is greatly appreciated.

    Thanks

  • Does this script need to be ran from the SCCM server or from the ACT Server? I have a connection to ACT from ConfigMgr, but when I connect to the DB, it says certain DB Fields are not found. I heard that your supposed to run this script on a fresh DB, i've blown away the DB and just created a blank DB nothing happens. Have ACT create the DB from scratch try to run update nothing changes. What am i doing wrong? ANY HELP would be great.

  • @Soren:   verified SCCM server is Local Admin on ACT box.  Still getting "unspecified error".  Help?

  • This needs to be corrected if my experience is not wrong.

    {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 (domain\machinaccount$) where the machine account name is the ConfigMgr server where the ACT Connector is installed.

    It should be

    {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 (domain\machinaccount$) where the machine account name is the ACT provider is installed ...

    with giving the name in the ConfigMgr server where the ACT Connector is installed never worked for me.

  • I am having a different issues with the configuration of the ACT Connector.

    I get the message “The ConfigMgr Provider reported an error” on the Application Compatibility Toolkit Server entry under the Application Compatibility Toolkit Connector node on the my SCCM Console. When I try to Configure the ACT Server the text windows for the server name and database name are greyed out.

    If I run the script provided in this note I get an error 0x80041013 on line 35 where the objects are enumerated in WMI. My examination of the SMS_ActConfig instance does not show any objects.

    Please make a suggestion on where I should look next to resolve this issue.