solas

We have been using this product for 10 years and renewals have never been an issue. I would appreciate if someone could reach out to me and assist me.

Public license is 33C-HEP-9XJ i don;t see anything in common with the machines that are failing. Even stand alone clients are having problems.

I just renewed my license for a year and many of my clients are showing product not activated. To make matters worse, the clients that are activated are showing a mix of old and new license information. Some show they expire next month and others show the correct expiry a year from now. Product activation fails entering the key manually on the client fails as well. I was able to remotely uninstall the Eset AV software using ERA on one client and then remotely push it out and on that particular client the activation still failed, however I was able to activate it by entering the key manually in to the client. I have tried several others and the uninstall fails so can't even go that route. What is causing all of this headached? Years past I just renewed the license and all clients switched to the new date automatically. The key information is always the same. Please help.

The repository is set for autoselect While the log says that it cannot be resolved, I am able to nslookup the hostname of the server from the client and it responds correctly. I can also nslookup the name of the client from the ESMC and it responds correctly. I have firewall rules to allow the ip of the ESMC inbound on all ports. The client is currently reporting in tot he ESMC just fine and has the most up to date version of the agent. I am just unable to install the latest AV client.

In this case I am trying to install a new version of the agent.

I am still battling with client update inconsistency. Sometimes they fail and then I try again a few minutes later and they are successful without any changes being made. Agent trace logs are showing the messages below and the ESMC console shows Failed to synchronize package repository. See trace message for more details. The name of the server resolves accurately on the client and I have windows firewall rules to allow the ESMC server on all ports. 2019-10-18 17:00:44 Error: CReplicationModule [Thread 167c]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: "era001.corp.company.com" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "era001.corp.company.com" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message: Failed to create subchannel, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: era001.corp.company.com:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 79983a6a-b3d1-4533-9469-4bcea77e58bd, Sent logs: 0, Cached static objects: 50, Cached static object groups: 9, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] 2019-10-18 17:01:44 Error: CSystemConnectorModule [Thread 1690]: CDeviceSnapshotWinLoaderUtils::ReadDiskDriveIDs: calling funtion=[CreateFile] for volume=[\\?\Volume{258f614d-f0e0-11e9-9fe9-9cebe8762ed0}] failed, error=[5] 2019-10-18 17:01:44 Error: CNetworkGrpcModule [Thread 31a0]: GRPC:Failed to resolve: era001.corp.company.com:2222 2019-10-18 17:01:44 Error: CReplicationModule [Thread 167c]: InitializeConnection: Initiating replication connection to 'host: "era001.corp.company.com" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "era001.corp.company.com" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message: Failed to create subchannel, and error details: 2019-10-18 17:01:44 Warning: CReplicationModule [Thread 167c]: InitializeConnection: Not possible to establish any connection (Attempts: 1) 2019-10-18 17:01:44 Error: CReplicationModule [Thread 167c]: InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current) 2019-10-18 17:01:44 Error: CReplicationModule [Thread 167c]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: era001.corp.company.com port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "era001.corp.company.com" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message: Failed to create subchannel, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: era001.corp.company.com:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 79983a6a-b3d1-4533-9469-4bcea77e58bd, Sent logs: 0, Cached static objects: 50, Cached static object groups: 9, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0]

I just upgraded to ESMC 7 and I'm having issues with upgrading clients on any machines that are not local to the ESMC. Previously on ERA 6.5 I had one server in the UK servicing all my users in the UK and North America without issues for years. I read another thread where someone found a proxy timeout setting in the httpd.conf file but I don't have the same settings in my file and I am running on windows not an appliance. How do I resolve this? As it stands I can't get the majority of my clients to update. The remote agent updates fine but the software install task to upgrade the eset av fails every time.