cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Xfactor
Level 7
Report Inappropriate Content
Message 11 of 20

Re: AutoUpdate not working / no valid repository

KB94895 has been updated:

"Standalone Agents - Agents not managed by any ePO solution need to be manually remediated by uninstalling and reinstalling the agent. For instructions, see the first workaround below. We’re working on an easier solution to implement and this article will be updated when that solution is available."

Would be happy for a notification in this forum as soon as the solution is available.
Xfactor
Level 7
Report Inappropriate Content
Message 12 of 20

Re: AutoUpdate not working / no valid repository

Hi @Saif_f ,

I also found an error log file "UpdaterUI_MIC" stating the following.

Maybe this is helpful?

---

2021-09-23 07:45:58 I #5652 msgbus Received 366 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:45:58 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:45:58 I #5652 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
2021-09-23 07:45:58 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:45:58 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:45:58 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:45:59 I #5652 msgbus New connection on pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928> with status <0>, provider: 0123BA48
2021-09-23 07:46:00 I #5652 msgbus Received secure credentials for peer pipe handle=<940>, pid=<18128>.
2021-09-23 07:46:00 I #5652 msgbus uv timer data(012364B8)
2021-09-23 07:46:00 I #5652 msgbus
2021-09-23 07:46:00 I #5652 msgbus named pipe authentication started.
2021-09-23 07:46:00 I #5652 msgbus on_client_authenticate_cb callback called with status <0>.
2021-09-23 07:46:00 I #5652 msgbus named pipe connection accepted.
2021-09-23 07:46:00 I #5652 msgbus accept callback invoked pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928> with status <0>
2021-09-23 07:46:00 I #5652 msgbus Calling user callback on this new connection on pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928>
2021-09-23 07:46:00 I #5652 msgbus Adding new accepted connection object with pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8>
2021-09-23 07:46:00 I #5652 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> is added into connection manager
2021-09-23 07:46:00 I #5652 msgbus set consumer in named pipe connection
2021-09-23 07:46:00 I #5652 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> start receiving...
2021-09-23 07:46:00 I #5652 msgbus Received 332 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:46:00 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 msgbus Received 5 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8>
2021-09-23 07:46:00 I #5652 msgbus received peer process pid <18128>
2021-09-23 07:46:00 I #10092 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=1, MaxProgress = 0, Progress Message = Es wurde kein gültiges Repository gefunden.
2021-09-23 07:46:00 I #10092 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=1 MaxProgress = 0 Progress Message = Es wurde kein gültiges Repository gefunden.
2021-09-23 07:46:00 I #5652 msgbus Error retrieving auth info from db for pid = <18128>, rc=<14>
2021-09-23 07:46:00 I #5652 msgbus Failed getting additional auth information, rc = <14>
2021-09-23 07:46:00 I #5652 msgbus Sending pid <5612>
2021-09-23 07:46:00 I #5652 msgbus Sending data on connected name pipe
2021-09-23 07:46:00 E #5652 msgbus Failed to write data on pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8>
2021-09-23 07:46:00 E #5652 msgbus UV write failed - uv error <36> <broken pipe>
2021-09-23 07:46:00 I #5652 msgbus topic <ma.msgbus.peer_end_termination> reachability <0>
2021-09-23 07:46:00 I #5652 loop_worker scheduled an async work request, now has 1 pending work requests
2021-09-23 07:46:00 I #5652 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> in connection manager
2021-09-23 07:46:00 I #5652 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> found in connection manager
2021-09-23 07:46:00 I #5652 msgbus Removed named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> from connection manager
2021-09-23 07:46:00 I #5652 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> connection closed...
2021-09-23 07:46:00 I #5652 msgbus Received 320 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:46:00 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #5652 msgbus <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5612.0123B928_035B7EC8> pipe closed completely
2021-09-23 07:46:00 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.msgbus.peer_end_termination>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #5652 msgbus Clean up publisher data
2021-09-23 07:46:00 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 loop_worker loop worker successfully processed a message, still 0 more to go...
2021-09-23 07:46:00 I #5652 msgbus Received 313 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:46:00 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:46:00 I #10092 UiProviderAdaptor On Progress Callback EventType=ProgressFinished, ProgressStep=1, MaxProgress = 0, Progress Message = Fehler beim Aktualisieren.
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:46:00 I #10092 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=1 MaxProgress = 0 Progress Message = Fehler beim Aktualisieren.
2021-09-23 07:46:00 I #5652 msgbus Received 379 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:46:00 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 msgbus Received 368 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:46:00 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #5652 msgbus Received 833 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:46:00 I #22880 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:46:00 I #5652 msgbus Received topic <ma.topic.pubsub.custom_events>, matched <ma.*>
2021-09-23 07:46:00 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:46:00 I #22880 msgbus Subscriber now invoking handler...
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:46:00 I #13744 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=0 MaxProgress = 0 Progress Message =
2021-09-23 07:46:00 I #13744 UiProviderAdaptor <<<<<EndUpdateDialog Title=Aktualisierung fehlgeschlagenEnd Message: Weitere Einzelheiten finden Sie im Aktualisierungsprotokoll. CountDownMessage : CountDownValue : 0
2021-09-23 07:46:00 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus Received 1134 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.task.execute>, matched <ma.*>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus Received 294 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
2021-09-23 07:48:06 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
2021-09-23 07:48:06 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus Received 273 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
2021-09-23 07:48:06 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus Received 321 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.policy.notification>, matched <ma.*>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #10092 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus Received 292 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy> option <0x10002> set, return value is <0>
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy>, sync send call
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
2021-09-23 07:48:06 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
2021-09-23 07:48:06 I #10092 msgbus Messagebus Request object Created
2021-09-23 07:48:06 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #10092 loop_worker scheduled an async work request, now has 1 pending work requests
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy> succeessfully submitted request to loop worker
2021-09-23 07:48:06 I #5652 msgbus Received 300 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy>, submitted loop worker request for sync send
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy>, waiting for loop worker sync request acknowledgement...
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
2021-09-23 07:48:06 I #22880 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #22880 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus uv timer data(0354D190)
2021-09-23 07:48:06 I #5652 msgbus
2021-09-23 07:48:06 I #5652 msgbus <ma.service.policy> service found in router
2021-09-23 07:48:06 I #5652 msgbus Service <ma.service.policy> found in local search and status of ep lookup is <2>
2021-09-23 07:48:06 I #5652 msgbus Calling lookup callback in async way with status <0> from ep lookup <0123E2A8>
2021-09-23 07:48:06 I #5652 msgbus uv timer data(0352D848)
2021-09-23 07:48:06 I #5652 msgbus
2021-09-23 07:48:06 I #5652 msgbus local broker look up succeeded for service <ma.service.policy> ans started timer with timeout <20000> for request <0354D190>
2021-09-23 07:48:06 I #5652 msgbus Endpoint <ma.service.policy> request successfully initiated
2021-09-23 07:48:06 I #5652 loop_worker loop worker successfully processed a message, still 0 more to go...
2021-09-23 07:48:06 I #5652 msgbus Message bus request <0354D190> lookup cb is invoked with status <0> from ep lookup <0123E2A8>
2021-09-23 07:48:06 I #5652 msgbus Sending message to router - correlation id <642> ephemeral name buffer <ma.internal.request.000015EC.642>
2021-09-23 07:48:06 I #5652 msgbus Adding received message into queue
2021-09-23 07:48:06 I #5652 msgbus Sending data on connected name pipe
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus Received 650 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2268.0000000001BD4C30>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
2021-09-23 07:48:06 I #5652 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
2021-09-23 07:48:06 I #13744 msgbus Subscriber now invoking handler...
2021-09-23 07:48:06 I #5652 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2252.0000000000E5C690> with status <0>
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #5652 msgbus Received 3118 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2252.0000000000E5C690>
2021-09-23 07:48:06 I #5652 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
2021-09-23 07:48:06 I #5652 msgbus Recevied expected response to message bus request
2021-09-23 07:48:06 I #5652 msgbus Invoking user callback in I/O thread
2021-09-23 07:48:06 I #5652 msgbus Endpoint <ma.service.policy>, sync send callback invoked
2021-09-23 07:48:06 I #5652 msgbus ep lookup <0123E2A8> stop, connection status recevied <No> ref count <3>
2021-09-23 07:48:06 I #10092 msgbus message bus request Released
2021-09-23 07:48:06 I #5652 msgbus Request Object Closes
2021-09-23 07:48:06 I #10092 msgbus Endpoint <ma.service.policy> release
2021-09-23 07:48:06 I #5652 msgbus message bus request Released
2021-09-23 07:48:06 I #5652 msgbus Messagebus Request object Destroys
2021-09-23 07:48:06 I #10092 UpdaterUIModule Enforcing UI policies
2021-09-23 07:48:06 I #5652 msgbus Endpoint <ma.service.policy> release
2021-09-23 07:48:06 I #10092 UpdaterUIModule AgentMode = 0
2021-09-23 07:48:06 I #5652 msgbus Endpoint <ma.service.policy> destroys
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber
2021-09-23 07:48:06 I #10092 UpdaterUIModule Show Agent UI: 1
2021-09-23 07:48:06 I #10092 UpdaterUIModule Allow Security Update: 1
2021-09-23 07:48:06 I #10092 UpdaterUIModule Language from policy : 0000
2021-09-23 07:48:06 I #10092 UpdaterUI Allow Update Security option State = 1
2021-09-23 07:48:06 I #5652 msgbus After Worker callback is Invoked in Subscriber

DG1
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 13 of 20

Re: AutoUpdate not working / no valid repository

Hi @Xfactor,

Also, do check the below.

https://kc.mcafee.com/corporate/index?page=content&id=KB52680

 

 

Was my reply helpful?
If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a solution" if this reply resolves your query!
Thanks and regards,
Deepak G
McAfee Technical Support
Xfactor
Level 7
Report Inappropriate Content
Message 14 of 20

Re: AutoUpdate not working / no valid repository

alright, I will give it a try...
Xfactor
Level 7
Report Inappropriate Content
Message 15 of 20

Re: AutoUpdate not working / no valid repository

Hi,

a) in the schedule option I have deselected randomization, the other parameters were already correct.

-> AutoUpdate still does not work.

b) in regedit I do not have the registry key HKLM\SOFTWARE\McAfee\DesktopProtection\Tasks\{21221C11-A06D-4558-B833-98E8C7F6C4D2}

My regedit tree struture is attached.

Kind regards!

DG1
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 16 of 20

Re: AutoUpdate not working / no valid repository

Hi @Xfactor,

In that case, you might have to raise a service request with our support team to check the issue.

 

Was my reply helpful?
If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a solution" if this reply resolves your query!
Thanks and regards,
Deepak G
McAfee Technical Support
Xfactor
Level 7
Report Inappropriate Content
Message 17 of 20

Re: AutoUpdate not working / no valid repository

actually the McAfee research team is currently investigation the issue, but apparently there is no solution yet or workaround for McAfee VirusScan Enterprise (VSE) 8.8:

https://kc.mcafee.com/corporate/index?page=content&id=KB94895
Xfactor
Level 7
Report Inappropriate Content
Message 18 of 20

Re: AutoUpdate not working / no valid repository

Hi @DG1,
in addition to the community forum I would like to sign-up for access to the ServicePortal. During the registering process the "Grant-Nummer" is being requested. Where can I find that?

Best regards!
markgarza
Level 10
Report Inappropriate Content
Message 19 of 20

Re: AutoUpdate not working / no valid repository

I am having this issue with clients that have VSE 8.8 installed but no McAfee agent installed, and it had been working fine up until recently going out to McAfee servers to receive DAT updates. Is the KB94895 still relevant?

AdithyanT
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 20 of 20

Re: AutoUpdate not working / no valid repository

Hi @markgarza,

Standalone endpoints running ENS or VSE will still include the core component of Agent Framework that helps them perform the update tasks. Hence, the KBA should still remain relevant.

However, May I know how you confirmed that the issue the same as the one described here? May I know if the errors were exactly the same as the one described in the KBA?

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

Thanks and regards,
Adithyan T
You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community