Hi.

I am seeing this event log entry pretty much every 15 minutes:

Log Name: Operations Manager

Source: Health Service Script

Event ID: 102

Level: Error

MbxCountPerMbxDbCollection.ps1 : (53):     $dw = $mg.GetDataWarehouse()

Exception: System.Management.Automation.RuntimeException: You cannot call a method on a null-valued expression.

at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)

at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)

Any clue?

Hi,

Whether your management server is virtual machine? I have ever seens someone have the same issue on his virtual management server. And based on my research, this may be a known issue in Exchange 2013 management pack.

Your environment should have Exchange 2013 monitored, right? Would you please try removing the MP and re-import the Exchange 2013 MP to check the result:

http://www.microsoft.com/en-hk/download/details.aspx?id=39039

In addition, after remove the MP, please run below powershell command:

Remove-SCOMDisabledClassInstance

https://technet.microsoft.com/en-us/library/hh920257(v=sc.20).aspx

Regards,

Yan Li

Yes, it is an Exchange 2013 environment monitored by SCOM 2012 SP1 (Exchange 2013 management pack). Actually, all SCOM management servers are virtual, excepting the RMS which is physical. By the way, the RMS is the one showing these error messages in the Operations Manager event log.

I'll remove the MP, run the Powershell command, and re-import this MP to see what happens.

UPDATE:

I removed the Exchange 2013 management pack, ran 'Remove-SCOMDisabledClassInstance', re-imported the management pack, but still seeing the same error message in the OperationsManager event log every 15 minutes.

Hello,

Did you find the resolution for this issue? I have the same problem.

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher 23 hours 45 minutes ago

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher Wednesday, June 17, 2015 7:28 AM

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher Wednesday, June 17, 2015 7:28 AM

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher Wednesday, June 17, 2015 7:28 AM

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher Wednesday, June 17, 2015 7:28 AM
• Marked as answer by KTManInc 17 hours 19 minutes ago

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher Wednesday, June 17, 2015 7:28 AM
• Marked as answer by KTManInc Friday, July 31, 2015 1:51 PM

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

• Proposed as answer by Aleksandr Kucher Wednesday, June 17, 2015 7:28 AM
• Marked as answer by KTManInc Friday, July 31, 2015 1:51 PM

Same issue for me :

An error is logged in the event viewer every 15 mn :

MbxCountPerMbxDbCollection.ps1 : (65): $result = $dw.GetDataWarehouseData('sdk.Exchange2013_GetMbxCountPerMbxDb',$spParams)

 Exception: System.Runtime.Serialization.SerializationException: Type 'System.Object[]' with data contract name 'ArrayOfanyType:http://schemas.microsoft.com/2003/10/Serialization/Arrays' is not expected. Consider using a DataContractResolver or add any types not known statically to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding them to the list of known types passed to DataContractSerializer.
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at WriteStoredProcedureParameterToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
   at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at WriteStoredProcedureParameterCollectionToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
   at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
   at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.DataContractSerializer.WriteObject(XmlWriter writer, Object graph)
   at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.CreateMessage(Type interfaceType, String methodName, IList`1 parameterNames, IList`1 parameterValues, IList`1 knownTypes)
   at Microsoft.EnterpriseManagement.Common.Internal.MonitoringDataWarehouseServiceProxy.GetDataWarehouseStoredProcedureResult(String SpName, StoredProcedureParameterCollection param, IEnumerable`1 columnFilter, Int32 timeout)
   at Microsoft.EnterpriseManagement.Warehouse.DataWarehouse.GetDataWarehouseData(String storedProcedureName, StoredProcedureParameterCollection param, IEnumerable`1 columnFilter, Int32 timeout)
   at Microsoft.EnterpriseManagement.Warehouse.DataWarehouse.GetDataWarehouseData(String storedProcedureName, StoredProcedureParameterCollection param)
   at CallSite.Target(Closure , CallSite , Object , String , Object )

My management servers have powershell v4 and my exchange servers powershell v3.

This is a bug in MP. Public release will be shipped with next MP version (approximately in the end of June).

As workaround you can disable the rule "Exchange 2013 Organization Synthetic: Mailbox Count"

I just double checked and it seems the new Exchange 2013 MP version has not been released yet. Still 15.0.665.19.

Yesterday, I installed the latest MP version (15.0.666.19). So far, it seems to have fixed this issue.

Thanks,