I want to uninstall an older version of the application with the new version. i am using a vb script as a CA to uninstall the older app. I am not able to place the CA properly so it is not working. Can anyone tell me the exact way to place the VB script in the custom action ( in script options etc)

I have tried upgrade but that is not working.

thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Could you please post the details of the problems you are facing?
as in are you getting an error while running the CA or is it not running at all?

also what is the issue you are facing while using upgrade table?
u can have a look on this link http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning6390&mpage=1&key=&#46390
Answered 08/20/2009 by: karshi
Purple Belt

Please log in to comment
0
i am using a vb script as a CA to uninstall the older app

why all this hassle when you can use the upgrade table which is very easy to use

using the msiexec /x {productcode} will only work in the UI sequence and not work if you try to uninstall silently using a type 34 CA

these are the options that you have in my option anyway

are you using wise or IS
Answered 08/20/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Both responses assume that the older version was installed with Windows Installer which may not necessarily be the case. Perhaps the OP is trying to run a legacy uninstaller.

Having said that, a script is probably the wrong choice. Either run a Custom Action to run the uninstaller EXE or, if there's no uninstaller, or if - as is often the case - the installation record file is missing or overwritten, you can use the RemoveFile and RemoveRegistry tables to delete the application. After all, at the end of the day, that's all an installation is - a collection of files and/or registry entries.
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
Karshi,

On the users systems, stata 8 and 9 is already installed. I am trying to upgrade to Stata 10 thru my package. When i tried the upgrade code of the older version (8,9), Stata 8 is getting uninstalled from the system and after that it throws an error like Internal error 27xx : INSTALLDIR. and Stata 9 is not getting uninstalled. So i thought that i will use a vb script as a CA to uninstall the stata 9. I am not able to place the script at the right place so it is not getting execute.

this is what i am facing.

thnxx
Answered 08/20/2009 by: dnmech
Senior Purple Belt

Please log in to comment
0
Why do people imagine that, if an uninstall via the proper mechanism fails, then trying the same thing via a different route will somehow magically make it work?

What is the actual error you get at the stage where v9 is trying to uninstall?

Also, where in the sequence is the RemoveExistingProducts action?
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
you might need to read this to get a better understanding of upgrades

https://kb.altiris.com/

and type in 1088
Answered 08/20/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
vbscab,

i am neither trying any improper route nor any magic. its just a different way to get it work.

i told earlier that i got error like Internal Error 27xx : INSTALLDIR . i am not able to recall the exact error code.

"Also, where in the sequence is the RemoveExistingProducts action?" - where can i find out this information??

tanxx
Answered 08/20/2009 by: dnmech
Senior Purple Belt

Please log in to comment
0
"Also, where in the sequence is the RemoveExistingProducts action?" - where can i find out this information??

you have the answers on the link I sent you

attention to detail is the key in application packaging
Answered 08/20/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
i am not able to recall the exact error code. If you want help, you might find that providing as much information as possible helps. Clairvoyance isn't a skill most packagers have.
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
- There's no "mastery" in supplying information.
- By "silly things" you must mean silly things like a total inability to use search engines? Or asking a question which has already been answered in a different thread THAT DAY?
- Post a link to any thread containing an arrogant stance.
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
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.


Read that before you post here...hahaha....another "silly things" is the inability to read your Signature that says the above....
Answered 08/20/2009 by: PackageExpert
Blue Belt

Please log in to comment
0
Anyway if I recall, if your package is Windows Installer based, use the Upgrade Table to include the Product Code,Version Minor Version Major etc.

I think the RemoveExistingProducts actions should be in between InstallValidate and InstallInitialize action which you can change from InstallExecute table.... You can google more for "Upgrading a Windows Installer Package" or any related search quotes...tonnes of info there....

and for the non-MSI installer follow what vbscab suggested.

Good Luck
Answered 08/20/2009 by: PackageExpert
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity