Failure during the package uninstall

Discussion in 'ESET NOD32 Antivirus' started by ssheikh, Apr 5, 2009.

Thread Status:
Not open for further replies.
  1. ssheikh

    ssheikh Registered Member

    Joined:
    Apr 5, 2009
    Posts:
    1
    I'm trying to uninstall v4 AV using Remote Administrator Console. Using "Uninstall ESET Security Products and NOD32 version 2" in the remote installation type. My settings are:

    NOD32: /UNINSTALL /PWD=""<password>""
    ESS: /qn REBOOT="Force"

    The password is surrounded by two sets of quotes. Though I have tried with one set and no quotes at all as well. Somehow I don't think that matters as that seems to be part of the parameters for v2.

    This is what happens after I click the uninstall button:

    1. The status window displays error:
    Code:
    Could not install ESET Installer on target computer (SC error code 11, GLE error code 5)
    and a prompt for username password opens.

    2. I provide a userid and password that has administrative rights on the target machine (which by the way the account that I am logged into the machine with remote administrator console also has admin rights over the target machine)

    3. The status window displays a couple of messages like starting remote installation process and starting ESET Installer...

    4. And then the process terminates with error:
    Code:
    Failure during the package uninstall - exit code: 1603, additional code: 2, description: Fatal error during installation.
    This is what I see in the c:\windows\temp\einstaller.log on the client machine itself.

    Code:
    [2009-04-05 12:56:18.263] Status 1, ID 0: ESET Installer (3.0.105) is preparing to uninstall.
    [2009-04-05 12:56:18.263] Status 1, ID 0: ESET Installer is trying to connect to 'avserver:2224'.
    [2009-04-05 12:56:18.294] Status 1, ID 0: ESET Installer is preparing to uninstall the package.
    [2009-04-05 12:56:18.294] Status 1, ID 0: ESET Installer is uninstalling the package.
    [2009-04-05 12:56:18.716] Status 1, ID 0: Installation package launch finished.
    [2009-04-05 12:56:18.716] Status 1, ID 0: ESET Installer is trying to reconnect to '192.168.1.69:2224'.
    [2009-04-05 12:56:18.731] Status 1, ID 0: Reconnected to '192.168.1.69:2224'.
    [2009-04-05 12:56:18.731] Status 1012, ID 0: Failure during the package uninstall - exit code: 1603, additional code: 2, description: Fatal error during installation.
    [2009-04-05 12:56:18.731] Status 20006, ID 0: Service stuff cleanup finished with return code 0.
    [2009-04-05 13:00:13.511] Status 1, ID 0: ESET Installer (3.0.105) is preparing to uninstall.
    [2009-04-05 13:00:13.511] Status 1, ID 0: ESET Installer is trying to connect to 'avserver:2224'.
    [2009-04-05 13:00:13.527] Status 1, ID 0: ESET Installer is preparing to uninstall the package.
    [2009-04-05 13:00:13.527] Status 1, ID 0: ESET Installer is uninstalling the package.
    [2009-04-05 13:00:14.058] Status 1, ID 0: Installation package launch finished.
    [2009-04-05 13:00:14.058] Status 1, ID 0: ESET Installer is trying to reconnect to '192.168.1.69:2224'.
    [2009-04-05 13:00:14.058] Status 1, ID 0: Reconnected to '192.168.1.69:2224'.
    [2009-04-05 13:00:14.199] Status 1012, ID 0: Failure during the package uninstall - exit code: 1603, additional code: 2, description: Fatal error during installation.
    [2009-04-05 13:00:14.199] Status 20006, ID 0: Service stuff cleanup finished with return code 0.
    
    The Windows Installer log terminates with the following error:

    Code:
    :
    :
    Action start 12:56:18: InstSuppIsUninstallAllowed.
    ESET: Entering CA InstSupp!IsUninstallAllowed
    MSI (s) (C4!44) [12:56:18:653]: Product: ESET NOD32 Antivirus -- Error 5004. Enter a valid password to continue uninstallation.
    
    Error 5004. Enter a valid password to continue uninstallation.
    ESET: Returing from CA InstSupp!IsUninstallAllowed, with status 1627
    Action ended 12:56:18: InstSuppIsUninstallAllowed. Return value 3.
    Action ended 12:56:18: INSTALL. Return value 3.
    :
    :
    MSI (s) (C4:48) [12:56:18:685]: Note: 1: 1725 
    MSI (s) (C4:48) [12:56:18:685]: Product: ESET NOD32 Antivirus -- Removal failed.
    
    MSI (s) (C4:48) [12:56:18:685]: Cleaning up uninstalled install packages, if any exist
    MSI (s) (C4:48) [12:56:18:685]: MainEngineThread is returning 1603
    MSI (s) (C4:50) [12:56:18:685]: Destroying RemoteAPI object.
    :
    
    My installation at the client is password protected. I am assuming that password somehow has to be fed to the Uninstall package. It seems that the password parameter in the settings of the Uninstall package only applies to NOD32 v2.

    If the above assumption of mine is correct, then how do I supply an uninstallation password from the remote administration console?

    As far as I can tell from the registry, there are no remnants of AVAST, spybot, or any other AntiVirus/Anti malware software on the machine.

    Uninstalling the client from Add/Remove programs works without a problem.

    Thanks.
     
  2. parenormal

    parenormal Registered Member

    Joined:
    Apr 8, 2009
    Posts:
    1
    Hi, I'm currently having the same problem as ssheikh with my NOD v.4. In my readings and searches I have come to the same conclusion about the /PWD= command, from what I have read it appears to be associated with version 2.x of nod. Any help on the issue would be greatly appreciated.
     
  3. Miami_T

    Miami_T Registered Member

    Joined:
    Apr 17, 2009
    Posts:
    1
    I have the same problem and I solved it by entering /PWD=""password"" in right field under ESS options.
     
  4. lukke

    lukke Registered Member

    Joined:
    Aug 22, 2009
    Posts:
    2
    The ESS is used for version 3.0/4.0. You need to enter PASSWORD=password, make sure you don't put a / in front of PASSWORD or any quotes. This worked for me and hope it helps others.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.