locked
Uninstall program problem RRS feed

  • Question

  • Colleagues,

    I try to uninstall such program as PDF Creator using SCCM 2007 R2.

    I've found following command line:

    C:\Program Files\PDFCreator\unins000.exe /silent   ( http://www.appdeploy.com/packages/detail.asp?id=1360 )

    So,

    1) I create new package PDF Creator Uninstall without data source (i didn't marked "This package contains source files). Other options by default.

    2) I didn't add any DP.

    3) I create program:

    with following command line: C:\Program Files\PDFCreator\unins000.exe /silent

    Run (general option): hidden

    Program can run (environment option): Whether or not is user logged on

    {Other options by default)

    4) I receive following error (Status Message Details - faild) on most computers (other - Accepted - No Further Status ):

    An error occurred while preparing to run the program for advertisement "33020031" ("3300003B" - "silent uninstall"). The operating system reported error -2147024894: The system cannot find the file specified. Additional program properties: Command line: C:\Program Files\PDFCreator\unins000.exe Working directory: Drive letter (? = any): Possible cause: This message most commonly occurs when the program's command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the SMS Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions. Solution: Check each of the items listed above.

     

    Which step is wrong?

     

     

    Tuesday, July 6, 2010 8:33 AM

Answers

  • Simple question... don't forget to put quotes around the command line  "C:\Program Files\PDFCreator\unins000.exe /silent"  program files has a space so it will throw an error or use
    %PROGRAMFILES%\PDFCreator\unins000.exe /silent
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Tuesday, July 6, 2010 12:16 PM
  • I run into this (by accident) all the time. If you check the ccmexec.log on the client, it will clearly show the client trying to find "C:\Program" which doesn't exist. This happens because of the space in the filename.

    Be careful with the %ProgramFiles% because of 64-bit redirection that happens: http://msdn.microsoft.com/en-us/library/aa384187(VS.85).aspx.


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Tuesday, July 6, 2010 12:34 PM

All replies

  • Hi UltraFanat,

    Personally,  i think i used a different method.
    I would have created a script file executing the command line that you quote.
    Then i would include this bat file in a package which I would run with the command line of a program.

    Best Regards


    Jean-Sébastien DUCHÊNE - www.windowstouch.fr - Microsoft Valuable Professional 2010 (MVP) ConfigMgr - Microsoft Student Partner (MSP) 2008/2010, MCITP Enterprise Desktop Support Technician 7/Enterprise Desktop Administrator 7, MCTS Configuration Manager/MDOP
    Tuesday, July 6, 2010 8:47 AM
  • Simple question... don't forget to put quotes around the command line  "C:\Program Files\PDFCreator\unins000.exe /silent"  program files has a space so it will throw an error or use
    %PROGRAMFILES%\PDFCreator\unins000.exe /silent
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Tuesday, July 6, 2010 12:16 PM
  • I run into this (by accident) all the time. If you check the ccmexec.log on the client, it will clearly show the client trying to find "C:\Program" which doesn't exist. This happens because of the space in the filename.

    Be careful with the %ProgramFiles% because of 64-bit redirection that happens: http://msdn.microsoft.com/en-us/library/aa384187(VS.85).aspx.


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Tuesday, July 6, 2010 12:34 PM
  • Hi,

    I'm usig somehing like this (not only for PDFCreator):

    Starts in: "%programfiles%\PDFCreator\"

    Command line: unins000.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /LOG="%systemdrive%\Temp\PDFCreator_101_uninst.log"

    If the uninstallation of PDFCreator is running silently, don't forget to use "/SUPPRESSMSGBOXES", because the uninstaller is asking on the background: "Do you realy want to uninstall all custom settings made by the user... ". Otherwise uninstallation will crash.

    For more info look here http://www.biopdf.com/guide/uninstall_command_line_switches.php


    • Edited by gatoos Tuesday, April 2, 2013 7:54 PM
    • Proposed as answer by José H Vasconcelos Wednesday, April 20, 2016 8:17 AM
    Tuesday, April 2, 2013 7:53 PM