Share via

ConfigMgr 2007: Error [-2146232060] Invalid object name ‘ACT Databases’ when connecting to SQL server in Configure ACT Server properties

  • Article

Here's another issue that a couple folks seem to be running into every now and then.  Thanks go to Clifton Hughes, a Senior Support Engineer in our Las Colinas office for writing this one up.

========

Issue: In the Configuration Manager admin console under the Application Compatibility Toolkit Connector container, Application Compatibility Toolkit Server, when you select Configure ACT Server, enter the SQL Server name and click connect you may receive the following error:

Check Connection
Cannot connect to <Servername>
[-2146232060] Invalid object name ‘ACT Databases’.

SMSPROV.LOG may also show the following error:

\r\nSystem.Management.ManagementException\r\nInvalid class \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

Cause: This error can occur if the ACT50 SQL database has not yet been created.

Resolution: To resolve this simply be sure to create your ACT50 database.  To create the ACT50 SQL database, run the ACT Configuration Wizard in the Application Compatibility Manager on the machine where you installed the Application Compatibility Toolkit, or run CreateDB.sql on the SQL server.  This file is included with the Application Compatibility Toolkit and is located in the All Users profile folder under \Application Compatibility Toolkit 5\CreateDB.sql.  Note that this path varies depending on the operating system upon which the Toolkit is installed.

For more information see the ACT5 Deployment Guide.  The ACT5 Deployment Guide is available for download along with the Application Compatibility Toolkit 5.0 itself at https://www.microsoft.com/downloads/details.aspx?FamilyId=24DA89E9-B581-47B0-B45E-492DD6DA2971&displaylang=en.

========

Thanks Clifton!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments

  • Anonymous
    January 01, 2003
    thank you
  • Anonymous
    January 01, 2003
    We are still having a problem with this error even after we created the database and populated it with inventory. Any idea's where to look next to solve this?