I am working on the uninstall package for office 2007 system. My goal is to make the uninstallation automatically, so I used the below method (take access for example)

"%COMMFILES%\Microsoft Shared\OFFICE12\Office Setup Controller\setup.exe" /config %SOURCE_DIR%\config.xml /uninstall ACCESS /dll OSETUP.DLL

The contents in the config.xml is as below

<Configuration Product="StdPlus">
<Display Level="None" />
<Setting Id="SETUP_REBOOT" Value="Never" />

This method works most of time, however, it fails some time with exit code 30054, then I tried to uninstall it manually, I got below picture

Choose a language in which to run setup


Then when one language is selected, the button OK is enabled, click OK, the uninstall proceeded.

I knew this screen should cause the failure, but I don't know how to bypass it!

Please help me on this!!!

Thanks a million
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Have you tried to use below - Like it works while installation,
<AddLanguage Id="en-us" ShellTransform="Yes" />
May be, you need to find similar Language Id for Deutsch.
Answered 12/30/2010 by: WiseAppPackager
Purple Belt

Please log in to comment
I haven't spent a great deal of time with Office 2007/2010 so I;m happy to be corrected but I don't think what you have there is right. Apart from anything, the 'ProductName' specified on your command line is erroneous but, if used, has to match the one used in the XML file.

What I believe you need to do is use the Office Customisation Tool (OCT) to create a new MSP which has Access set to 'Not Available'. IIRC, there is a shortcut to creating that, in that you can import the original MSP into the OCT, make your change, then save as a new MSP. You can then refer to that new MSP on the command line using the '/adminfile' argument. See what you make of this TechNet article. Although it's about Office 2010, much of it applies to 2007.
Answered 12/30/2010 by: VBScab
Red Belt

Please log in to comment