I have installed Exchange 2013CU7 on Server 2012 R2 in a VM.  I have removed and reinstalled several times and saw this error on each installation.  It happens a few times a day, somewhat randomly.  As far as I can tell nothing is impacted in terms of server function.

Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          12/19/2014 1:04:47 AM
Event ID:      8
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      myserver.mydomain.local
Description:
(PID 4064, Thread 136) Task Get-HealthReport throwing unhandled exception: System.ArgumentException: sessionState
   at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(ISessionState sessionState)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlersImpl(Task task)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task)
   at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b__4()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeNonRetryableFunc(Action func, Boolean terminatePipelineIfFailed).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange CmdletLogs" />
    <EventID Qualifiers="49152">8</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-19T08:04:47.000000000Z" />
    <EventRecordID>347</EventRecordID>
    <Channel>MSExchange Management</Channel>
    <Computer>myserver.mydomain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>4064</Data>
    <Data>136</Data>
    <Data>Get-HealthReport</Data>
    <Data>Get-HealthReport</Data>
    <Data>System.ArgumentException: sessionState
   at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(ISessionState sessionState)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlersImpl(Task task)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task)
   at Microsoft.Exchange.Configuration.Tasks.Task.&lt;BeginProcessing&gt;b__4()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeNonRetryableFunc(Action func, Boolean terminatePipelineIfFailed)</Data>
  </EventData>
</Event>

Hello,

Thank you for your post. This is a quick note to let you know that we are performing research on this issue.

If you have feedback for TechNet Subscriber Support, contact tnsfl@mic

Hi Mnm,

Please check if there is any error when running Get-HealthReport in EMS. If there is no error, please feel free to ingore this event as no Exchange function is impacted.

Besides, you may check if there is any protection software or backup software installed on the Exchange server. If yes, consider to temporarily stop using these softwares. And check if there is any schedule task would peforman this command. Then see if there is any update.

Thanks,

Jessie

• Marked as answer by Richard KuaiModerator Tuesday, January 13, 2015 2:50 AM
• Unmarked as answer by MnM Show Wednesday, January 14, 2015 10:20 PM

Hi MnM,

Do you need further help about this issue?

Thanks,

Jessie

Hi Mnm,

Please check if there is any error when running Get-HealthReport in EMS. If there is no error, please feel free to ingore this event as no Exchange function is impacted.

Besides, you may check if there is any protection software or backup software installed on the Exchange server. If yes, consider to temporarily stop using these softwares. And check if there is any schedule task would peforman this command. Then see if there is any update.

Thanks,

Jessie

Nothing besides exchange and associated MS app requirements are installed on the server.  Get-HealthReport -Identity myserver works fine from EMS.  Still get this error in the logs several times a day.

Hi Mnm,

Please check if there is any error when running Get-HealthReport in EMS. If there is no error, please feel free to ingore this event as no Exchange function is impacted.

Same here. Single Server running CU8, no third party software, no PS tasks;

Running Get-Healthreport in EMS is fine.

Having ECP\EacCtpMonitor unhealthy with a transition matching the timestamp in the eventlog,

so: yes, there *are* functional impacts.

Manually retriggering the probe brings back ECP back to healthy:

Invoke-MonitoringProbe -Identity ECP\EacSelfTestProbe -server myserver
WARNING: Please specify value forSslValidationOptions

• Edited by s_run 1 hour 47 minutes ago new information

Hi Mnm,

Please check if there is any error when running Get-HealthReport in EMS. If there is no error, please feel free to ingore this event as no Exchange function is impacted.

Same here. Single Server running CU8, no third party software, no PS tasks;

Running Get-Healthreport in EMS is fine.

Having ECP\EacCtpMonitor unhealthy with a transition matching the timestamp in the eventlog,

so: yes, there *are* functional impacts.

Manually retriggering the probe brings back ECP back to healthy:

Invoke-MonitoringProbe -Identity ECP\EacSelfTestProbe -server myserver
WARNING: Please specify value forSslValidationOptions

• Edited by s_run Friday, June 26, 2015 5:39 AM new information