Jump to content

Cannot remove client after ERA upgraded from 5.1.34 to 5.1.38.


Recommended Posts

Hello,

 

One month ago, I used the ERA maintenance tool(v5.1.38) migrate the ERA server from the old one to a new one with a different IP address, server name follows the ESET manual. Today, I found one issue that is I cannot remove client in era console(v5.1.38). The progress bar is always stay there at "Deleting 1%..."

 

I use the sql server management studio express to manually delete the client in DB is no problem(Test database) on same server.

 

 

Old Server Name:WS1

Windows 2008 R2 Std+MSSQL 2008 R2+ERA Server 5.1.34

 

New Server Name:WS2

Windows 2012 R2 Std+MSSQL 2008 R2+ERA Server 5.1.38

 

Any idea?

 

Thanks for your time. cheers!

Edited by nfree
Link to comment
Share on other sites

Hello nfree,

 

Please try restarting the ESET Remote Administrator server service. For directions on this process, please click or copy/paste the following ESET Knowledgebase article into your web browser
-------------------------------------------------------------------------------
How do I restart the ESET Remote Administrator Server service?
hxxp://kb.eset.com/zap/SOLN743
-------------------------------------------------------------------------------

 

You will need to reconnect the console to the server after restarting the service. Please try deleting the client after reconnecting.

 

Thank you,

ChadH

Link to comment
Share on other sites

Hello nfree,

 

Please try restarting the ESET Remote Administrator server service. For directions on this process, please click or copy/paste the following ESET Knowledgebase article into your web browser

-------------------------------------------------------------------------------

How do I restart the ESET Remote Administrator Server service?

hxxp://kb.eset.com/zap/SOLN743

-------------------------------------------------------------------------------

 

You will need to reconnect the console to the server after restarting the service. Please try deleting the client after reconnecting.

 

Thank you,

ChadH

 

 

Hi ChadH,

 

Thanks for your reply, I tried your method but not helpful for my issue.

Link to comment
Share on other sites

  • Administrators

Please carry out as follows:

- enable debug logging in the ERA Server setup (Debug log -> Log to text file)

- restart the ERA Server service

- reproduce the problem

- compress the debug log \logs\era_debug.log and send it to me via a personal message.

Link to comment
Share on other sites

Please carry out as follows:

- enable debug logging in the ERA Server setup (Debug log -> Log to text file)

- restart the ERA Server service

- reproduce the problem

- compress the debug log \logs\era_debug.log and send it to me via a personal message.

 

Hi Marcos,

 

I just sent the debug info to you, please check it. Thank you!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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