Home » Groups » Asset & CMDB

What is the preferred method for upgrading to Asset Control 6.2?

What is the preferred method for upgrading to Asset Control 6.2?
Filed under: Asset Control Solution Best Practices
Admin's picture
Submitted by Admin on 29 June, 2006 - 11:16

Q:
What precautions/best practices should be followed when upgrading from Asset and Contract 6.1 to version 6.2 via the Solution Center?

A:
To ensure that all prerequisites for Asset 6.2 will also be installed, go to the Configuration tab > Upgrade/Install additional solutions > AZ Solutions > click on Asset Control and Contract Management install.

This will make sure that all prerequisites for Asset Control 6.2 will be properly installed.

4
Average: 4 (6 votes)

Caution

gebhartj's picture
Submitted by gebhartj on 29 June, 2006 - 12:11.

From my testing, I found a bit of an issue that you should watch out for.

If you are using a SQL Server account for your database connection, there's a good chance the Asset 6.2 will undergo a "stealth failure".

The install will report successful, but none of the objects will show up.

The solution that I found, with Altiris support, was to ensure that the Application Identity was the account accessing the database.

Resolution to possible Asset Control 6.2 upgrade failure

Greg Giles's picture
Submitted by Greg Giles on 29 June, 2006 - 14:58.

Good comment gebhartj. Altiris support confirmed that in environments where the application identity is not the DBO of the database or the application identity does not have system administrator privileges the upgrade will fail. Running the upgrade under a user context without sufficient rights will cause the inv_asset_tag backup table to remain, and disallow the proper view from being created (a view cannot have the same name as a table). This issue will cause the installation to rollback and undo all database changes previously made during the upgrade.

To correct this issue, the application identity must be the DBO of the database or have system administrator rights. Under the DBO or system administrator context, the backup table will be removed correctly and remediate the duplicate naming issue which causes the upgrade to fail.

Thanks, Greg

gebhartj's picture
Submitted by gebhartj on 13 July, 2006 - 15:15.

Yep. We were using a SQL account for the Altiris SQL login, not the AppIdentity via passthrough authentication.