Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 10
Report Inappropriate Content
Message 1 of 2

MSMS Event 6060 not parsed

The Security for Microsoft SharePoint 3.5 events, mainly Event ID 6060 are not parsed/processed when they are passed to the ePolicy Orchestrator (ePO) server. 6060 = PortalShield event statistics. Events are sitting in the DB\Events\Debug folder on the ePO server and will not parse. I tried to parse them but that didn't work. The correct MSMS Reports 3.5.1489.102 extension has been installed since 2018. Should I remove the extension and re-install the extension?

This KB article states this issue was resolved, but not for us.


1 Reply
Level 10
Report Inappropriate Content
Message 2 of 2

Re: MSMS Event 6060 not parsed

I'm just getting back to this issue. No one responded. I'm going to proceed with opening up a case with McAfee Technical support.

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