Unknown Error - MSExchange Configuration Core - Event ID 2

Hi there,

We are getting the following event log on our Exchange 2013 server, but cannot identify what the cause or issue being reported.

Event ID: 2 
Event Source: MSExchange Configuration Core 
Event Type: Error 
Event Description: Log Name:      Application
Source:        MSExchange Configuration Core
Date:          12/11/2014 9:55:23 AM
Event ID:      2
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ************
Description:
The description for Event ID 2 from source MSExchange Configuration Core cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer the display information had to be saved with the event.

The following information was included with the event: 

12048
w3wp.exe
Exception from CmdletLogger.AsyncCommit : System.ArgumentException: activityScope is null.
   at Microsoft.Exchange.Diagnostics.CmdletInfra.CmdletLogger.AsyncCommit(Guid cmdletUniqueId Boolean forceSync)
   at Microsoft.Exchange.Configuration.Tasks.LoggingModule.CommitLog(String loggingStep)

the message resource is present but the message is not found in the string/message table

Anyone else having this issue, and what fixes/workarounds are there to stop it from occurring? Thanks. 

February 19th, 2015 8:07am

Hi,

Please check if you have Antivirus running in Exchange server. If there is Antivirus installed, please make sure you set the antivirus exclusions properly.

A related article for your reference.

https://technet.microsoft.com/en-us/library/bb332342%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Free Windows Admin Tool Kit Click here and download it now
February 20th, 2015 8:33am

Hi there,

We don't have AV installed on our Exchange servers.

Any other possible causes for this error?

February 20th, 2015 8:57am

We have had the same issue on two clean installs of Exchange 2013, one CU6 and one CU7 (both on VMWare ESXi 5.5).

No functional issues, but this message in the application log 5000 times every 24 hours.

Opened a case with MS support, but they were unwilling to help! Since there were no functional issues, this was a case for root cause analysis, which requires premium support, which requires you to shell out another 25 grand a year ...

I find it very strange that we have this issue on both of our clean installs, but there's hardly anything on the internet about this error.


  • Edited by Wouter Ooms Wednesday, February 25, 2015 12:29 PM
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2015 7:09am

We have had the same issue on two clean installs of Exchange 2013, one CU6 and one CU7 (both on VMWare ESXi 5.5).

No functional issues, but this message in the application log 5000 times every 24 hours.

Opened a case with MS support, but they were unwilling to help! Since there were no functional issues, this was a case for root cause analysis, which requires premium support, which requires you to shell out another 25 grand a year ...

I find it very strange that we have this issue on both of our clean installs, but there's hardly anything on the internet about this error.


  • Edited by Wouter Ooms Wednesday, February 25, 2015 12:29 PM
February 25th, 2015 10:09am

This is what I tried so far:

                - re-created all Health Mailboxes

                - set an unlimited throttling policy for all Health Mailboxes

                - moved all System Mailboxes to an Exchange 2013 server

                - disabled anti-spam

All this without any result.

               

Then I tried a complete re-install:

                - completely removed Exchange, IIS & WAS from the server

                - re-checked all prerequisites

                - re-applied schema/AD/domain prep

                - checked for any errors/updates

                - re-installed Exchange

Immediately after the install, the same errors start appearing in the application log:

Log Name:      Application

Source:        MSExchange Configuration Core

Date:          26/02/2015 14:57:26

Event ID:      2

Task Category: (1)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      mp-exch13.Jaga.local

Description:

The description for Event ID 2 from source MSExchange Configuration Core cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

3240

w3wp.exe

Exception from CmdletLogger.AsyncCommit : System.ArgumentException: activityScope is null.

   at Microsoft.Exchange.Diagnostics.CmdletInfra.CmdletLogger.AsyncCommit(Guid cmdletUniqueId, Boolean forceSync)

   at Microsoft.Exchange.Configuration.Tasks.LoggingModule.CommitLog(String loggingStep)

the message resource is present but the message is not found in the string/message table

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Configuration Core" />

    <EventID Qualifiers="49152">2</EventID>

    <Level>2</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-02-26T13:57:26.000000000Z" />

    <EventRecordID>91653</EventRecordID>

    <Channel>Application</Channel>

    <Computer>mp-exch13.Jaga.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>3240</Data>

    <Data>w3wp.exe</Data>

    <Data>Exception from CmdletLogger.AsyncCommit : System.ArgumentException: activityScope is null.

   at Microsoft.Exchange.Diagnostics.CmdletInfra.CmdletLogger.AsyncCommit(Guid cmdletUniqueId, Boolean forceSync)

   at Microsoft.Exchange.Configuration.Tasks.LoggingModule.CommitLog(String loggingStep)</Data>

  </EventData>

</Event>


  • Edited by Wouter Ooms Thursday, February 26, 2015 2:02 PM
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 2:01pm

This is what I tried so far:

                - re-created all Health Mailboxes

                - set an unlimited throttling policy for all Health Mailboxes

                - moved all System Mailboxes to an Exchange 2013 server

                - disabled anti-spam

All this without any result.

               

Then I tried a complete re-install:

                - completely removed Exchange, IIS & WAS from the server

                - re-checked all prerequisites

                - re-applied schema/AD/domain prep

                - checked for any errors/updates

                - re-installed Exchange

Immediately after the install, the same errors start appearing in the application log:

Log Name:      Application

Source:        MSExchange Configuration Core

Date:          26/02/2015 14:57:26

Event ID:      2

Task Category: (1)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      mp-exch13.Jaga.local

Description:

The description for Event ID 2 from source MSExchange Configuration Core cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

3240

w3wp.exe

Exception from CmdletLogger.AsyncCommit : System.ArgumentException: activityScope is null.

   at Microsoft.Exchange.Diagnostics.CmdletInfra.CmdletLogger.AsyncCommit(Guid cmdletUniqueId, Boolean forceSync)

   at Microsoft.Exchange.Configuration.Tasks.LoggingModule.CommitLog(String loggingStep)

the message resource is present but the message is not found in the string/message table

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Configuration Core" />

    <EventID Qualifiers="49152">2</EventID>

    <Level>2</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-02-26T13:57:26.000000000Z" />

    <EventRecordID>91653</EventRecordID>

    <Channel>Application</Channel>

    <Computer>mp-exch13.Jaga.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>3240</Data>

    <Data>w3wp.exe</Data>

    <Data>Exception from CmdletLogger.AsyncCommit : System.ArgumentException: activityScope is null.

   at Microsoft.Exchange.Diagnostics.CmdletInfra.CmdletLogger.AsyncCommit(Guid cmdletUniqueId, Boolean forceSync)

   at Microsoft.Exchange.Configuration.Tasks.LoggingModule.CommitLog(String loggingStep)</Data>

  </EventData>

</Event>


  • Edited by Wouter Ooms Thursday, February 26, 2015 2:02 PM
February 26th, 2015 5:01pm

Seems to be a bad bit of code in Exchange 2013 from what I gather. 

For those having the issues, is it just on VMware hosts, or on other VM platforms as well? 

Free Windows Admin Tool Kit Click here and download it now
February 27th, 2015 2:56am

Wouter,

is the message showing up at precisely at 3 - 4 min interval?

Can you set MSExchange Web Services\Core diagnostic level to expert? an check what additional info you get in event log

Set-EventLogLevel -Identity "Yourexchange\MSExchange Web Services\Core " -Level Expert

Also you can install and run BPA to see if it detects any issues in your environment

https://justaucguy.wordpress.com/2014/02/28/exchange-2013-service-pack-1-best-practices-analyzer-updated/


  • Edited by net_tech 20 hours 14 minutes ago
February 27th, 2015 9:43am

Wouter,

is the message showing up at precisely at 3 - 4 min interval?

Can you set MSExchange Web Services\Core diagnostic level to expert? an check what additional info you get in event log

Set-EventLogLevel -Identity "Yourexchange\MSExchange Web Services\Core " -Level Expert

Also you can install and run BPA to see if it detects any issues in your environment

https://justaucguy.wordpress.com/2014/02/28/exchange-2013-service-pack-1-best-practices-analyzer-updated/


  • Edited by net_tech Friday, February 27, 2015 3:17 PM
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2015 2:44pm

Wouter,

is the message showing up at precisely at 3 - 4 min interval?

Can you set MSExchange Web Services\Core diagnostic level to expert? an check what additional info you get in event log

Set-EventLogLevel -Identity "Yourexchange\MSExchange Web Services\Core " -Level Expert

Also you can install and run BPA to see if it detects any issues in your environment

https://justaucguy.wordpress.com/2014/02/28/exchange-2013-service-pack-1-best-practices-analyzer-updated/


  • Edited by net_tech Friday, February 27, 2015 3:17 PM
February 27th, 2015 2:44pm

No precise intervals. I got 4647 of these events in the last 24 hours, that's about 3 to 4 errors each minute! They keep coming at such a rate that my application log only holds about 24hrs of data.

I have set the logging level as requested.

I installed the BPA and ran a scan. This gave me 9 errors and 21 warnings! I'll start by trying to get these sorted.

Will update this thread with the results.

Free Windows Admin Tool Kit Click here and download it now
March 2nd, 2015 7:35pm

I was able to fix some minor issues, but most of these errors are beyond me.

They seem to be related to the new "Managed Avalibility" feature:

I have "Check server health entry" for Mapi.Submit.Monitor, OutlookRpcSelfTestMonitor, OutlookRpcDeepTestMonitor & RpsDeepTestPSProxyMonitor.

"Check state of server component" for ForwardSyncDaemon & ProvisioningRps.

"Check report of health set" for MailboxTransport, RPS & Outlook.Protocol. 

Any idea where to start troubleshooting?

March 3rd, 2015 2:21pm

You would want to start looking at the logs.

Do you want to start a new thread since the discovered problem is not the issue you originally posted about?

Please post the version of the OS and Exchange CU level, I would like to see the result of

Get-WindowsFeature | Where-Object {$_.InstallState -eq "Installed"}

and have it compared to the requirements in the link below

https://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx

Thanks

  • Edited by net_tech Tuesday, March 03, 2015 3:15 PM
Free Windows Admin Tool Kit Click here and download it now
March 3rd, 2015 2:54pm

You would want to start looking at the logs.

Do you want to start a new thread since the discovered problem is not the issue you originally posted about?

Please post the version of the OS and Exchange CU level, I would like to see the result of

Get-WindowsFeature | Where-Object {$_.InstallState -eq "Installed"}

and have it compared to the requirements in the link below

https://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx

Thanks

  • Edited by net_tech Tuesday, March 03, 2015 3:15 PM
March 3rd, 2015 2:54pm

I started a new thread for the Managed Availibity issues under the title "Managed Availibility errors in clean install of CU7". I would post the link, but I need to verify my account first.

Is there anything more we can do about the original MSExchange Configuration Core errors? The expert logs have been running for some days now.


  • Edited by Wouter Ooms Wednesday, March 04, 2015 10:40 AM
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2015 10:33am

I started a new thread for the Managed Availibity issues under the title "Managed Availability errors in clean install of CU7".

Is there anything more we can do about the original MSExchange Configuration Core errors? The expert logs have been running for some days now.




March 4th, 2015 10:33am

I started a new thread for the Managed Availibity issues under the title "Managed Availability errors in clean install of CU7".

Is there anything more we can do about the original MSExchange Configuration Core errors? The expert logs have been running for some days now.




  • Edited by Wouter Ooms Friday, March 13, 2015 12:12 PM
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2015 10:33am

I started a new thread for the Managed Availibity issues under the title "Managed Availability errors in clean install of CU7".

Is there anything more we can do about the original MSExchange Configuration Core errors? The expert logs have been running for some days now.




  • Edited by Wouter Ooms Friday, March 13, 2015 12:12 PM
March 4th, 2015 10:33am

I succeeded in getting rid of the errors on my test server. I think it was activating IPv6 and rebooting that did the trick! Although it is not mentioned anywhere in the prerequisites, apparently all kinds of strange things can start happening on Exchange 2013 with IPv6 disabled (search for "Once again, Unchecking IPv6 on a NIC Breaks Exchange 2013").

Strangely enough, this did NOT fix the issue on my first 2013 server. But I'm afraid I have no time to wonder why, I'm moving forward with the server without the errors!

Thanks for all help and suggestions and good luck to anyone still experiencing this issue.

Free Windows Admin Tool Kit Click here and download it now
March 5th, 2015 2:31am

I succeeded in getting rid of the errors on my test server. I think it was activating IPv6 and rebooting that did the trick! Although it is not mentioned anywhere in the prerequisites, apparently all kinds of strange things can start happening on Exchange 2013 with IPv6 disabled (search for "Once again, Unchecking IPv6 on a NIC Breaks Exchange 2013").

Strangely enough, this did NOT fix the issue on my first 2013 server. But I'm afraid I have no time to wonder why, I'm moving forward with the server without the errors!

Thanks for all help and suggestions and good luck to anyone still experiencing this issue.

March 5th, 2015 7:30am

I succeeded in getting rid of the errors on my test server. I think it was activating IPv6 and rebooting that did the trick! Although it is not mentioned anywhere in the prerequisites, apparently all kinds of strange things can start happening on Exchange 2013 with IPv6 disabled (search for "Once again, Unchecking IPv6 on a NIC Breaks Exchange 2013").

Strangely enough, this did NOT fix the issue on my first 2013 server. But I'm afraid I have no time to wonder why, I'm moving forward with the server without the errors!

Thanks for all help and suggestions and good luck to anyone still experiencing this issue.

Free Windows Admin Tool Kit Click here and download it now
March 5th, 2015 7:30am

I am afraid I was too early in celebrating, after a while, the errors returned ...

Since I suspected I was on the right track with the IPv6 issue, I tried a completely new clean install, this time with IPv6 enabled. Alas, same issue: server installs without any issues, but after a little while, the unknown errors start appearing again.

So, still no solution and the issue is 100% repeatable with 10 exchange installs and counting...

March 13th, 2015 8:12am

Final solution for this issue was NOT to install from CU6 or CU7, but from the SP1 release.

I am not sure if upgrading to CU6/7 will bring back my issues, but for now I'm hapopy running an error-free SP1.

  • Proposed as answer by Wouter Ooms 18 hours 38 minutes ago
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 8:47am

Final solution for this issue was NOT to install from CU6 or CU7, but from the SP1 release.

I am not sure if upgrading to CU6/7 will bring back my issues, but for now I'm hapopy running an error-free SP1.

  • Proposed as answer by Wouter Ooms Tuesday, March 31, 2015 12:46 PM
March 31st, 2015 12:46pm

Have 10 of These per day at Exchange 2013CU8 running on HyperV Virtual Machine.
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 7:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics