Description: Failed to process manifest file http://www.solutionsam.com/imports/6_2/patch/microsoft/PMImport_InvariantLanguage.cab -> Invalid object name 'TempCSDetails'.
Altiris requires that it's AppID or Database Credentials default to the "DBO" schema of its own database by owning the database. Many confuse the idea of owning the database with the “db_owner” role which is assigned to database users. Ownership of all SA level logins are by virtue of being an SA, able to login to all databases as the user(schema) “DBO”. Additionally the owner of the database also logs into the database it owns as “DBO”. A SQL login can own a database even if they have no other rights outside of that database on the SQL server. In SQL 2000 only the owner of the database and all all SA level SQL logins use the “DBO” schema as needed by Altiris. In SQL 2005 a user can be switched to default to a different schema without having to be either the owner of the database or a SA level SQL login.
select user” which will return the database user that is logged in. With SQL 2000 if it does not return "dbo" then the SQL login does not explicitly use the "DBO" schema.
select name,type from sysobjects where uid>4
To fix one object, run the following command putting in the objects schema name and object name separated by a ".".
sp_changeobjectowner 'Schema Name.Object Name',
SQL 2005 / 2008:
Alter Schema dbo Transfer 'Schema Name.Object Name
Alter Schema dbo Transfer <user>.spCreateKeyIndex If the "DBO" schema already has an object by that name, then this procedure will fail; in which one of the versions will have to be deleted. Generally the one created last should be kept and changed to be owned by "DBO".
To prevent other objects from getting created under the wrong schema, the SQL login account used by Altiris needs to be switched to default to the "DBO" schema
For SQL 2000
sp_changedbowner 'SQL login Name used by Altiris'
For SQL 2005
For SQL 2014