Hello all,

I'm currently trying to uninstall an application that I'm intending to upgrade. I have a command file that goes like this:

Start /WAIT /HIGH msiexec.exe /X {8492EBE8-FB8D-4209-A162-94751C1D14A5} /Li C:\LOGS\SAPGUI6.4.3_Uninstall.log /Q

Start /WAIT /HIGH msiexec.exe /I C:\Apps\SAPGUI\SAPGUI_710.msi /Li C:\LOGS\SAPGUI_7.10_Install.log /Q ALLUSERS=1

The initial uninstall runs from the CCM\cache folder but the uninstall hangs after InstallFinalize with a couple of MSI INFO messages regarding 2 DLLs failing to unregister. The MSI errors appear in the log when it's run locally but crucially it doesn't hang and it uninstalls without error. When it's run from SMS, (and by the way it doesn't happen on all machines - I've had the SMS job complete successfully for at least 4 machines) it tends to hang.

Any ideas people? TIA.

0 Comments   [ + ] Show 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.



Does SAPGUI 7.10 have a populated upgrade table for 6.4.3?
If so then the act of installing 7.10 will upgrade for you.

You could also use an MST to populate the upgrade table, so that it does perform the required upgrade.
The ALLUSERS property can be added to the MST, as well as the standard ROOTDRIVE and REBOOT properties which you don't appear to have considered.

I've never had much joy with giving SMS a script to run, like the one you've posted - it tends to provide erratic results.

I always add the MSI to SMS using the "New Package from Definition" option and customise the command line as required.
The bonus is that SMS adds the MIF information and relies on that to acuarately report the status of the deployment.

Hope this points you in the right direction.

Let me know how you get on,

Answered 06/06/2008 by: dunnpy
Red Belt

Please log in to comment
Hi Dunnpy, thanks for your reply.

I'm an MSI packager by trade, and this SMS stuff has been pushed on me - not that I'm complaining - I'm enjoying the challenge. To answer your question, I can't use the upgrade tables to upgrade this even though I tried because the component GUIDs are all out of Sync and it would mean a ridiculous amount of work. I'm using the MSIEXEC /x command at the moment and generally speaking it works, always when executed locally. Occasionally it hangs when being run via SMS which is frustrating because I don't know the reason why.

As regards the properties, I'm aware of this functionality, and the MSI has been pre-populated in any case so thanks.

I just think I've been lumbered with trying to remove a problem MSI that was poorly packaged initially. In which case, how do you remove something that's broken? Nightmare scenario given it's on 3,500 machines!
Answered 06/09/2008 by: dm1
Blue Belt

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