Hello everyone. I've recently installed on my OpsMgr 2012 R2 latest Exchange 2013 management pack. After few hours it discovered some alerts, but when i click dashboards view i get an error:

Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderException: An error occurred executing the command: [Microsoft.Exchange.15.Visualization.Components.DataProviders!GridDataProvider/GetOrganizationGridData] in provider: [Microsoft.Exchange15.Visualization.Components.DataProviders.GridDataProvider, Microsoft.Exchange.15.Visualization.Components.DataProviders, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]. : StoredProcedureNotAvailable ---> Microsoft.Exchange15.Visualization.Components.DataProviders.DataWarehouseException: StoredProcedureNotAvailable ---> Microsoft.EnterpriseManagement.Common.UnknownDatabaseException: Could not find stored procedure 'sdk.Microsoft_Exchange_15_Visualization_Components_GetOrganizationGridData'.
   at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
   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 Microsoft.Exchange15.Visualization.Components.DataProviders.GridDataProvider.GetOrganizationGridData(String connectionTicket, DateTime startTime, DateTime endTime)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange15.Visualization.Components.DataProviders.GridDataProvider.GetOrganizationGridData(String connectionTicket, DateTime startTime, DateTime endTime)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.ExecuteInternal[TResult](DataCommand command)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.<ExecuteAsync>b__0[TResult](<>f__AnonymousType0`1 data)

Maybe someone, who already installed latest MP, have the same issue?

Hi,

Based on my research, following error may appear when you open dashboards shortly after the management pack has been imported:

Microsoft.EnterpriseManagement.Common.UnknownDatabaseException: Could not find stored procedure 'sdk.Microsoft_Exchange_15_Visualization_Components_GetOrganizationGridData'

This error occurs because some Management Pack components have not yet been deployed to the System Center Operations Manager data warehouse database. Wait until the deployment process is completed and restart Operations Manager console to get the dashboard working.

Regards,

Yan Li

Yes, I have the same issues with the latest MP for Exchange 2013 15.0.652.19
with Microsoft Exchange Server 2013, both in production and my test environment. tried to upgrade to scom 2012 R2 CU4 in my test environment, but no different. (CU3 in produktion)

The exchange server have exchange 2013 CU5 installed on Windows server 2012

Regards,

Christer Fredriksson.

Hi,

Based on my research, following error may appear when you open dashboards shortly after the management pack has been imported:

Microsoft.EnterpriseManagement.Common.UnknownDatabaseException: Could not find stored procedure 'sdk.Microsoft_Exchange_15_Visualization_Components_GetOrganizationGridData'

This error occurs because some Management Pack components have not yet been deployed to the System Center Operations Manager data warehouse database. Wait until the deployment process is completed and restart Operations Manager console to get the dashboard working.

Regards,

Yan Li

Hi.

I had the same situation as the first question here. As you can see in the error dump, something like "(String connectionTicket, DateTime startTime, DateTime endTime)", made me think that it had to be something related to the language settings on the computer where the console is run from.

The following solution worked for me:

I changed my "Format" to "English (United States)" under Regions settings, restarted the SCOM Console and it work  after that.

Best regards
Jan-Ove Vangen

• Proposed as answer by Chrille_dom Friday, November 28, 2014 11:59 AM

Hi.

I had the same situation as the first question here. As you can see in the error dump, something like "(String connectionTicket, DateTime startTime, DateTime endTime)", made me think that it had to be something related to the language settings on the computer where the console is run from.

The following solution worked for me:

I changed my "Format" to "English (United States)" under Regions settings, restarted the SCOM Console and it work  after that.

Best regards
Jan-Ove Vangen

• Proposed as answer by Chrille_dom Friday, November 28, 2014 11:59 AM

Hi.

I had the same situation as the first question here. As you can see in the error dump, something like "(String connectionTicket, DateTime startTime, DateTime endTime)", made me think that it had to be something related to the language settings on the computer where the console is run from.

The following solution worked for me:

I changed my "Format" to "English (United States)" under Regions settings, restarted the SCOM Console and it work  after that.

Best regards
Jan-Ove Vangen

• Proposed as answer by Chrille_dom Friday, November 28, 2014 11:59 AM

Hi

Thank you Jan-Ove

That workaround worked for me too.

Hi,

Similar issue and none of the steps listed here resolves it.

Regards,

Mirza

Hello,

Anyone had any luck fixing this error? I have the same error. I tried changing the regional settings but it didn't fix it.

I did some more research and tried to run the stored procedures in OpsMgrDW (I provided the requested parameters) but both stored procedures 'Microsoft_Exchange_15_Visualization_Components_GetOrganizationGridData' and 'Microsoft_Exchange_15_Visualization_Components_GetServerGridData' produce the same error Invalid Object name 'Exchange2013.vMailbox'.

I suspect that 'Exchange 2013.vMailbox' is a view in the datawarehouse which is missing, hence the error. If my assumption is correct, there must be a way to recreate and populate this view, no? 

If anyone else has gotten any further with this, any help would be greatly appreciated.

Regards,

Tom

Hi,

we took up this case to Microsoft.

1. Initially as MS recommended, we tried to make the COLLATION NAMES of the reporting databaseto match with that of the Datawarehouse. 

That did not solve it.

2. It was found that the Miscellaneous settings of the Datawarehouse database was modified to custom. We reverted to default and in a while we could see the reports and the dashboard views come up fine.

Regards,

Mirza

Hi Mirza,

Thanks for the update. 

That still doesn't explain why the views weren't created originally when the MP was imported. I extracted the MP, hoping to find a SQL script that would create this view. After extracting it, I could not find a such a sql script....

I'm pretty sure I didn't look over it or maybe it is created as part of another sql script. I'm going to walk through the different sql scripts and see if I can find something...

Kind regards,

Tom.

People,

Thanks to 2 of my colleagues, I can report the issue is fixed here...

If there's interest, I'll explain but it's a lengthy explanation as my problem was not exactly as the one described above...

Kr,

Tom

Hi,

The following is what resolved my problem, this is provided as is. If you want to try this, take precautions and it's at your own risk.

As stated before, my problem was slightly different. After I imported the management pack the views and dashboards were present.
Alerts started coming in, but when I tried to open the organization summary or server summary I got the stored procedure error.
The mp had been imported for 10 days and the regional settings were set to EN-US.
We tried to remove and reimport the mp, didn't help. We had previously deployed the mp to our DEV environment and there it worked fine.

After the third (or fourth) reimport, we kept getting the error. We tried a different approach and went into the OpsMgrDW db to see what had been created and if there was something missing.
Surprise! Only the exchange 2013 schema was present, nothing else was. No views, no tables, no stored procedures.
So we took a snapshot of the sql server. 
We first removed the exchange 2013 schema but left the mp installed.
We then exported the exchange 2013 schema from our DEV environment as a create sql script. We ran it on our Prod OpsMGrDW DB and it completed without error.
Next, we exported the tables, views and stored procedures from our DEV environment as a create sql script and ran that. That also completed successful.
I went back to the console did a refresh and could open the organization summary and server summary without error.
A little later, monitoring kicked in and so far everything is working fine. No more stored procedure error.

I do have to note that our DEV environment doesn't have an exchange 2013 environment, so everything the mp created when we imported it to the dev environment  was created properly but it was empty.

And yes, I still have those sql scripts...

Kind regards,

Tom

And for completeness and reference if you want to check in your environment, following elements were present in my OpsMgrDW DB when it started to work properly. (Sorry for any typos I might have made)

Schema:

Exchange 2013 Schema

Tables:

Exchange2013.Mailbox, Exchange2013.MailboxDatabase, Exchange2013.MailboxDatabaseBackupInfo_AC0BF88D359B4942A0DD0A913C2CE140, Exchange2013.MailboxDatabaseStaging, Exchange2013.MailboxProperties_B686F07FBC924DC8BA4EB8B1E47FC310, Exchange2013.MailboxStatsDaily_3FE9C0A2A86543D39631D2D962962480, Exchange2013.MailboxStatsRaw_B686F07FBC924DC8BA4EB8B1E47FC310, Exchange2013.MailboxStatsStaging

Views:

Exchange2013.vMailbox, Exchange2013.vMailboxDatabase, Exchange2013.vMailboxDatabaseBackupInfo, Exchange2013.vMailboxProperties, Exchange2013.vMailboxStatsDaily, Exchange2013.vMailboxStatsRaw

Stored Procedures:

dbo.Exchange2013_MailboxDatabaseGroom, dbo.Exchange2013_MailboxDatabaseInsertStaging, dbo.Exchange2013_MailboxProcessStaging, dbo.Exchange2013_MailboxDatabaseStatsAggregate, dbo.Exchange2013_MailboxStatsDelete, dbo.Exchange2013_MailboxDatabaseStatsGroom, dbo.Exchange2013_MailboxDatabaseStatsProcessStaging, dbo.Exchange2013_Report_GetRelatedResults, dbo.Exchange2013_Report_MailboxStatsTopReportDataGet, dbo.Exchange2013_Report_PerfomaceReportDataGet, dbo.Exchange2013_Report_PerformaceTopReportDataGet, sdk.Exchange2013_GetMbxCountPerMbxDB, sdk.Microsoft_Exchange_15_Visualization_Components_GetOrganizationGridData, sdk.Microsoft_Exchange_15_Visualization_Components_GetServerGridData

Thanks Tom,

For us the , the store procedure built did not work. 

Eventually the DW Miscellanous settings  was set to default, especialy Parameterization  changed to Simple from Forced.

That did the trick!

regards,

Mirza