Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

RS 7.1 Complete Removal

Created: 08 Mar 2013 | 1 comment
MonitorMan's picture

For those who have used RS 7.1 and then uninstalled the solution, there are still components left behind that break other components. For instance, the task of running SQL on the SMP or if you have AMS and attempt to edit computer assets cause the page loading to fail. The error within the SMP logs appear to call RS assembles that are no longer available. Obviously the removal of the solution is not clean.

Description: Exception encountered: Altiris.NS.Exceptions.AeXException: An unexpected exception has occured during CreateInstance. (Assembely:Altiris.RecoverySolution, Version=7.1.0.0, Culture=neutral, PublicKeyToken=d516cb311cfb6e4f Type:Altiris.RecoverySolution.RS_ResourceDataClass) ---> System.IO.FileNotFoundException: Could not load file or assembly 'Altiris.RecoverySolution, Version=7.1.0.0, Culture=neutral, PublicKeyToken=d516cb311cfb6e4f' or one of its dependencies. The system cannot find the file specified.
File name: 'Altiris.RecoverySolution, Version=7.1.0.0, Culture=neutral, PublicKeyToken=d516cb311cfb6e4f'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity

Calls to support are futile as all we get are the solution was EOL and these were known issues.

Has anyone been ever provided the SQL or another means to fully pull out these no longer existing RS dependencies?

Ugh.

Thanks
 

Operating Systems:

Comments 1 CommentJump to latest comment

Lery's picture

I might be able to help you, but it will not be pretty.  Altiris solutions have always uninstalled ugly.  First you can try running:

--Begin SQL Query

select * from class where type like '%Recovery%'  

--End SQL Query

If you could post back the results of that select statement, it would be nice to see.

Regardless of the results, your next step is the risky one.  Therefore, you best backup your database first.  Then you can run something like this:

--Start SQL Query Code

delete from ClassBaseClass

where baseclassguid in

(select guid from class where type like '%Recovery%')

or ClassGuid in

(select guid from class where type like '%Recovery%')

delete from class

where type like '%Recovery%'

--End SQL Query Code

Best of luck to you!