01:29:26 Error: CReplicationModule : InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current) 01:29:26 Warning: CReplicationModule : InitializeConnection: Not possible to establish any connection (Attempts: 1) 01:29:26 Error: CReplicationModule : InitializeConnection: Replication connection problem: GetAuthenticationSessionToken: Received failure status response: AUTHENTICATION_FAILED (Error description: unable to authenticate entity) 01:29:26 Error: AuthenticationModule : EntityAuthenticationCommand execution failed with: Failed to create credentials for communication 01:29:26 Warning: AuthenticationModule : EntityAuthenticationCommand execution failed with:, falling back to legacy implementation Trace log has this infotmation reported each minute: Error code: 0x80092002Ĭheck that correct peer certificate format (PFX/PKCS12) is used in the configurationĬheck that correct peer certificate password was set in the configuration We have a client server with similar symptoms - it's running Windows Server 2016.įrom C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html the issue appears to be with the Peer Certificate:Įrror: ParsePfxCertificate: PFXImportCertStore failed with An error occurred during encode or decode operation. The servers are running Windows Server 2012 R2. I have tried restarting one of the servers to complete the update however it still isn't connecting to the ESET PROTECT server. The agent ceased reporting to the server after the update. From the update log (attached) it appears the update completed ok but required a restart to finalise the install. We have 3 server devices that had their ESET Management Agents automatically attempt an upgrade from vers. We're an MSP running our own ESET PROTECT server to manage our clients' ESET endpoints.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |