| Event ID 7036: Der Dienst "McAfee McShield" befindet sich jetzt im Status "Angehalten" |
|
|
|
Fehler im System Ereignisprotokoll: Der Dienst "McAfee McShield" befindet sich jetzt im Status "Angehalten"
Quelle: Service Control Manager Der Dienst "McAfee McShield" befindet sich jetzt im Status "Angehalten" Der Dienst "McAfee McShield befindet sich jetzt im Status "Ausgeführt"
ERROR: Event ID: 7036, The McAfee McShield service has entered the or state (after applying VSE 8.5i Patch 2 or later)
Diese Meldung tritt auf, nachdem Sie VSE 8.5i Patch 2 oder höher angewendet haben.
McAfee VirusScan Enterprise 8.5i
McAfee VirusScan Enterprise 8.5i (Patch 2 and 3)
Microsoft Windows
System Event log is populated with multiple entries for Event ID 7036 after installing VirusScan Enterprise 8.5i. Patch 2 or later:
VirusScan Enterprise 8.5i. Patch 2 or later was installed on the computer.
This event is informational only, and does not indicate an issue with the product. The presence of the event indicates that Service Control Manager has noted a change in state of the McShield service, such as the service entering the paused or running state.
This change in behavior was introduced to better synchronize the scanning activity of the McShield service with modification or enforcement of scanning configuration settings, where prior to the update in Patch 2 or later a rare timing issue could result in termination of the McShield service.
Event Properties would show for running state
Event Properties would show for paused state
This issue was resolved with HotFix 370722 which is attached to this KnowledgeBase article. In addition, both ePolicy Orchestrator (ePO) server(s) and client(s) must be restarted for this HotFix to take effect, because the ePO Server may still have events queued that need to be removed.
NOTE: An issue was found with the previously attached HotFix 370721, which is no longer available. With the HotFix installed the property information for the Patch version was no longer reported. HotFix 370722 will also fix the reporting issue.
This article was previously published under KnowledgeBase article 613548.
|




