Event ID 7022
Nov17

Event ID 7022

KB ID 0000138  Problem Event ID 7022 The McAfee Framework Service service hung on starting. The Framework service starts before the network is up. Solution 1. Start > run > Regedit {enter}. 2. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMcAfeeFramework. 3. In the right hand window locate DependOnService > Double click it. 4. Add the following to the bottom of the list, “Netman” without the quotes....

Read More
Event ID 7001
Nov17

Event ID 7001

KB ID 0000137  Problem Event ID 7001 The McAfee ePolicy Orchestrator 3.5.0 Server service depends on the McAfee ePolicy Orchestrator 3.5.0 Event Parser Service which failed to start because of the following error: The operation completed successfully. The domain admin password has been changed and ePO is using the old one. Solution 1. Start > run > services.msc 2. Locate the following three services. i. MacAfee ePolicy...

Read More
Event ID 7000
Nov17

Event ID 7000

KB ID 0000136  Problem Event ID 7000 The Network Load Balancing service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Even when Network Lo aad Balancing (NLB) is not currently installed, some NLB registry keys may be present in the registry. Microsoft has identified this as a problem in Windows 2000 Advanced server. The...

Read More
Event ID 5719
Nov17

Event ID 5719

KB ID 0000712  Problem You see the following error in your event log (seen here in the system log on a domain controller). Log Name: System Source: NETLOGON Date: 15/11/2012 06:00:35 Event ID: 5719 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Servername.Domain-Name.com Description: This computer was not able to set up a secure session with a domain controller in domain (domain-name) due to the following:...

Read More
Event ID 5008
Nov17

Event ID 5008

KB ID 0000269  Problem Event ID 5008 The message tracking log file C:Program FilesExchsrvr{server name}{log number}.log was deleted. Not really an error, you are seeing this because message tracking is enabled but you have set message tracking to delete logs after x number of days.   Solution You can either disable message tracking, or change the amount of days logs are held for, or stop it deleting logs all together (Note: logs...

Read More