Tuesday, May 24, 2016

MSExchangeDiagnostics Crashing


After running through one of my newly built Exchange 2016 CU1 Servers, I noticed I had a few errors within the event viewer as shown below.

The description for Event ID 1007 from source MSExchangeDiagnostics 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:

System.ArgumentException: Value does not fall within the expected range.
at PlaLibrary.DataCollectorSetClass.start(Boolean Synchronous)
at Microsoft.Exchange.Diagnostics.PerformanceLogger.PerformanceLogSet.StartLog(Boolean synchronous)
at Microsoft.Exchange.Diagnostics.PerformanceLogger.PerformanceLogMonitor.CheckPerflogStatus()
ExchangeDiagnosticsPerformanceLog

The handle is invalid

The description for Event ID 4999 from source MSExchange Common 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:

35200
E12IIS
c-RTL-AMD64
15.01.0396.030
M.E.Diagnostics.Service
M.E.Diagnostics.PerformanceLogger
M.E.D.P.PerformanceLogSet.StartLog
System.ArgumentException
95c6
15.01.0396.030
False
True
Microsoft.Exchange.Diagnostics.Service

The handle is invalid

The description for Event ID 1039 from source MSExchangeDiagnostics 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:

C:\

Exception
System.Management.ManagementException: Invalid namespace
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.Exchange.Diagnostics.Service.DiagnosticsService.DriveLocked(String diagnosticsRootDrive)

The handle is invalid

Anil over at MSFT posted a very nice fix for Exchange 2013 when following the same procure for on my Exchange 2016 CU1 server successfully remedied the issue and the errors were resolved. If you are experiencing the same events , please check out this article on how to resolve it.

Monday, May 23, 2016

Outlook Chaced Mode Email Delay

Since Outlook 2010 I have been running in online mode to allow me to see "real-time" updates to AD Photos and GAL related items. so I was boggled when a coworker said that on occasion in outlook 2013 he would get new emails in batches. So I spun up a VM with 2013 at the same patch level as him and low and behold I noticed a delay from when the message hit my mailbox according to Outlook Web App & ActiveSync. Running Outlook 2016 on my primary client I to notice the issue when in cached mode. after digging through a very long TechNet thread, I found this article posted by Jeff Guillet over at his blog. his article provide some great insight as to how outlook behaves once it is notified of a new message when running in cached mode.

while this change outlined by Jeff will have a slight performance hit to your Exchange environment it may be help deal with users who notice the delay. when I applied the changes I was not as aggressive and set the values to 10.

Here is the registry Key for Outlook 2016

[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\office\16.0\Outlook\Cached Mode]
"Download"=dword:0000000a
"Upload"=dword:0000000a
"Maximum"=dword:0000000a


hope this helps, till next time