Software Deployment

Hi daher,

Uninstall with verbose logging as that should tell you where in the code it fails.

Daher, you have installed your application and usually it creates a copy fo your installer under C:\Windows\Installer and uses fro repair amd uninstallation if REINSTALLMODE property si not being used by your MSI. When you do some changes to your local MSI and start a uninstallation it stills refers to C:\windows\installer.
For time being, you can go and delete your backed up MSi from C:\Windows\Installer and start uninstallation form your local copy. To avoid such kind of issue permantely use REINSTALLMODE Property which will help the installer to always look at your local copy.

Jeeoo!
Santro

Santro, you're on the wrong track there, I'm afraid. You're thinking of the error where the WI engine cannot access the original source media.

daher, Kim (AngelD) is almost right. You need to log the install to see which script is missing but note that WI logging doesn't show code execution. Indeed, it will only show you the first few lines of the code itself. All scripts should include the writing of progress and/or error messages to the MSI log, using the Session.Message method People rarely do, though, because they make the fatal mistake of assumption, i.e. they assume a script will always execute perfectly and they fail to program defensively. I do the reverse: I assume that EVERY STEP of the script will fail and code accordingly.

I had already faced this kind of issue and tested and solved it in that way. If we are installing msi locally it creates the copy and uses it for uninstallation even if we dont have the local copy.

NOTE - I have just given an option to try.

Cheers!
Santro

ORIGINAL: zipsantro
If we are installing msi locally it creates the copy and uses it for uninstallation even if we dont have the local copy. It does indeed but if the script is missing from the original - which is the case here - it will still be missing from the copy. Unless you know some means that an MSI can acquire missing components whilst being copied by the engine, of course :)

My purpose in pointing that out was to avoid the OP chasing red herrings, nothing else.There's no point in trying it out because, simply put, it won't work in this case.

Thanks for your replies,

Well I tried what Santro said. But i am still stuck with the same error.


VBScab: i deleted the script from my MSI and it still pointing to an error in my MSI mainly in the action holding the script that i deleted.

I agree with you that scripts can have a lot of errors and i knew where is the error ... but the problem is that i deleted the whole vbscript and in log it points that there is an error in the vbscript which i deleted.

Well i am still stuck but i can not attach my log file (no sufficient permission)
Thanks for your replies again.

For the time being i solved the problem as follows.

Under software list i repaired the installed software then uninstalled it.

Well one should be careful with the scripts.

Thanks again for the support

ORIGINAL: daher
Well one should be careful with the scripts. ...and have decent (or any!) source control software and/or some back-up software.