ERA 6.5 to ESMC Components Upgarde Issue

[Riadg 0]

Dear All 

Afer Succesful Upgrade to running componenet upgarde task , some clients failed , so do we create all in one installer and install on the failed clients ?

 

Thanks

 

 

 

Edited January 15, 2019 by Riadg

[MichalJ 434]

Do you know, what are the reasons of the failed upgrade? There could be many, like issues with repository connectivity, pending reboot, not enough disk space, etc. I would recommend to look at the failed clients, check the execution history at attempt to rerun the task. It might resolve itself. Some cases needs to be troubleshooted manually, but your description is so generic, that I can´t provide any guidance. 

[Riadg 0]

Hi 

We excuted client task Security Management Center Components Upgrade , the succesful ones only updated the agent , but endpoint security is not updated do we need to do something else ? once we finish  those we will start to debug the failed ones .

[MichalJ 434]

ESET Security Management Components Upgrade task is only intended to upgrade agents & other ESMC components. If you want to install a newer version of the endpoint, you need to do it via "software install task". The simplest way, if you already have ESMC V7 would be to navigate to the main dashboard, tab "ESET Applications", locate the table "outdated applications" and click on the individual entries you want to update. You can then click "update installed eset products", and that would automatically create corresponding installation tasks.

[Riadg 0]

Hi 

We still have problems in upgrading agents and eset security as well , please check these messages 

on server side

2019-02-21 06:00:07 Warning: CReplicationModule [Thread d48]: VerifyDeviceAuthenticationToken: Verification of authentication token: ac9ee386f05a39a7122ec45a40f4c3c007ac2c6a770897e2f95b69c44d63f5e9 failed (error_code=INVALID_TOKEN, status=TOKEN_EXPIRED, msg=
2019-02-21 06:00:07 Warning: CReplicationModule [Thread d48]: RpcCheckReplicationConsistencyHandler: Token validation failure
2019-02-21 06:04:21 Error: CRepositoryModule [Thread fc8]: GetFile: Host 'us-repository.eset.com' not found [error code: 20002]

 

Remote agents

 

2019-02-20 06:22:07 Error: CReplicationModule [Thread 328]: SendRequestAndHandleResponse: Rpc message response AUTHENTICATION_FAILURE (Token status: TOKEN_EXPIRED) -> Request new session token and resend replication request
2019-02-21 16:00:25 Warning: CSystemConnectorModule [Thread 90]: CWinRestartAgentTask: unable to restart at the moment. Retrying in a minute

 

Can you pleasde point us what can we do next

[MartinK 378]

1 hour ago, Riadg said:

2019-02-21 06:04:21 Error: CRepositoryModule [Thread fc8]: GetFile: Host 'us-repository.eset.com' not found [error code: 20002]

This issue indicates that hostname us-repository.eset.com cannot be resolved on this host, which is used for downloading installer packages and creating installers.

 

1 hour ago, Riadg said:

2019-02-20 06:22:07 Error: CReplicationModule [Thread 328]: SendRequestAndHandleResponse: Rpc message response AUTHENTICATION_FAILURE (Token status: TOKEN_EXPIRED) -> Request new session token and resend replication request

2019-02-21 16:00:25 Warning: CSystemConnectorModule [Thread 90]: CWinRestartAgentTask: unable to restart at the moment. Retrying in a minute

Unfortunately this log entries does not provide any details. I would recommend to check documentation for troubleshooting agent connectivity issues.

[Riadg 0]

Hi Martink

Resolved the issue , but still we have another issue which is as follows , can't deploy easet agent and product from console , we get the message ( try to install software manually ) when we try to install software manually we get error message ( This may be a result of malware activity and recommends to run a specialized cleaner ). We downloaded it from ESET and ran the specialized cleaner wirth a result of ( No malware had been found on the system ). When we remove ESET and try to reinstall the package again we get the same error of malware activity and error 108. msi.

In client log file before ESET removal we get this error which is in most machines , proxy is not enabled on the server.

2019-03-03 12:20:04 Warning: CReplicationModule [Thread 2228]: InitializeConnection: Not possible to establish any connection (Attempts: 1)
2019-03-03 12:20:04 Error: CReplicationModule [Thread 2228]: InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current)
2019-03-03 12:20:04 Error: CReplicationModule [Thread 2228]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: "WIN-95NG7KIBUQE" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "WIN-95NG7KIBUQE" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message:  Failed to create subchannel, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: WIN-95NG7KIBUQE:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: a601b950-8f2e-4bd7-8cde-3d05befd2491, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0]