Jump to content

Update to new agent wont work on several servers


Recommended Posts

Hi, 

 

There is less than 10% of workstations that wont update the agent. One of the errors that is on every workstation from trace.log :

 

2015-09-28 14:12:27 Error: CEssConnectorModule [Thread 118c]: Set policy failed: CNodcommChannel: Send request failed with 14, Command failed - Make sure that Agent runs with Administrator privileges.

 

Strange thing is that all workstations are in domain, and group policies are the same for all, so permissions should not be the problem here. But what can i do to check if the issue is with permissions?Agent is running as which user? Also there is some error, with replication:

 

 Error: NetworkModule [Thread 854]: Unable to resolve any endpoints.resolve: (0x2af9), No such host is known
2015-09-29 08:36:41 Error: CReplicationModule [Thread 2118]: CReplicationManager: Replication (network) connection to 'host: "xxxxxxxxxx" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2af9), No such host is known
2015-09-29 10:41:41 Error: NetworkModule [Thread 854]: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found
2015-09-29 10:41:41 Error: CReplicationModule [Thread f8]: CReplicationManager: Replication (network) connection to 'host: "xxxxxxxxxx" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found
2015-09-29 11:44:41 Error: NetworkModule [Thread 854]: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found
2015-09-29 11:44:41 Error: CReplicationModule [Thread 1efc]: CReplicationManager: Replication (network) connection to 'host: "xxxxxxxxxx" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found
 
But i can resolve server host name with no problem, and also if this is a problem, it would be the problem for all workstations ( i guess). 
 
Regards, 
 
Uros
Edited by ucvijan
Link to comment
Share on other sites

  • ESET Moderators

Hello,

Are the clients with the permission issue same as the ones with the replication issue?

If so, does uninstalling and reinstalling the Agent resolve the issue?

Link to comment
Share on other sites

I didnt try to reinstall the agent, as i had problems with remote uninstall (from ERA) before. And users (mostly developers)  are already frustrated that computer froze and had to restart the workstation. Problem was, their work was not saved. So i was looking for some solution where i will not bother them directly. 

 

Checked in the trace logs on all workstations that wont update the agent. And each has the same problem  with permission issue, and only couple with the resolving issue.

 

One of them has this as well as next to the permission issue:

 

2015-10-01 07:47:12 Error: CReplicationModule [Thread d94]: CReplicationManager: Failed to start replication, connection for replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (REGULAR)) is already pending
2015-10-01 08:42:12 Error: NetworkModule [Thread 96c]: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found
2015-10-01 08:42:12 Error: CReplicationModule [Thread 17f8]: CReplicationManager: Replication (network) connection to 'host: "xxxxxxxxxxxxx" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found
2015-10-01 11:51:12 Error: CReplicationModule [Thread 2e0c]: CReplicationManager: Failed to start replication, connection for replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (REGULAR)) is already pending
2015-10-01 11:52:12 Error: CReplicationModule [Thread 2cbc]: CReplicationManager: Failed to start replication, connection for replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (REGULAR)) is already pending
2015-10-01 11:53:12 Error: CReplicationModule [Thread 2c60]: CReplicationManager: Failed to start replication, connection for replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (REGULAR)) is already pending
2015-10-01 11:54:12 Error: CReplicationModule [Thread 247c]: CReplicationManager: Failed to start replication, connection for replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (REGULAR)) is already pending
2015-10-01 11:55:12 Error: NetworkModule [Thread 96c]: The connection will be closed due to timeout. SessionId:244
2015-10-01 11:55:12 Error: CReplicationModule [Thread 2878]: CReplicationManager: Stopping replication scenario due to network connection close (scenario type: Regular, scenario status: Running)
2015-10-01 11:55:12 Error: CReplicationModule [Thread 2878]: CReplicationManager: Failure of scenario (type=Regular, task_id='00000000-0000-0000-7005-000000000001', link='Automatic replication (REGULAR)' (00000000-0000-0000-7007-000000000001), current_step=Receiving [MetadataStaticObjects], current_step_phase=Receiving, remote_peer=host: "xxxxxxxxxxx" port: 2222, remote_peer_type=3, remote_peer_id=c5abeb78-c325-4dc9-92b3-7e54988e459f, remote_realm_id=c5abeb78-c325-4dc9-92b3-7e54988e459f)
2015-10-01 11:55:12 Error: NetworkModule [Thread 2f8c]: User context does not exist for id 244
 
Maybe I am doing something wrong with uninstalling the agent form ERA console. I should go with the task:

Stop Managing (Uninstall ERA Agent)

 

That should be enough, and them to install the agent again (by that i mean deploy)?

 
Regards, 
 
Uros
Edited by ucvijan
Link to comment
Share on other sites

  • 4 weeks later...
  • ESET Moderators

Hello, as nobody had any suggestions for this case, please contact your local customer care in order to investigate the issue further.

Thank you.

Link to comment
Share on other sites

  • Administrators

Just to make sure, are you using the latest version of ERA? Another customer claimed that upgrading ERA components to the latest version via the ERA Component Upgrade task solved the issue.

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