Posts

Showing posts from May, 2017

Report server install error "The specified SQL Server instance is not valid."

After installing a new SCOM 2016 management group I was getting this error when trying to install the Reporting server component on a seperate server. The DW database was on a different server that was part of an Always On availability group. When I ran the install it would always bomb out with this error: The specified SQL Server instance is not valid.  The possible causes of this problem include the following: * SSRS has not been configured correctly * Secure Socket Layer (SSL) is configured for the SQL Server Report Server. * A proxy server is configured for the SQL Server Report Server. After much digging around and trying all the usual crazy stuff (delete encryption keys, ResetSRS.exe etc) I found this error in the log that SCOM creates when adding/removing components. It's located in the user profile of whomever is running the install %USERPROFILE%\AppData\Local\SCOM\LOGS\OpsMgrSetupWizard.log. [13:54:08]: Always: :Reporting URL: http://MyReportServer/ReportServer_REP_01 [13:

Console crashing

This affects SCOM 2012 and 2016. At a client site I was doing a side-by-side upgrade of SCOM 2012 SP1 to 2016. In the old SCOM environment clicking on any state views resulted in the UI crashing, the local SCOM guy put it down to a poked SCOM databases. When I built the new 2016 environment, we were getting the same issue. Turns out it was a patch released in October 2016 causing the problem. The fix was to install windows8.1-kb3200006-x64_c699272ce136f853353d4c6804126b8a6025d76a.msu. Kevin discusses it  here .

Migrate notifications to another management group

These are the steps I took to migrate notifications from a production SCOM 2012 SP1 management group to a new 2016 management group. This works really well and is an awesome time-saver. Export the Microsoft.SystemCenter.Notifications.Internal mp in the old and new management groups - do not modify these, they are our backup copies Make a copy of both files and rename them to something meaningful like Microsoft.SystemCenter.Notifications.Internal. ManagementGroupName_backup .xml Make a note of the mp version number of the Microsoft.SystemCenter.Notifications.Internal mp from the new management group. In my case it was 7.2.11719.0 Open up the Microsoft.SystemCenter.Notifications.Internal.xml file for the old management group and change the version number to that of the new management group mp version + 1 . In my case I changed it from 7.0.9538.0 to 7.2.11719.1. This is so the mp imports properly in the new management group At this point you may want to consider disabling all the subscrip

Fixing SPN issues

When you install SCOM 2012/16 you will usually get this alert form all management servers: Name:  Data Access Service SPN Not Registered Description:  The System Center Data Access service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/hostname and MSOMSdkSvc/hostname.domain.name to the servicePrincipalName of CN=hostname,OU=MyOU,DC=domain,DC=name This alert is a bug and is discussed  here . I usually disable this alert as it's useless but we do need to confirm SPNs are setup correctly so run this command: setspn -L domain\DasUserAccount You should get this back if it's all good: Registered ServicePrincipalNames for CN=domain\DasUserAccount,OU=MyOU,DC=domain,DC=name: MSOMSdkSvc/MS1 MSOMSdkSvc/MS1.domain.name MSOMSdkSvc/MS2 MSOMSdkSvc/MS2.domain.name If not, we just need to setup the SPNs for all management servers like this: setspn -S MSOMSdkSvc/MS1 domain\DasUserAccount setspn -S MSOMSdkSvc/MS1.domain.name domain\DasUserAccount setspn -S MSOMSdkSvc/MS2 domai

SCOM general

Install logs To view the log files created when adding or removing SCOM components are here %LOCALAPPDATA%\SCOM\LOGS. Where are my database servers? To find the servers that the SCOM databases have been installed on, logon to any management server, open regedit and go to  HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup. Ops db is here: DatabaseName DatabaseServerName DW db is here: DataWarehouseDBName DataWarehouseDBServerName Misc alert stuff Severity mapping 0 - Information 1 - Warning 2 - Critical Priority mapping 0 - Low 1 - Medium (or Normal ) 2 - High Default Resolution States 0 - New 247 - Awaiting Evidence 248 - Assigned to Engineering 249 - Acknowledged 250 - Scheduled 254 - Resolved 255 - Closed