cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

McAfee ENS Update to 10.7 Hanging up and Stalling out

Jump to solution
Updating all machines from 10.6.1 to 10.7.0 has been resulting in a one of three outcomes. Sometimes it succeeds, but more often it fails when updating the McAfee Common component with the McAFee_Common_VSCore_Install_All_########.log stating: MMS Service mfevtp: [##:##:##:###] - SERVICE_START_PENDING. After this the corresponding .etl file begins growing non-stop until the task times out (I've had it reach up to 250MB in size with nothing else ever happening). The other possible outcome is during the install of Common the McAfee_Common_Bootstrapper gets to the point of "Modifying DB from Common Bootrapper" and then begins spitting out line after line of "Database could not be opened. Sleeping for 1 second." This continues until the task time runs out too, and will give a 1603 error at the last second and say it failed. Has anyone else been seeing these kinds of issues with the 10.7 update or know of a resolution to fix it aside from having to uninstall and re-install ENS on every troublesome endpoint?
1 Solution

Accepted Solutions
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: McAfee ENS Update to 10.7 Hanging up and Stalling out

Jump to solution

Hi @User74296424 

Not a known issue with 10.7 as such. Would need a deep analysis.

Can you please share McAfeeLogs folder from one of the machine where upgrade failed? You can look into C:\windows\Temp\McAfeeLogs folder if did the upgrade from EPO or %temp% location if did locally. 

Also I would suggest to open a SR for the same. Please IM me the logs.

View solution in original post

1 Reply
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: McAfee ENS Update to 10.7 Hanging up and Stalling out

Jump to solution

Hi @User74296424 

Not a known issue with 10.7 as such. Would need a deep analysis.

Can you please share McAfeeLogs folder from one of the machine where upgrade failed? You can look into C:\windows\Temp\McAfeeLogs folder if did the upgrade from EPO or %temp% location if did locally. 

Also I would suggest to open a SR for the same. Please IM me the logs.

View solution in original post

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