Video Screencast Help

Wise 6.0 - Remove CA

Created: 20 Aug 2012 • Updated: 29 Aug 2012 | 14 comments
This issue has been solved. See solution.

Hi,

In WSI i have CA that i deleted completely. when i run MSI on the upgrade from prevouis version,

the Removed CA appears as part of installation. I checked the CA table and the Removed CA does not exist,But i do not know from where

this CA appears during the installation, i can see it in the log too  . any idea how to prevent the unwanted CA from reappreaing.

A quick prompt highly appreciatd as i am in the middle of HEAT!!

BTW - it is a Major Upgrade.

Comments 14 CommentsJump to latest comment

piyushnasa's picture

Is it happening only on upgrade? If yes, then is it coming from the uninstall of previous application?

You need to see the log and see where this CA is occuring.

Put the condition as 0 rather than deleting it in InstallExecuteSequence and InstallUISequence tables. It might have an entry in Control table from where it runs CA. Remove it from there as well.

 

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

NetRock's picture

Thanks for the reply.

yes only during Upgrade happing. But what do you mean by condition as 0. Could please direct me to the right direction. Also, in the Control table i do not see any signs of any CA. How do i know which entry is for CA.

Thanks for your kind help.

piyushnasa's picture

Maybe this custom action is running at the time of uninstall of previous MSI. If that is the case the I am afraid, there is no way to go ahead and this will come for sure.

If it is happening only from this MSI, then I was saying that put the condition of the CA as 0 in InstallExecuteSequence and InstallUISequence tables.

There is a Condition column in these tables. Put the condition as 0. This will disable the custom action.

 

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

SOLUTION
piyushnasa's picture

One more thing: If this issue is not coming at uninstall of previous application when you uninstall it manually, then write a script to uninstall the previous application first and install this application then.

I know it is not an ideal solution but I cannot suggest anything else without actually looking at logs or actual package.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

EdT's picture

An upgrade runs an uninstall of the "old" package using the locally cached MSI already on the system. If you want to disable a CA in the old MSI, then you need to add some code to either replace the locally cached MSI with a modified version, or actually edit the locally cached MSI to disable the custom action.

 

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

piyushnasa's picture

Is this really a practical solution to deploy? I know this can be done, but never done.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

EdT's picture

Anything that solves a problem is a practical solution. It has been done in the past.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

JohanH's picture

Do a custom action after Installvalidate. Check for Not Installed AND <Actionproperty from Upgrade table>. I have used vbscript for this custom action. You have to know the ProductCode of the installed package.You get the path to the cached MSI with installer.ProductInfo(ProductCode, "LocalPackage"). Then you can open the cached database and edit the tables directly using SQL queries with vbscript (OpenDatabase, OpenView etc.)

EdT's picture

...as I said earlier, it is a practical solution.;-))

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

NetRock's picture

Thank you Guys for your input.

What i did is to remove a file needed for CA to run, Since CA could not find the file, was not able to execute. I am waiting a news from Validation.

Nice to hear from you Edt.

EdT's picture

As long as the CA failing does not cause a fatal error which leads to the upgrade rolling back.....

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

VBScab's picture

>I am waiting a news from Validation
Frankly, if I was validating the package, I'd fail it.

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.

NetRock's picture

Thank you everyone for your help. but the post from piyushnasa helped me to solve the issue. The CA was still in InstallExecuteSequence table, even after i deleted the CA.That is why removing the file helped.

Thank you again for all your help.

And VBScab, "Frankly", i send all my LOVE to you....! 

Peace.   

piyushnasa's picture

I am glad that your issue is solved. :)

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/