Pages

Thursday, 16 February 2012

My Experience installing SCORCH 2012 RC

My Experience installing SCORCH 2012 RC

Server Details

Server Name
Server Role
Operating System
OMMS1
Orchestrator 2012 role server
Windows 2008 R2 Standard
OMDB
SCORCH Database
Windows2008 R2 Enterprise and SQL 2008 R2 Enterprise
 

Account details

LAB\ scorchsvc
SCORCH Management, Runbook, and Monitor Account
LAB\ ScorchUsers
SCORCH users security global group



1. Install SCORCH 2012:
·    Log on using your domain user account that is a member of the ScorchUsers group.
·    Run Setuporchestrator.exe

·    Click on Install
·    Provide the Product registration information and click Next.
 
·    Accept the license agreement and click Next.
·    Check all boxes on the getting started screen for:
o  Management Server
o  Runbook Server
o  Orchestration console and web service
o  Runbook Designer
·    Input the service account “scorchsvc” and input the password, domain, and click Test. Ensure this is a success and click Next.
·    Configure the database server. Type in the local computer name if you installed SQL on this SCORCH Server, or provide a remote SQL server (and instance if using a named instance) to which you have the “System Administrator” (SA) rights to in order to create the SCORCH database and assign permissions to it. Test the database connection and click Next.
·    Specify a new database, Orchestrator. Click Next.

·    Browse AD and select your domain global group for ScorchUsers. Click Next.

·    Accept defaults for the SCORCH Web service ports of 81 and 82, Click Next.
·    Accept default location for install and Click Next.

·    Select the appropriate options for Customer Experience and Error reporting. Click Next.
·    Click Install.
·    Setup will install all roles, create the Orchestrator database, and complete very quickly.
 2. Register and then deploy the Integration Packs that ship with the Release Candidate
        ·    Make a directory on the local SCORCH server such as “C:\Integration Packs”
        ·    Copy to this directory, the downloaded IP’s that shipped with the RC, such as the following:
       ·    virtual_machine_manager_2012_r2_integration_pack.oip
       ·    service_manager_2012_integration_pack.oip
       ·    operations_manager_2007_integration_pack.oip
         · operations_manager_2012_integration_pack.oip
       ·    data_protection_manager_2012_integration_pack.oip
       ·    configuration_manager_2012_integration_pack.oip
·    Open the Deployment Manager console
·    Expand “Orchestrator Management Server”
·    Right click “Integration Packs” and choose “Register IP with the Orchestrator Management Server”
.
·    Click Next, then “Add”. Browser to “C:\Integration Packs” and select all of the OIP files you copied here. You have to select one at a time and go back and click “Add” again to get them all.

Click Next, then Finish. You have to accept the License Agreement for each IP


·    Right Click “Integration Packs” again, this time choose “Deploy IP to Runbook server or Runbook Designer”.

·    Click Next, select all the available IP’s and click Next.



·    Type in the name of your Runbook server role name, and click Add.



·    On the scheduling screen – accept the default (which will deploy immediately) and click Next.



·    Click Finish. Note the logging of each step in the Log entries section of the console.

My Experience to upgrade SCOM 2012 Beta to SCOM 2012 RC

My Experience to upgrade SCOM 2012 Beta to SCOM 2012 RC

Server Details

Server Name
Server Role
Operating System
OMMS1
Management Server and web console Server
Windows 2008 R2 Standard
OMDB
Operations Manager and OperationManagerDW
Windows2008 R2 Enterprise and SQL 2008 R2 Enterprise

 Account details

LAB\OMAA
OM Serer Action Account
LAB\OMDAS
OM Config and Data Access service Account
LAB\OMWRITE
OM Reporting Write Account
LAB\OMREAD
OM Reporting Read Account
LAB\SQLSVC
SQL 2008 Service Account
LAB\OMADMIS
OM Administration Security Group
LAB\OMADMIN
OM Administration Account

 Upgrading Management Server Role on OMMS1

· Logon using OM Administration Account (OMADMIN)

· Run Setup.exe and click on Install

 ·         Accept the License Agreement and click Next
 


·         Click Next




·         Accept the default install path and click on Next





·         On the accounts screen, Enter the system Center Configuration Service and System Center Data Access service Account


·         Click on Upgrade


·         Once Setup complete click on Close

Friday, 11 November 2011

My Experience Handling Event ID: 10830 issue


My Experience Handling Event ID: 10830 issue

Event Type:           Error
Event Source:       Health Service Modules
Event Category:   None
Event ID:                10830
Date:                      11/11/2011
Time:                      10:33:27 AM
User:                      N/A
Computer:             IND-APP142
Description:
An alert couldn't be inserted to the database. This could have happened because  of one of the following reasons:

                - Alert is stale. The alert is generated by an MP recently deleted.
                - Database connectivity problems or database running out of space.
                - Alert received is not valid.

 The following details should help to further diagnose:

 Details: RuleId:8654b44b-a532-3e3a-19be-1d4a66e9f790. HealthServiceId:e840b3ad-86d3-d373-1970-4c8b39f171c2. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:8654b44b-a532-3e3a-19be-1d4a66e9f790. HealthServiceId:e840b3ad-86d3-d373-1970-4c8b39f171c2. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated..


To display which Agent is sending the Stale Data use the below commandlet

get-monitoringobject -id < HealthServiceId>
Ex: get-monitoringobject -id e840b3ad-86d3-d373-1970-4c8b39f171c2

This will display the agent name which is causing the issue. Follow the below steps to resolve the issue.

1.     Login to the effected server
2.     Stop the System Center Management Service
4.     Start the System Center Management service.

My Experience Handling Event ID: 31552 issue


My Experience Handling Event ID: 31552 issue

We have observed below two flavors of Event ID’s. I have worked with PSS support team around 3 months to fix this issue.  Belo w are the Event Details


Event Type:           Error
Event Source:       Health Service Modules
Event Category:   Data Warehouse
Event ID:                31552
Date:                      6/28/2011
Time:                      9:16:46 AM
User:                      N/A
Computer:             IND-APP142
Description:
Failed to store data in the Data Warehouse.
Exception 'SqlException': Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
One or more workflows were affected by this. 
Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance
Instance name: State data set
Instance ID: {0AD76E64-3116-AE30-BCF0-740C26A1863C}
Management group: MG_IND
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Event Type:           Error
Event Source:       Health Service Modules
Event Category:   Data Warehouse
Event ID:                31552
Date:                      6/24/2011
Time:                      5:37:48 AM
User:                      N/A
Computer:             IND-APP142
Description:
Failed to store data in the Data Warehouse.
Exception 'SqlException': Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
One or more workflows were affected by this. 
Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.Configuration
Instance name: tac-app142.prod.ds.russell.com
Instance ID: {024F88C7-F71B-9221-D650-8D988DB4901B}
Management group: MG_IND
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


The first event (Instance name: State data set) we have fixed with the below steps.

Query to display the Dirty Ind’s

Declare @DataSet as uniqueidentifier
Set @DataSet = (Select datasetid from standarddataset where schemaname = 'State')

Select Count(*) from StandardDataSetAggregationHistory
where DataSetId = @DataSet
And DirtyInd = 1
----------------------------------------------------------------------------------------------------------------------------------

Query to clear the Dirty Ind’s
declare @i int
set @i=0
DECLARE @DataSet uniqueidentifier
SET @DataSet = (SELECT DatasetId FROM StandardDataset WHERE SchemaName = 'State')
while(@i<=500)
begin
EXEC standarddatasetmaintenance @DataSet
set @i=@i+1
Waitfor delay '00:00:05'
end
---------------------------------------------------------------------------------------------------------------------------

Second 31552 event was due to we are using SQL 2005 standard version and Online Indexing was failing every hour. This which captured using SQL profiler tool.