Jump to content

New eset client can not connect to the Era server


Recommended Posts

A new pc with the Eset Remote agent installed receives an error in the agent connection. Existing clients do not have a problem

Error: SendRequestAndHandleResponse: Rpc message response INTERNAL_ERROR. Error message: . RequestId: 48a4896c-fe3e-4485-bb33-c3df3fc473d8

  • Task: CStaticObjectTask
  • Scenario: Automatic replication (REGULAR)
  • Connection: ESET-ERA.********
  • Connection established: true
  • Replication inconsistency detected: false
  • Server busy state detected: false
  • Realm change detected: false
  • Realm uuid: 35c8e672-9aac-467e-b4e0-808bd75b5b00
  • Sent logs: 0
  • Cached static objects: 1
  • Cached static object groups: 1
  • Static objects to save: 124
  • Static objects to delete: 1
  • Modified static objects: 0
  • All replication attempts: 93

ESET PROTECT On-Prem (Server), Version 11.1 (11.1.756.0)

ESET PROTECT On-Prem (Web Console), Version 11.1 (11.1.144.0)

Link to comment
Share on other sites

  • 2 weeks later...
  • Most Valued Members

Is there anything in the trace.log? 

Link to comment
Share on other sites

Hello BOB,

according to this topic

there is a bug on EP version 11.1.x , there is workaround to restart EP service after new agent deploy.

Edited by kelepe
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

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