NOD32 remote deployment failiure after domain admin password change

Discussion in 'Other ESET Home Products' started by Dissidente, May 22, 2007.

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

    Dissidente Registered Member

    Joined:
    May 22, 2007
    Posts:
    3
    Hi.

    I manage a Windows 2003 / XP environment, with NOD32 Enterprise 2.7.32, managed through a NOD32 Server 1.0.14 and RAC 1.0.14.

    A few weeks ago we changed our Domain Admin password, without any complications.

    Since then we noticed that NOD32 deployment through the server ceased to complete. The account info under which the deployment is carried out is correct, but it simply wont install.

    Here is a sample of the installation log:

    Code:
    [2007-05-16 11:31:32.514] Status 1: NOD32 Installer (1.0.14) is preparing to install.
    [2007-05-16 11:31:32.514] Status 1: NOD32 Installer is trying to connect to 'FARO:2224'.
    [2007-05-16 11:31:32.530] Status 1: NOD32 Installer is creating a temporary file.
    [2007-05-16 11:31:32.545] Status 1: NOD32 Installer is downloading an installation package 'NOD32 Installation for NT 2000 XP and VISTA- Fullsix Package' from server 'FARO:2224'.
    [2007-05-16 11:31:33.980] Status 1: NOD32 Installer is installing NOD32.
    [2007-05-16 11:31:34.264] Status 1012: Failure during NOD32 install - exit code: -3.
    Trying to troubleshoot the problem we tryied to install the default package, also without success:

    Code:
    [2007-05-16 11:38:22.350] Status 1: NOD32 Installer (1.0.14) is preparing to install.
    [2007-05-16 11:38:22.350] Status 1: NOD32 Installer is trying to connect to 'FARO:2224'.
    [2007-05-16 11:38:22.366] Status 1: NOD32 Installer is creating a temporary file.
    [2007-05-16 11:38:22.366] Status 1: NOD32 Installer is downloading an installation package 'Default' from server 'FARO:2224'.
    [2007-05-16 11:38:23.716] Status 1: NOD32 Installer is installing NOD32.
    [2007-05-16 11:38:24.140] Status 1012: Failure during NOD32 install - exit code: -4.
    Shared a folder and copied the installation files with the package merged, also without success:

    Code:
    [2007-05-16 13:39:55.900] Status 1: NOD32 Installer is installing NOD32.
    [2007-05-16 13:39:56.134] Status 1012: Failure during NOD32 install - exit code: -3.
    [2007-05-16 13:49:19.106] Status 1: NOD32 Installer (1.0.14) is preparing to install.
    [2007-05-16 13:49:19.106] Status 1: NOD32 Installer is trying to connect to 'FARO:2224'.
    [2007-05-16 13:49:19.122] Status 1: NOD32 Installer is sending installation request.
    [2007-05-16 13:49:19.622] Status 1: NOD32 Installer (1.0.14) is preparing to install.
    [2007-05-16 13:49:19.622] Status 1: NOD32 Installer is trying to connect to 'FARO:2224'.
    [2007-05-16 13:49:19.638] Status 1: NOD32 Installer is creating a temporary file.
    [2007-05-16 13:49:19.638] Status 1: NOD32 Installer is downloading an installation package 'NOD32 Installation for NT 2000 XP and VISTA- Fullsix Package' from server 'FARO:2224'.
    [2007-05-16 13:49:20.998] Status 1: NOD32 Installer is installing NOD32.
    [2007-05-16 13:49:21.342] Status 1012: Failure during NOD32 install - exit code: -3.
    [2007-05-16 13:49:22.655] Status 1012: Failure during NOD32 install - exit code: -3.
    [2007-05-16 13:49:22.655] Status 1: Request failed. NOD32 Installer has administrator rights, trying to continue.
    [2007-05-16 13:49:22.655] Status 1: NOD32 Installer is creating a temporary file.
    [2007-05-16 13:49:22.655] Status 1: NOD32 Installer is downloading an installation package 'NOD32 Installation for NT 2000 XP and VISTA- Fullsix Package' from server 'FARO:2224'.
    [2007-05-16 13:49:24.109] Status 1: NOD32 Installer is installing NOD32.
    [2007-05-16 13:49:24.265] Status 1012: Failure during NOD32 install - exit code: -3.
    After browsing a little in this forum I found a post referring that the exit error codes are Windows system codes, so I checked which each code standed by:

    ERROR_PATH_NOT_FOUND
    3 The system cannot find the path specified.

    ERROR_TOO_MANY_OPEN_FILES
    4 The system cannot open the file.

    It doesn't make much sense. NOD32 installer can't find the path that himself setted? Wierd...

    We ended up installing several machines manually, using the client's installer, configuring the update mirror to our own, from where it receives the package configuration and managing server information.

    I don't know if it is a relevant information, but we are now meeting the license threshold clients, and are waiting for aproval for the license upgrade. Still, this problem started a couple of workstations prior to the threshold, so I assume it has nothing to do with it, also from my previous experience using NOD32.

    Any ideas as to what is going on here?

    Even though the problems started on the same time as the password change, I really don't see any relation between the events, as the deployment account information is correct. :doubt:

    Hope anyone has the answer...
     
  2. Dissidente

    Dissidente Registered Member

    Joined:
    May 22, 2007
    Posts:
    3
    I see nobody has any clue about this... :(
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    The agent (nod32install) has all information necessary for establishing a connection to RAS server embedded. Therefore, if you change some of those settings you also need to re-create the installation package.
     
  4. Dissidente

    Dissidente Registered Member

    Joined:
    May 22, 2007
    Posts:
    3
    Marcos,

    I don't think this is the case. The account information under which the package will be installed is prompted at the beggining of the operation in RAS.

    Even so I created a clean new package and it failed once again, with the same error code. :rolleyes:
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    Well, negative exit codes usually means a crash during installation. I'd suggest that you try installing nod32 manually by running setup.exe with the /test parameter and send nsetup.log to support[at]eset.com along with a link to this thread so that we have some background info about the case.
     
Thread Status:
Not open for further replies.