Agent installation task fails with Event ID 2412 (Unable to find valid repository)

[FA1]

Dear All,

we are running ePO 5.10 upd 15 on prem and Agent version 5.7.9.139. The query failed product updates shows large numbers of machines that report Event ID 2412 with a descriptio of "Unable to find valid repository") The action that seems to fail is the installation of of the agent. Any pointers would be welcome.

Event ID: 2402

Severity: Critical

Event type: update

Error code: Unable to find valid repository

Initiator ID: EPOAGENT3000

Initiator Type: UpdateTask

Product Name: Trellix Agent

[cdinet]

What does the mcscript_deploy log show for why the repository is invalid?  It would show as either an out of date site or can't be reached typically.  When did this start and did anything at all change?  Does the epoapsvr log show any errors building the agent package?  Are the clients using the epo server or distributed repositories?

[FA1]

McScript_deploy.log

There are a number of the below. 

#23268 downloader client api sync_get_system_proxy failed.

#23268 network URL(http s://removedIP:443/Software/SiteStat.xml?hash={removed}) request, failed with curl error 28, Response 0, Connect code 0,

#23268 curl text 52 connect to removed IP port 443 failed: Timed out

There are also but less of the below.

#23268 MueEep Invoking events withEventId " 0" Severity " 0" Productid " EPOAGENT3000" Locale " 0409" UpdateType " N/A" UpdateError " 26" iUpdateState " 4" New Version " N/A" Date Time " N/A" Script Id" 4059" Custom Message " "

#23268 mue Updater session state = <4>, Update session result = "FAILED".

epoAppSvr log

Does not seem to contain any errors

The issue seems to have been present longer than 30 days

[cdinet]

So then you try the browser.

http s://removedIP:443/Software/SiteStat.xml

Can the system get to that url?  If so, uncheck everything in proxy settings, including automatically detect, and try again.  If it fails, then there might need to be some proxy settings configured in repository policy for the agent.  If it fails completely either way from browser, then that is outside of the agent and would appear to be a network or server side issue.  If it fails, then go to that server and check the server logs for any errors.  It is possible the server might have some problems accepting connections.  But typically a timeout connecting from the client is more along the network side.  It kind of depends on what happens to your browser check.  

[FA1]

In our case the failures turned out to be benign. The agent seems to try update and install actions even when it cannot get to the ePO. In that case it will log an error.