Kein gültiges Repository / no valid repository found

[cheetah]

Ich habe derzeitig ein paar System, welche sich nicht über den Update Task Updaten lassen.

Hier bekomme ich dann gemeldet, dass „Kein gültiges Repository“ gefunden wird.

Was ich schon probiert habe:

Agent neu ausgebracht = KEINE Besserung

VSE Deinstalliert und im Anschluss neu installiert = KEINE Besserung

Alles per Removal Tool deinstalliert und im Anschluss erst den Agent über den ePO neu Ausgebracht und dann noch einmal die VSE über den ePO neu Ausgebracht.

Auch dieses hat KEINE Besserung gebracht.

Wie gesagt, es betrifft hier nur 4-7 Systeme von 37.

Agent Version 5.6.2.209

VSE Version 8.8 Patch 13

Windows 10 Versionen 1809 und 1903 betroffen.

Hat hier noch jemand einen Super Tipp für mich?

I currently have a few systems that can not be updated via the Update Task.
Here I get reported that "No valid repository" is found.

What I have already tried:
Agent reapplied = NO improvement
VSE Uninstalled and then reinstalled = NO improvement

All deinstalled by virus removal tool and then reissued the agent on the ePO and then again issued the VSE on the ePO.
This has NOT brought any improvement.

As I said, it affects only 4-7 systems of 37 here.
Agent Version 5.6.2.209
VSE Version 8.8 Patch 13
Windows 10 versions 1809 and 1903 affected.
Does anyone have a super tip for me here?

[vivs]

Hello,

Have you tried checking the logs:

Please go to the below (default) location and try to check the logs:

C:\ProgramData\McAfee\Agent\logs

Try to check masvc.log and mcscript.logs

Was my reply helpful?
If you find this post useful, Please give it a Kudos! l Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

[cheetah]

Danke euch beiden.

Ich werde mir die Log Dateien mal genauer anschauen und mich dann wieder melden.

[chealey]

As @vivs said no valid repository typically means that there is a network error between the client and the server. The "mcscript" log would help you see why it's failing. Look for "no valid repository" in the log and look around that time, you'll probably see things like curl error 6 (just an example)

[cheetah]

Just found:

2019-09-13 13:50:02 I #2684 downloader Downloading file from https://192.168.1.102:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7} to C:\WINDOWS\TEMP\SiteStat.xml with timeout 18000
2019-09-13 13:50:02 I #2684 network URL(https://192.168.1.102:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7}) request, failed with curl error 7, Response 0, Connect code 0,
2019-09-13 13:50:02 I #2684 curl text 21 Closing connection 0
2019-09-13 13:50:02 E #2684 downloader Error trace:
2019-09-13 13:50:02 E #2684 Thread [Main thread]->
2019-09-13 13:50:02 E #2684 SessMgr [initializeScript]->
2019-09-13 13:50:02 E #2684 creposi [setNextRepositoryToUse]->
2019-09-13 13:50:02 E #2684 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2019-09-13 13:50:02 E #2684 downloader Downloading file from https://192.168.1.102:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7} to C:\WINDOWS\TEMP\SiteStat.xml failed.
2019-09-13 13:50:02 I #2684 downloader calling system proxy client api.
2019-09-13 13:50:02 I #2684 downloader client api sync_get_system_proxy failed.
2019-09-13 13:50:02 I #2684 downloader Downloading file from https://****.nbg.l-h.de:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7} to C:\WINDOWS\TEMP\SiteStat.xml with timeout 18000
2019-09-13 13:50:02 I #2684 network URL(https://***.de:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7}) request, ro, Response 0, Connect code 0,
2019-09-13 13:50:02 I #2684 curl text 21 Closing connection 0
2019-09-13 13:50:02 E #2684 downloader Error trace:
2019-09-13 13:50:02 E #2684 Thread [Main thread]->
2019-09-13 13:50:02 E #2684 SessMgr [initializeScript]->
2019-09-13 13:50:02 E #2684 creposi [setNextRepositoryToUse]->
2019-09-13 13:50:02 E #2684 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2019-09-13 13:50:02 E #2684 downloader Downloading file from https://****.nbg.l-h.de:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7} to C:\WINDOWS\TEMP\SiteStat.xml failed.
2019-09-13 13:50:02 I #2684 downloader calling system proxy client api.
2019-09-13 13:50:02 I #2684 downloader client api sync_get_system_proxy failed.
2019-09-13 13:50:02 I #2684 downloader Downloading file from https://****:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7} to C:\WINDOWS\TEMP\SiteStat.xml with timeout 18000
2019-09-13 13:50:02 I #2684 network URL(https://****:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7}) request, failed with curl error 7, Response 0, Connect code 0,
2019-09-13 13:50:02 I #2684 curl text 21 Closing connection 0
2019-09-13 13:50:02 E #2684 downloader Error trace:
2019-09-13 13:50:02 E #2684 Thread [Main thread]->
2019-09-13 13:50:02 E #2684 SessMgr [initializeScript]->
2019-09-13 13:50:02 E #2684 creposi [setNextRepositoryToUse]->
2019-09-13 13:50:02 E #2684 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2019-09-13 13:50:02 E #2684 downloader Downloading file from https://****:5443/Software/SiteStat.xml?hash={9eec2256-d61c-11e9-02e1-dfe4af0038e7} to C:\WINDOWS\TEMP\SiteStat.xml failed.
2019-09-13 13:50:02 I #2684 creposi Repository ePO_*** is not usable for the current update session.
2019-09-13 13:50:02 I #2684 creposi Trying the repository McAfeeHttp
2019-09-13 13:50:02 I #2684 creposi Checking for a valid license.
2019-09-13 13:50:02 I #2684 licmgr Downloading file from https://lc.mcafee.com:443/LicenseServer/LicenseWS.asmx/MLNodeUpdateCheck
2019-09-13 13:50:02 I #2684 network URL(https://lc.mcafee.com:443/LicenseServer/LicenseWS.asmx/MLNodeUpdateCheck) request, failed with curl error 7, Response 0, Connect code 0,
2019-09-13 13:50:02 I #2684 curl text 21 Closing connection 0
2019-09-13 13:50:02 E #2684 licmgr Error trace:
2019-09-13 13:50:02 E #2684 Thread [Main thread]->
2019-09-13 13:50:02 E #2684 SessMgr [initializeScript]->
2019-09-13 13:50:02 E #2684 creposi [setNextRepositoryToUse]->
2019-09-13 13:50:02 E #2684 licmgr Downloading file from https://lc.mcafee.com:443/LicenseServer/LicenseWS.asmx/MLNodeUpdateCheck failed.
2019-09-13 13:50:02 E #2684 creposi Error trace:
2019-09-13 13:50:02 E #2684 Thread [Main thread]->
2019-09-13 13:50:02 E #2684 SessMgr [initializeScript]->
2019-09-13 13:50:02 E #2684 creposi [setNextRepositoryToUse]->
2019-09-13 13:50:02 E #2684 creposi Download is allowed from the McAfee repositories but error condition found. Error code:-2. Error message:
2019-09-13 13:50:02 I #2684 downloader calling system proxy client api.
2019-09-13 13:50:02 I #2684 downloader client api sync_get_system_proxy failed.
2019-09-13 13:50:02 I #2684 downloader Downloading file from http://update.nai.com:80/Products/CommonUpdater/SiteStat.xml?hash={9ef522ca-d61c-11e9-08eb-dfe4af003...} to C:\WINDOWS\TEMP\SiteStat.xml with timeout 18000
2019-09-13 13:50:02 I #2684 network URL(http://update.nai.com:80/Products/CommonUpdater/SiteStat.xml?hash={9ef522ca-d61c-11e9-08eb-dfe4af003...}) request, failed with curl error 7, Response 0, Connect code 0,
2019-09-13 13:50:02 I #2684 curl text 21 Closing connection 0
2019-09-13 13:50:02 E #2684 downloader Error trace:
2019-09-13 13:50:02 E #2684 Thread [Main thread]->
2019-09-13 13:50:02 E #2684 SessMgr [initializeScript]->
2019-09-13 13:50:02 E #2684 creposi [setNextRepositoryToUse]->
2019-09-13 13:50:02 E #2684 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2019-09-13 13:50:02 E #2684 downloader Downloading file from http://update.nai.com:80/Products/CommonUpdater/SiteStat.xml?hash={9ef522ca-d61c-11e9-08eb-dfe4af003...} to C:\WINDOWS\TEMP\SiteStat.xml failed.
2019-09-13 13:50:02 I #2684 creposi Repository McAfeeHttp is not usable for the current update session.
2019-09-13 13:50:02 I #2684 downloader no relay found in the network.
2019-09-13 13:50:02 I #2684 ScrptMain McAfee Update Engine is exiting with return code: 1
2019-09-13 13:50:02 I #2684 SessMgr Unable to find any valid repository
2019-09-13 13:50:02 I #2684 MueEep Invoking events withEventId " 0" Severity " 0" Productid " EPOAGENT3000" Locale " 0407" UpdateType " N/A" UpdateError " 26" iUpdateState " 4" New Version " N/A" Date Time " N/A" Script Id" 15762" Custom Message " "
2019-09-13 13:50:02 I #2684 MueEep Updating session state to 4
2019-09-13 13:50:02 I #2684 MueEep Updating final session state to 4
2019-09-13 13:50:02 I #2684 MueEep Invoking EndUpdateDialog withTitle " Aktualisierung fehlgeschlagen" Message " Weitere Einzelheiten finden Sie im Aktualisierungsprotokoll." CountdownMessage " " CountdownValue" 0"
2019-09-13 13:50:02 I #2684 SessMgr Final session state is 4
2019-09-13 13:50:02 I #2684 mue Updater session state = <4>, Update session result = "FAILED".
2019-09-13 13:50:02 I #2684 mue Updater install <0> uninstall <0> update <0>
2019-09-13 13:50:02 I #2684 mue Check if any post update executable to run.
2019-09-13 13:50:02 I #2684 LpcConnMgr Stopping lpc connection manager
2019-09-13 13:50:02 I #2684 LpcConnMgr Cleaning up watchdog instance
2019-09-13 13:50:02 I #2684 WatchDog Stopping watchdog monitor
2019-09-13 13:50:02 I #2684 LpcConnMgr Done cleaning up watchdog instance
2019-09-13 13:50:02 I #2684 LpcConnMgr Triggering lpc unavailable
2019-09-13 13:50:02 I #2684 LpcConnMgr Invoking lpc revalidation on lpc unavailable
2019-09-13 13:50:02 I #2684 MsgPoll Setting stop to message poll thread
2019-09-13 13:50:02 I #2684 MsgPoll Unregistering client channel for message type 1496913389 extended id 474185642 client id 194086155
2019-09-13 13:50:02 I #2684 MsgQueue Aborting message queue operation
2019-09-13 13:50:02 I #11676 WinLpcChnl Shutdown event was signalled
2019-09-13 13:50:02 I #11676 MsgQueue No data available in message queue channel
2019-09-13 13:50:02 I #11676 MsgPoll stopping message queue poll thread
2019-09-13 13:50:02 I #2684 MsgQueue Cleaning up message queue
2019-09-13 13:50:02 I #2684 MfeLpcFactory Successfully released mfelpc objects
2019-09-13 13:50:02 I #2684 LPCDLLManager Successfully released LPC runtime mfelpc.dll
2019-09-13 13:50:07 I #2684 ma_client stopping ma client.
2019-09-13 13:50:07 I #5728 msgbus Unregistered for msgbus connectivity resync
2019-09-13 13:50:07 I #5728 msgbus Removed file watcher on broker config file <c:\programdata\mcafee\agent\msgbus\config.ini>
2019-09-13 13:50:07 I #2684 crypto Crypto logger released <01979920>
2019-09-13 13:50:07 I #2684 MueEep Deinitializing entry execution point
2019-09-13 13:50:07 I #2684 Thread Exit program</c:\programdata\mcafee\agent\msgbus\config.ini>

[chealey]

https://curl.haxx.se/libcurl/c/libcurl-errors.html

Da geht wohl etwas mit der Kommunikation schief. Verwenden Sie eine Proxy?

CURLE_COULDNT_CONNECT (7)
Failed to connect() to host or proxy.

[cheetah]

Hi Chaealey,

Nein, bei uns gibt es keinen Proxy.

Des ist es ja, was mich wundert.

Ich hatte auch schon in der VSE-Konsole umgestellt auf "keine Proxy", aber auch das hat nicht geholfen.

[vivs]

It is getting failed with the below error:

2019-09-13 13:50:02 I #2684 downloader Downloading file from http://update.nai.com:80/Products/CommonUpdater/SiteStat.xml?hash={9ef522ca-d61c-11e9-08eb-dfe4af003...} to C:\WINDOWS\TEMP\SiteStat.xml with timeout 18000
2019-09-13 13:50:02 I #2684 network URL(http://update.nai.com:80/Products/CommonUpdater/SiteStat.xml?hash={9ef522ca-d61c-11e9-08eb-dfe4af003...}) request, failed with curl error 7, Response 0, Connect code 0,

Curl Error 7 means 

CURLE_COULDNT_CONNECT (7)

Failed to connect to host or proxy

https://kc.mcafee.com/corporate/index?page=content&id=KB74939&actp=LIST_RECENT

Just wanted to confirm is there any Proxy/Firewall  available in the netwrok?

Can you go to the browser on that machine to this location and pull the sitestat.xml?

https://****.nbg.l-h.de:5443/Software/SiteStat.xml?

If yes, is the browser using any proxy?

Please try to restart the ePO Services and please do check whether the package is available in the Master Repository.

Was my reply helpful?
If you find this post useful, Please give it a Kudos! l Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

[cheetah]

Danke euch beiden! 

Da wir ja keinen Proxy nutzen, kann es ja nur noch etwas mit der Firewall sein.

Dieses werde ich dementsprechend Prüfen und das Ergebnis natürlich mitteilen.

Vielen Dank an dieser Stelle und ein schönes Wochenende.

[chealey]

Super, halten Sie uns bitte auf dem Laufenden 🙂

Ebenfalls ein schönes Wochenende.