Skip to main content

SCOM 2012 Service Level Dashboard SLD Empty

Faced an issue when we created the Service Level Dashboard in SCOM 2012
As SLD can be created in the SCOM console in 2012 version of it , i went ahead and created a Distributed Application , then associated Service level monitoring with it.

Finally i went ahead and created the SLD from SCOM Console.

However once the dashboard was created it did not show any data.
The Image is shown here:


As i was checking online i found a thread on technet forum:
http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/def9592c-0de6-47e5-9312-5a5fbbc8df34

Accordingly i checked the Data Warehouse Synchronization Server Discovered Inventory in our case.

It was empty. Image as shown:

Ran the Powershell Script given in the technet forum:

#Note: change these values appropriately
$OperationalDbSqlServerInstance = "SDOHHQDBA107.mog.maerskoil.com"
$OperationalDbDatabaseName = "OperationsManager"
$DataWarehouseSqlServerInstance = "SDOHHQDBA107.mog.maerskoil.com"
$DataWarehouseDatabaseName = "OperationsManagerDW"

$ConsoleDirectory = "E:\Program Files\System Center 2012\Operations Manager\Console"

##########################################


$dataWarehouseClass = get-SCOMClass -name:Microsoft.SystemCenter.DataWarehouse
$seviewerClass = get-SCOMClass -name:Microsoft.SystemCenter.OpsMgrDB.AppMonitoring
$advisorClass = get-SCOMClass -name:Microsoft.SystemCenter.DataWarehouse.AppMonitoring

$dwInstance = $dataWarehouseClass | Get-SCOMClassInstance
$seviewerInstance = $seviewerClass | Get-SCOMClassInstance
$advisorInstance = $advisorClass | Get-SCOMClassInstance

#Update the singleton property values
$dwInstance.Item($dataWarehouseClass.Item("MainDatabaseServerName")).Value = $DataWarehouseSqlServerInstance
$dwInstance.Item($dataWarehouseClass.Item("MainDatabaseName")).Value = $DataWarehouseDatabaseName

$seviewerInstance.Item($seviewerClass.item("MainDatabaseServerName")).Value = $OperationalDbSqlServerInstance
$seviewerInstance.Item($seviewerClass.item("MainDatabaseName")).Value = $OperationalDbDatabaseName

$advisorInstance.Item($advisorClass.item("MainDatabaseServerName")).Value = $DataWarehouseSqlServerInstance
$advisorInstance.Item($advisorClass.item("MainDatabaseName")).Value = $DataWarehouseDatabaseName

$dataWarehouseSynchronizationServiceClass = get-SCOMClass -name:Microsoft.SystemCenter.DataWarehouseSynchronizationService
#$dataWarehouseSynchronizationServiceInstance = $dataWarehouseSynchronizationServiceClass | Get-SCOMClassInstance

$mg = New-Object Microsoft.EnterpriseManagement.ManagementGroup -ArgumentList localhost
$dataWarehouseSynchronizationServiceInstance = New-Object Microsoft.EnterpriseManagement.Common.CreatableEnterpriseManagementObject -ArgumentList $mg,$dataWarehouseSynchronizationServiceClass

$dataWarehouseSynchronizationServiceInstance.Item($dataWarehouseSynchronizationServiceClass.Item("Id")).Value = [guid]::NewGuid().ToString()

#Add the properties to discovery data
$discoveryData = new-object Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData

$discoveryData.Add($dwInstance)
$discoveryData.Add($dataWarehouseSynchronizationServiceInstance)
$discoveryData.Add($seviewerInstance)
$discoveryData.Add($advisorInstance)

#$connector = Get-ScomConnector -name:"Operations Manager Internal Connector"
$momConnectorId = New-Object System.Guid("7431E155-3D9E-4724-895E-C03BA951A352")
$connector = $mg.ConnectorFramework.GetConnector($momConnectorId)

$discoveryData.Overwrite($connector)

#Update Global Settings. Needs to be done with PS V1 cmdlets
Add-pssnapin microsoft.enterprisemanagement.operationsmanager.client

cd $ConsoleDirectory

.\Microsoft.EnterpriseManagement.OperationsManager.ClientShell.NonInteractiveStartup.ps1

Set-DefaultSetting ManagementGroup\DataWarehouse\DataWarehouseDatabaseName $DataWarehouseDatabaseName
Set-DefaultSetting ManagementGroup\DataWarehouse\DataWarehouseServerName $DataWarehouseSqlServerInstance


###################################################
After that it did show  some GUID etc in the Discovered Inventory for Data WareHouse Synchronization Servers
(We have to Management servers)






Within some time the Dashboard started to populate the data .

Hope this Helps.

Comments

Popular posts from this blog

Citrix XenApp 6.5 Discovery fails Event 3989

Citrix XenApp 6.5 Service account password change caused console discovery to fail and we saw event ID 3989 in System Event logs "Citrix XenApp failed to connect to the Data Store. ODBC error while connecting to the database: 28000 -> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." After changing the service account password needed to run the following command on the delivery controllers. DSMAINT CONFIG /user:abc\ABCSVCCitrix /pwd:nP@ssword /dsn:"C:\Program Files (x86)\Citrix\Independent Management Architecture\mf20.dsn" Restart IMA service You should now be able to run the discovery successfully Hope this helps

Group Policy Object did not apply because it failed with error code '0x80070534 No mapping between account names and security IDs was done

One of our servers was losing the Local Admin settings as we control them using GPO (restricted Groups) We were receiving the following event on this particular server : Event ID 4098 Application Event Log The computer 'Administrators (built-in)' preference item in the 'Servers Local Admins {odjd9DBD-22AF-48EA-ADF5-F42ADE4182hst}' Group Policy Object did not apply because it failed with error code '0x80070534 No mapping between account names and security IDs was done.' This error was suppressed. To fix the issue we deleted all the folders from the following location and rebooted the server C:\ProgramData\Microsoft\Group Policy\History Hope this helps.

DSS WSUS server fail to download Updates HTTP status 404: The requested URL does not exist on the server.

When managing a Downstream WSUS server , it may happen that when a patch is approved it tried to immediately download it form the source server (USS) Sometime we see errors in event viewer stating that the the download failed Event ID: 364 Content file download failed. Reason: HTTP status 404: The requested URL does not exist on the server. Source File: /Content/6E/72131F469F73C884B32124746BAFCA2C8E0A106E.cab Destination File: E:\WSUS\WsusContent\6E\72131F469F73C884B32124746BAFCA2C8E0A106E.cab Event ID 10032 The server is failing to download some updates. We also see following entries in softwaredistribution.log 2016-09-26 07:53:29.287 UTC Warning WsusService.3 ContentSyncAgent.ProcessBITSNotificationQueue ContentSyncAgent recieved Failure for Item: f52f0b8a-2b22-43cf-933e-af8de6b11eb6, Item fails 2016-09-26 07:53:29.287 UTC Info WsusService.3 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileDownloadFailed for Item: f5...