Today i am going to talk about one of annoying errors that has been flooding my SCOM lately.
Data Warehouse failed to deploy reports for a management pack to SQL Reporting Services Server. Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
Exception ‘DeploymentException’: Failed to deploy reports for management pack with version dependent id ‘edf9e0b9-65aa-df29-6729-d16f0005e820’. Failed to deploy linked report ‘Microsoft.SharePoint.Server_Performance_Report’. Failed to convert management pack element reference ‘$MPElement[Name=”Microsoft.SharePoint.Foundation.2013.Responsetime”]$’ to guid. Check if MP element referenced exists in the MP. An object of class ManagementPackElement with ID 75668869-f88c-31f3-d081-409da1f06f0f was not found.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
In short the error was telling me that my SCOM is unable to deploy SharePoint server performance related reports to SCOM reporting services, which means that SharePoint Reports will be unavailable, however that was not the case for me. As I was able to see all SP 2013 reports listed in my reporting pane.
So I thinking it to be a false positive and have been breaking my head on this for almost 3 days to resolve the alert.
- I deleted the SharePoint 2013 MP and added it again
- Reconfigured it again
- Recheck all run as accounts
But still nothing seemed to fix this thing.
Then after a lot searching I came across Kevin Holman blogs which states that it is known issues with SharePoint 2013 MP 15.0.4425.1000
Follow the above link for more information on this.
While working at a customer site, I came across a situation suddenly where on of the MS was in grayed out state.
Initially I followed the main troubleshooting steps in these situation that we all do:
- Flush Health service state cache from SCOM console, for MS you can do it from Operations Manager folder -> Management group Health
Click on MS and in RHS under task select ‘Flush Health service state’ It was fine for 2 mins or so and then again back to grayed out state.
So time for next move
- Deleted the ‘Health service state’ under operations manfer-> Server folder on the MS
Still same thing server is backed to grayed out state.
I am now going through each and every error in event viewer and that’s when I came across below error related to healthservice
Now it makes sense, so the main culprit here is this workflow.
Actually, this workflow is lined with OMS, but client is neither using OMS nor have they configured it ever.
So, it quite odd to have this pop here.
In the OMS configuration console, nothing is configured. So very odd.
Obviously, you can’t remove the OMS or System Center Advisor or Intelligence MP from SCOM as to do that you have to remove other dependant MPs which is not possible, so what do we do?
Now comes the resolution,
- GO to Authoring Pane-> Rules type intel
- You will find the below 3 rules show up in search results.
- Click on first 2 rules and select enable hit override value as False make sure to select enforce check box too
- Repeat it other for the 2nd rule
- Save these overrides in a separate MP and not under Default MP
- Once done, now again flush healthservice state cache and check
Voila! MS is now healthy, when I check event viewer logs, even the error are now gone.
Note: Do this only when you DO not want to connect your on-premise SCOM to OMS
When it says select performance counter like in the screenshot below and you do not see anything to select
Enable the monitors which are associated with the performance counters.
Monitors associated with the performance counters are in disabled state. As a result, you get the see the views but cannot select the counters.
This happens when we import MPs which bring in monitors but it is in disabled state by default.
While working at a customer location, one day i got a request that they need to send email on scom alerts but does not want to use the traditional or scom email notifications. Reason that sometimes the person or team who needs to be notified can be different than what is created in subscribers for email notifications.
That’s when i thought that is a really a good request and needs to be incorporated. There is paid option for it in the market already but client was not looking to pay for such a small thing. So i decided to make one and came up with this:
Send email from SCOM console directly
How it works:
- When you see an alert is scom console, under Alert Tasks on RHS you also see an action called send email
- Once you click on it, a new email from your default email client opens up
- All alerts related details are auto filled in the new email
- Just need to add the people in TO field of email
- and hit send.
I hope this will help a lot of you.
Please do share your feedback.