I have disabled the FEP.Maintenance.Workitem check in FEPActiveMonitoringContext.xml on one of my EX2013 mailbox servers, however, I keep getting the following monitoring maintenance log error;

System.Exception: The following definitions were not created successfully:FEP.Maintenance.Workitem: An item with the same primary key 37 already exists in the table. Existing definition name: FEP.Maintenance.Workitem. New definition name: FEP.Maintenance.Workitem

Does anybody know how to fix this?

I noticed the "false" setting isn't taking effect and it keeps trying to find the Forefront executables;

The error message from the last result is:System.InvalidOperationException: Service MsMpSvc was not found on computer '.'. ---> System.ComponentModel.Win32Exception: The specified service does not exist as an installed service

Cheers.

Hi Matthew,

Do you mean you are using SCOM monitor Exchange? It seems like this is an Forefront related issue, if that is the case, it is suggested to post in the Forefront foru.

Hope the link below can be helpful:

Exchange 2013 Managed Availability HealthSet Troubleshooting

http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx

Regards,

Yan Li

Hi Yan, I think I worked with you a few years back on a SCOM premier support case.. Anywho..

I already followed that article, in particular the disable FEP disable. We don't use forefront on exchange.

Three other exchange servers had the config change, and they no longer monitor FEP. Any ideas? And yes, we are using SCOM for exchange 2013.

• Edited by Matthew Cosentino Thursday, February 19, 2015 10:10 AM

Hi,

Do you recieve alert in SCOM console? Where did you recieve those errors?

Will you please go through the below thread and follow it to change your FEPActiveMonitoringContext.xml:

https://social.technet.microsoft.com/Forums/exchange/en-US/92e7d044-99c4-4b9e-8798-8d4964f4917b/healthset-antimalware-is-checking-fep-which-is-not-installed?forum=exchangesvradmin

Regards,

Yan Li

Hey Yan,

I receive both those errors in the SCOM console, and the Exchange Monitoring log.

Have already changed the .XML before hand - like the other 3 Exchange 15 servers with the same error.

Hi Yan, I've worked it out.

There's a second value that isn't blogged about - only in that post is it mentioned.

FEPServiceRunningEnabled="false"

I fixed that and the error went away straight away.

Thanks for your help.

• Marked as answer by Yan Li_Microsoft contingent staff, Moderator Saturday, February 21, 2015 3:01 AM
• Edited by Matthew Cosentino Saturday, February 21, 2015 3:54 AM

Hello Yan, sorry to bother you again but the error as come back again;

Maintenance workitem "FEP.Maintenance.Workitem" (ID: 37) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause monitoring gap and should be investigated.

The error message from the last result is:

System.InvalidOperationException: Service MsMpSvc was not found on computer '.'. ---> System.ComponentModel.Win32Exception: The specified service does not exist as an installed service

This log is just after the following log;

Maintenance workitem "XmlDefinitionReaderWorkItem" (ID: 13) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause monitoring gap and should be investigated.

The error message from the last result is:

System.Exception: The following definitions were not created successfully:

FEP.Maintenance.Workitem: An item with the same primary key 37 already exists in the table. Existing definition name: FEP.Maintenance.Workitem. New definition name: FEP.Maintenance.Workitem

Do you know what the second error is?

Cheers.