Jump to content

Problem update


Krzysztof.Wawro
 Share

Recommended Posts

Hi,

I have a big problem. After update ESET ERA from v6.5 to ESMC v7 i can't update Eset ERA Agents to Eset Management Agents on my 1/2 workstations (I have 700-750 workstations). I try update via GPO (msi + mst files) and  ESMC console tasks. All the time it is the same effect. In trace.log on workstations i see the agents update successfully but next, the agents rollback to 6.5v. In ESMC console after upadate task i see duplicate workstations (one with Agent v6.5 and second with Agent v6.5 + Agent v7), but a few minutes later workstation with Agent v6.5 + Agent v7 does't raport to ESMC server and the ESMC console task still running (until expired). Often the last entry on trace.log is:

"Error: CReplicationModule [Thread e40]: CReplicationManager: Failed to start replication, replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (OUT_OF_ORDER)) is already in use"

Thanks ! 

Krzysztof 

Link to comment
Share on other sites

  • Administrators

A recommended way of upgrading agent is by sending a SMC component upgrade task to clients. Did you try that?

image.png

 

Link to comment
Share on other sites

  • Administrators

Could you please post C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\trace.log after upgrade? Also I recall there should be an install log created in the temp folder which might shed more light. Other mods should be able to provide the exact name.

Link to comment
Share on other sites

There is re-upgrade-agent.log

 

= Logging stopped: 2019-04-25  15:48:11 ===
MSI (s) (98:CC) [15:48:11:481]: Note: 1: 1708 
MSI (s) (98:CC) [15:48:11:512]: Product: ESET Management Agent -- Installation failed.

MSI (s) (98:CC) [15:48:11:543]: Instalator Windows zainstalował produkt. Nazwa produktu: ESET Management Agent. Wersja produktu: 7.0.577.0. Język produktu: 1033. Producent: ESET, spol. s r.o.. Stan powodzenia lub błędu instalacji: 1603.

MSI (s) (98:CC) [15:48:11:606]: Deferring clean up of packages/files, if any exist
MSI (s) (98:CC) [15:48:11:621]: MainEngineThread is returning 1603
MSI (s) (98:20) [15:48:11:699]: No System Restore sequence number for this installation.
MSI (s) (98:20) [15:48:11:746]: User policy value 'DisableRollback' is 0
MSI (s) (98:20) [15:48:11:762]: Machine policy value 'DisableRollback' is 0
MSI (s) (98:20) [15:48:11:793]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (98:20) [15:48:11:840]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (98:20) [15:48:11:902]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (98:20) [15:48:11:933]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (98:20) [15:48:11:949]: Restoring environment variables
MSI (s) (98:20) [15:48:11:980]: Destroying RemoteAPI object.
MSI (s) (98:B8) [15:48:12:011]: Custom Action Manager thread ending.
MSI (c) (D0:94) [15:48:12:074]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (D0:94) [15:48:12:105]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2019-04-25  15:48:12 ===

Link to comment
Share on other sites

  • Administrators

Please post the whole re-upgrade-agent.log since the log above is truncated and contains only last records from the log that are not helpful for troubleshooting the issue.

Link to comment
Share on other sites

  • Administrators

Agent upgrade ended because a newer version was detected:
A newer version of ESET Remote Administrator Agent is already installed. The installation will be aborted.

When installing the latest agent manually, run the msi with the "/lvx* install.log" parameter and provide install.log.

Link to comment
Share on other sites

  • Administrators

The problem seems to be that two versions of agent were detected:

PROPERTY CHANGE: Modifying WIX_UPGRADE_DETECTED property. Its current value is '{41F12F70-5FA9-43F5-94F4-53B54EB4EEC4}'. Its new value: '{41F12F70-5FA9-43F5-94F4-53B54EB4EEC4};{94FB5797-B020-44BC-BCAB-DBB35366B9B0}'.

{41F12F70-5FA9-43F5-94F4-53B54EB4EEC4} is a GUID of 6.5.522.0
{94FB5797-B020-44BC-BCAB-DBB35366B9B0} is a GUID of 6.4.283.0

Did you deploy both via GPO or how? Is either one currently installed?

Link to comment
Share on other sites

Hi,

I deployed two versions of agent via GPO(The third version is agent v7) in the same GPO( First 6.4, next 6.5 and this time, i try deploy 7). Version 6.5 updates version 6.4. Version 7 updates versions 6.5 and 6.4. Currently version is 6.5 and on workstations with this agent, update end with failure.

Link to comment
Share on other sites

  • 2 weeks later...

Hi. I solved this problem, via script, which delete REG Keys (old agent versions)

script:

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\786A20824144DB1449FA500C3A98D88D" /v "7975BF49020BCB44CBBABD3B35669B0B" /f
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\7975BF49020BCB44CBBABD3B35669B0B" /f
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{94FB5797-B020-44BC-BCAB-DBB35366B9B0}" /f

REG DELETE "HKEY_LOCAL_MACHINE\Software\Classes\Installer\UpgradeCodes\786A20824144DB1449FA500C3A98D88D" /v "7975BF49020BCB44CBBABD3B35669B0B" /f
REG DELETE "HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\7975BF49020BCB44CBBABD3B35669B0B" /f
REG DELETE "HKEY_LOCAL_MACHINE\Software\Classes\Installer\Features\7975BF49020BCB44CBBABD3B35669B0B" /f

REG DELETE "HKEY_CLASSES_ROOT\Installer\UpgradeCodes\786A20824144DB1449FA500C3A98D88D" /v "7975BF49020BCB44CBBABD3B35669B0B" /f
REG DELETE "HKEY_CLASSES_ROOT\Installer\Products\7975BF49020BCB44CBBABD3B35669B0B" /f
REG DELETE "HKEY_CLASSES_ROOT\Installer\Features\7975BF49020BCB44CBBABD3B35669B0B" /f

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...