Jump to content

Eset Agent Error RPC Massage Response Busy


Recommended Posts

have a problem Same like the following, I have tried to telnet ESMC port 2222 from the client side and it was successful, but for the last replication status the agent status is still error, is there a solution to solve this error?

RPC.PNG

Link to comment
Share on other sites

  • Administrators

Looks like the server db has grown quite a lot recently and the server is busy. Have you recently added a bunch of new clients that started to report to the ESET PROTECT server? Have you recently made any changes to policies or requested diagnostic logs from clients? Have you made any changes to the db or the hw configuration of the ESET PROTECT / db server?

Link to comment
Share on other sites

 

Yes, indeed, in recent days we have added a lot of new clients, there is a solution to this problem

Link to comment
Share on other sites

  • Administrators

How many clients are reporting to the ESET PROTECT server?
What is the hw configuration of the server?
What db do you use? Is the db on the same server or another one? If the latter, what is the hw configuration of the db server?
Have you created a policy that enabled additional reporting, such as all installed applications, websites allowed by Web Control, etc.?

Link to comment
Share on other sites

30,000 clients reporting to the ESET PROTECT server

The db we use is Microsoft SQL Server 2016, and the db server is on a different server
yes we do additional reporting, such as all installed applications, websites that are permitted by Web Control

Next we send the dxdiag image from the ESET PROTECT server and the db server1436389845_HWServerEset.jpg.fcbac441abca833a2ecd7786ad475766.jpg940689491_HWServerDBEset.jpg.07456609a30c49845cc580df4d54314f.jpg

Link to comment
Share on other sites

  • Administrators

Start reducing the load by removing the Web Control policy which enables logging of all visited websites. This can produce thousands of new records on each client on a daily basis which causes a burned on the server and DB.  I'd recommend contacting your local ESET distributor for instructions how to delete the Web Control logs from the DB.

Another thing that would lower the load is reporting of all installed applications. Try temporarily disabling this option.

Link to comment
Share on other sites

Identification software is needed for policy mirrors in each branch so it can't be disabled

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...