Jump to content

Archived

This topic is now archived and is closed to further replies.

verus

ERA 6 with Windows XP not starting

Recommended Posts

Hi,

 

I installed ESET administrator agent on a windows XP computer (push install via server) and the first time the agent worked but after reboot, the administrator agent doesn't start anymore.

In the windows event logs I get this:

 

De ESET Remote Administrator Agent-service is gestopt met de specifieke servicefout 70 (0x46).
 
Zie Help en ondersteuning op hxxp://go.microsoft.com/fwlink/events.aspvoor meer informatie.
 
It's in dutch but it says that de service stopped because of fault 70 (0x46).
No Idea what that means.
 
The status log shows this:
 
Peer certificate | 2015-Mar-10 13:04:29 | Error: No such node (result.strIssuer)
 
 
trace.log:
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Starting module NetworkModule
2015-03-10 13:04:29 Information: CAgentSecurityModule [Thread f0]: Checking agent peer certificate expiration in 30 days
2015-03-10 13:04:29 Information: SchedulerModule [Thread 5e0]: Received message: RegisterSleepEvent
2015-03-10 13:04:29 Information: Kernel [Thread ef0]: Initiating crash dumps sender for directory: "C:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Dumps\"
2015-03-10 13:04:29 Error: Service [Thread dc4]: Kernel start: Last starting module failed with: No such node (result.strIssuer)
2015-03-10 13:04:29 Information: Service [Thread dc4]: Preparing to stop
2015-03-10 13:04:29 Error: CAgentSecurityModule [Thread f0]: No such node (result.strIssuer)
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Used memory before modules shutdown is 48100 KB
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CUpdatesModule
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CSymbolsModule
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CDatabaseModule
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: CAgentSecurityModule
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Preparing to stop module: SchedulerModule
2015-03-10 13:04:29 Information: Kernel [Thread dc4]: Stopping crash dumps sending thread
2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CUpdatesModule
2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CSymbolsModule
2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CDatabaseModule
2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: CAgentSecurityModule
2015-03-10 13:04:30 Information: Kernel [Thread dc4]: Stopping module: SchedulerModule
2015-03-10 13:04:30 Information: Service [Thread dc4]: Kernel shut down nicely
2015-03-10 13:04:30 Information: AutomationModule [Thread dc4]: Facade: All triggers have been unloaded.
2015-03-10 13:04:30 Error: Service [Thread dc4]: Kernel start failed
 
 
 
any idea ?
thanks.
 

Share this post


Link to post
Share on other sites

Please compress the content of the folder "C:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Dumps\" and send it to us for analysis along with the output of running ESET Log Collector (hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3466). Upload the stuff to a safe location and pm me the download link(s).

Share this post


Link to post
Share on other sites

The dump folder is empty.

I will send the ESET log collector log via a message to you.

Thanks, Ph.

Share this post


Link to post
Share on other sites

I have this same error and ESET agent crash on another computer with windows 8 also now.

Share this post


Link to post
Share on other sites

I'm having the same issue, no dump generated at all, i'm gonna reproduce the steps you've said Marcos and wait for an answer.

Share this post


Link to post
Share on other sites

ERA Agent is not crashing, but it is stopping because of missing peer certificate or bad password for that certificate. This can happen if policy for that agent was made and a certificate was not set or password was set incorrectly. Only option at this moment would be to repair installation and set correct certificates.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...