Service Manager 2012 Data Warehouse (Upgrade)

Posted: November 22, 2011 in Data Warehouse
Tags: , , , , ,

 

So, my journey with System Centre Service Manager 2012 Beta has begun and so far I have indeed found some funnies.

I will be blogging about them, to make everyone else’s life a little bit easier and in the hope of better product adoption for this product. It is simply put a fantastic product.

Ok, so the first time I ran the upgrade (remember I have a pre-prod environment), so I was able to rollback and did not have to follow Disaster Recovery with the Failure. I will cover the Disaster Recovery steps that I will follow in Production if I have an issue.

Error

So, like I was saying, I ran into a Reporting Services error when upgrading the Data Warehouse. So I rolled back to a previous state as I am using VMS. However, to resolve this particular issue, I ran the upgrade again. However, this time I opened the SQL Reporting Services webpage and allowed the reporting services webpage to load to completion before running the upgrade.

Reporting Services

I suspect due to the limited specs on my virtual environment, the slow opening and hence communications with the Reporting Services caused my first failure. The second attempt was perfect.

I now had SCSM 2012 Beta Data Warehouse.

So, here is a breakdown of what I did.

1. Install Cumulative Update 2 for System Centre Service Manager 2010 SP1

2. Install Windows Server 2008 R2 Service Pack 1

3. Backup Encryption Key

4. Restart Server

5. Check the status of SQL Reporting Services (services.msc)

6. Check the status of Reporting Service (web site). First load of this website was VERY slow.

7. Disabled Data Warehouse Jobs http://technet.microsoft.com/en-za/library/hh495610(en-us).aspx

8. Waited 10 Minutes

9. Run the Upgrade

10. We have successfully upgraded the Data Warehouse Server.

11. The only thing I did differently this time, I left the reporting services website open the whole time of the upgrade process.

With Analysis Services(Cubes), Permissions are controlled differently. Open SQL Management Studio, and ensure that you connect to Analysis Services and NOT Database Engine and then specify the SQL Server and assign permissions as needed so that people can/cannot access Cubes within Service Manager 2012 Console.

More to follow soon on the Management Server.

Follow me

facebook-small32225 twitter-small32225

MCC_Logo_NEW

Advertisements
Comments
  1. Mikael says:

    Hi Fletcher, nice blog!
    Can you think of any reason why my DW upgrade would fail due to:
    “Service Manager data warehouse management server
    The System Center Management Configuration service could not log on with its
    current credentials. Verify the credentials and retry upgrade.”

    Im follow the:
    How to Upgrade to System Center 2012 – Service Manager

    I’m on SCSM2010 SP1 CU3, I have stopped the DW jobs and the portal web page. I’ve tried various accounts as the service account in question, including my domain/schema admin account. Restarting the service work just fine. All event logs are very uneventful in terms of anything to explain to issue.

    • Rejeesh says:

      I have the same error while doing the upgrade.

      • Can someone perhaps provide a screenshot and some indication of errors from the OpsMan Event log?

      • Rejeesh says:

        Log Name: Operations Manager
        Source: OpsMgr Config Service
        Date: 4/3/2012 6:58:33 PM
        Event ID: 29104
        Task Category: None
        Level: Warning
        Keywords: Classic
        User: N/A
        Computer: XXX014KKKMAAIND.xyz.local
        Description:
        OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
        Event Xml:

        29104
        3
        0
        0x80000000000000

        1221
        Operations Manager
        XXX014KKKMAAIND.xyz.local

        06:20:59:LoadPrerequisites: Start adding ComponentTitles
        06:20:59:LoadPrerequisites: Start adding DataItems
        06:20:59:Memory check
        06:21:14:Microsoft SQL Server 2008 Analysis Management Objects
        06:21:14:Memory check
        06:21:14:Processor speed check
        06:21:14:Processor speed check
        06:21:14:Processor speed check
        06:21:14:IIS check
        06:21:14:ASP.NET check
        06:21:14:Basic Authentication check
        06:21:14:Windows Authentication check
        06:21:14:Microsoft .NET Framework 4 check
        06:21:14:Windows Service Pack check
        06:21:14:Microsoft Report Viewer Redistributable check
        06:21:14:PowerShell 2.0 check
        06:21:14:SharePoint Server 2010 check
        06:21:14:SharePoint Farm Administrator check
        06:21:14:SharePoint Server 2010 configuration check
        06:21:14:ADO.NET Data Services Update check
        06:21:14:Microsoft SQL Server 2008 Native Client check
        06:21:14:Language Pack for SharePoint Server 2010 or SharePoint Foundation 2010 – English check
        06:21:14:LoadPrerequisites: Done adding prerequisites checks
        06:21:14:
        06:21:14:**************************************************
        06:21:14:CheckPrerequisites: Checking Memory check prereq.
        06:21:14:CheckPrerequisites: Logic Type:and MemoryCheck-8gbWarn: 1
        06:21:14:
        06:21:14:CheckPrerequisites: Memory check: Warning
        06:21:14:
        06:21:14:**************************************************
        06:21:14:
        06:21:14:**************************************************
        06:21:14:CheckPrerequisites: Checking Microsoft SQL Server 2008 Analysis Management Objects prereq.
        06:21:14:Entered RequiredAMO
        06:22:26:Trying alternate method of detection using Assembly.Load
        06:22:37:CheckPrerequisites: Logic Type:and AMO-err: 0
        06:22:37:
        06:22:37:CheckPrerequisites: Microsoft SQL Server 2008 Analysis Management Objects: Passed
        06:22:37:
        06:22:37:**************************************************
        06:22:37:
        06:22:37:**************************************************
        06:22:37:CheckPrerequisites: Checking Processor speed check prereq.
        06:22:37:CheckPrerequisites: Logic Type:and DWProcessorSpeedCheck2.5MHz-Warn: 0
        06:22:37:CheckPrerequisites: Logic Type:and ProcessorCoreCheck4Core-Warn: 0
        06:22:37:
        06:22:37:CheckPrerequisites: Processor speed check: Passed
        06:22:37:
        06:22:37:**************************************************
        06:22:37:
        06:22:37:**************************************************
        06:22:37:CheckPrerequisites: Checking Windows Service Pack check prereq.
        06:22:37:CheckPrerequisites: Logic Type:and Win2k8R2Sp1Check-Err: 0
        06:22:37:CheckPrerequisites:
        06:22:37:CheckPrerequisites: ProductType was not a match. Looking for: LanmanNT Found: ServerNT
        06:22:37:CheckPrerequisites: Logic Type:or Win2k8R2Sp1DCCheck-Err: 2
        06:22:37:CheckPrerequisites:
        06:22:37:CheckPrerequisites: The value 6.1.7601.65536 was not within the range 6.2.0 to 9.9.9999.
        06:22:37:CheckPrerequisites: Logic Type:or WinSrvrVNextCheck-Err: 2
        06:22:37:CheckPrerequisites:
        06:22:37:CheckPrerequisites: ProductType was not a match. Looking for: LanmanNT Found: ServerNT
        06:22:37:CheckPrerequisites: Logic Type:or WinSrvrVNextDCCheck-Err: 2
        06:22:37:
        06:22:37:CheckPrerequisites: Windows Service Pack check: Passed
        06:22:37:
        06:22:37:**************************************************
        06:22:37:
        06:22:37:**************************************************
        06:22:37:CheckPrerequisites: Checking PowerShell 2.0 check prereq.
        06:22:37:CheckPrerequisites: Logic Type:and PowerShell2Check-err: 0
        06:22:37:CheckPrerequisites: Logic Type:or PowerShell2Check32-err: 0
        06:22:37:
        06:22:37:CheckPrerequisites: PowerShell 2.0 check: Passed
        06:22:37:
        06:22:37:**************************************************
        06:22:37:
        06:22:37:**************************************************
        06:22:37:CheckPrerequisites: Checking Microsoft SQL Server 2008 Native Client check prereq.
        06:22:37:CheckPrerequisites: Logic Type:and SQLNCLI10-err: 0
        06:22:37:
        06:22:37:CheckPrerequisites: Microsoft SQL Server 2008 Native Client check: Passed
        06:22:37:
        06:22:37:**************************************************
        06:22:37:CheckPrerequisites: Return Value 1
        06:24:06:Collecting SQL instances on server XXX014KKKMAAIND
        06:24:06:Connecting to SQL server 2008 On XXX014KKKMAAIND.ds.petrofac.local
        06:24:06:Error:GetSqlInstanceList(), Exception Type: System.Management.ManagementException, Exception Message: Invalid namespace
        06:24:06:StackTrace: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
        at System.Management.ManagementScope.InitializeGuts(Object o)
        at System.Management.ManagementScope.Initialize()
        at System.Management.ManagementObjectSearcher.Initialize()
        at System.Management.ManagementObjectSearcher.Get()
        at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.GetSqlInstanceList(String sqlServerName, Int32 serviceType)
        06:24:19:Collecting SQL instances on server ABC503KKKMAAIND
        06:24:19:Connecting to SQL server 2008 On ABC503KKKMAAIND.ds.petrofac.local
        06:24:21:Found SQL Instance: ABC503KKKMAAIND
        06:24:21:Getting TCP port for SQL instance ABC503KKKMAAIND
        06:24:21:Connecting to SQL server On ABC503KKKMAAIND.ds.petrofac.local
        06:24:21:Validating SQL Instance ABC503KKKMAAIND
        06:24:21:SQL Server: ABC503KKKMAAIND
        06:24:21:SQL Server version: 10.50.1600.1
        06:24:21:Collation of SQL Instance: SQL_Latin1_General_CP1_CI_AS
        06:24:21:SQL collation: SQL_Latin1_General_CP1_CI_AS
        06:24:21:Service Manager has discovered the use of an unsupported SQL collation. Using an unsupported collation (including the default, SQL_Latin1_General_CP1_CI_AS) might cause unpredictable behavior in multi-lingual environments.

        If you continue to install Service Manager, and later decide to change the SQL collation, you will have to reinstall Service Manager which results in the loss of all accumulated data. For a list of approved SQL collations, consult the Microsoft System Center 2012 – Service Manager Planning Guide.
        06:24:22:Full text search installed: True
        06:24:22:Checking if ‘DSPETROFAC\admin_scsm_maa’ is Sysadmin Or (SecurityAdmin And DbCreator) on SQL Instance ABC503KKKMAAIND
        06:24:22:Getting SQL default Data Path
        06:24:22:SQL default Data Path: H:
        06:24:22:SQL default Log Path: L:
        06:24:22:Connecting to Remote SQL server ABC503KKKMAAIND
        06:24:22:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:22:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:22:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:22:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:22:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:22:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:22:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:22:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:22:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:22:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:22:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:22:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:25:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:25:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:25:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:25:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:25:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:25:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:26:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:26:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:26:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:26:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:26:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:26:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:27:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:27:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:27:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:27:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:27:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:27:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:27:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:27:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:27:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:27:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:27:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:27:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:28:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:28:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:28:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:28:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:28:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:28:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:28:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:28:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:28:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:28:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:28:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:28:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:28:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:29:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:29:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:29:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:29:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:29:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:29:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:29:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:29:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:29:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:29:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:29:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:29:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:29:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:29:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:29:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:29:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:30:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:30:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:30:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:30:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:30:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:30:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:30:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:30:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:30:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:30:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:30:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:30:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:30:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:30:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:30:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:30:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:30:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:30:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:30:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:30:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:30:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:30:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:30:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:30:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:30:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:31:Collecting SQL instances on server ABC503KKKMAAIND
        06:24:31:Connecting to SQL server 2008 On ABC503KKKMAAIND.ds.petrofac.local
        06:24:31:Found SQL Instance: ABC503KKKMAAIND
        06:24:31:Getting TCP port for SQL instance ABC503KKKMAAIND
        06:24:31:Connecting to SQL server On ABC503KKKMAAIND.ds.petrofac.local
        06:24:31:Validating SQL Instance ABC503KKKMAAIND
        06:24:31:SQL Server: ABC503KKKMAAIND
        06:24:31:SQL Server version: 10.50.1600.1
        06:24:31:Collation of SQL Instance: SQL_Latin1_General_CP1_CI_AS
        06:24:31:SQL collation: SQL_Latin1_General_CP1_CI_AS
        06:24:31:Service Manager has discovered the use of an unsupported SQL collation. Using an unsupported collation (including the default, SQL_Latin1_General_CP1_CI_AS) might cause unpredictable behavior in multi-lingual environments.

        If you continue to install Service Manager, and later decide to change the SQL collation, you will have to reinstall Service Manager which results in the loss of all accumulated data. For a list of approved SQL collations, consult the Microsoft System Center 2012 – Service Manager Planning Guide.
        06:24:33:Full text search installed: True
        06:24:33:Checking if ‘DSPETROFAC\admin_scsm_maa’ is Sysadmin Or (SecurityAdmin And DbCreator) on SQL Instance ABC503KKKMAAIND
        06:24:33:Getting SQL default Data Path
        06:24:33:SQL default Data Path: H:
        06:24:33:SQL default Log Path: L:
        06:24:33:Connecting to Remote SQL server ABC503KKKMAAIND
        06:24:33:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:33:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:33:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:33:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:33:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\CMDWDataMart.mdf
        06:24:33:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\CMDWDataMartlog.ldf
        06:24:33:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:33:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:33:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:33:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:33:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\OMDWDataMart.mdf
        06:24:33:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\OMDWDataMartlog.ldf
        06:24:33:Verify Database Configuration on SQL Instance ABC503KKKMAAIND
        06:24:33:Verify Database Data/Log file path on server ABC503KKKMAAIND
        06:24:33:UNC SQL Data Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:33:UNC SQL Log Path: \\ABC503KKKMAAIND.ds.petrofac.local\H$
        06:24:33:Data file path: \\ABC503KKKMAAIND.ds.petrofac.local\H$\CMDWDataMart.mdf
        06:24:33:Log file path: \\ABC503KKKMAAIND.ds.petrofac.local\L$\CMDWDataMartlog.ldf
        06:24:51:Validate Account…
        06:24:51:Validating Account: DSPETROFAC\admin_scsm_maa
        06:24:51:Account ‘DSPETROFAC\admin_scsm_maa’ is valid
        06:24:51:Account ‘DSPETROFAC\admin_scsm_maa’ is Local Admin
        06:24:51:Failed to check for Local account:The requested name is valid, but no data of the requested type was found
        06:24:52:Failed while trying to check remote AS: Invalid namespace – at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
        at System.Management.ManagementScope.InitializeGuts(Object o)
        at System.Management.ManagementScope.Initialize()
        at System.Management.ManagementObjectSearcher.Initialize()
        at System.Management.ManagementObjectSearcher.Get()
        at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.PreReqRemoteMachineforAS(String hostName)
        at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.ValidateAS(String hostName).
        06:25:05:Collecting SQL instances on server ABC503KKKMAAIND
        06:25:05:Connecting to SQL server 2008 On ABC503KKKMAAIND.ds.petrofac.local
        06:25:05:Found SQL Instance: ABC503KKKMAAIND
        06:25:37:Validate Account…
        06:25:37:Validating Account: DSPETROFAC\admin_scsm_maa
        06:25:37:Account ‘DSPETROFAC\admin_scsm_maa’ is valid
        06:25:37:Account ‘DSPETROFAC\admin_scsm_maa’ is Local Admin
        06:25:37:Failed to check for Local account:The requested name is valid, but no data of the requested type was found
        06:25:41:Disable Customer Experience Improvement Program
        06:25:41:Disable Error Reporting
        06:25:41:Disable Operational Data Reporting
        06:25:46:Doing Pre-Upgrade checks…
        06:25:46:Validating database DWStagingAndConfig on SQL Server ABC503KKKMAAIND
        06:25:46:Validating SQL Instance ABC503KKKMAAIND
        06:25:46:SQL Server: ABC503KKKMAAIND
        06:25:46:SQL Server version: 10.50.1600.1
        06:25:46:Full text search installed: True
        06:25:46:Checking if ‘DSPETROFAC\admin_scsm_maa’ is Sysadmin Or (SecurityAdmin And DbCreator) on SQL Instance ABC503KKKMAAIND
        06:25:46:Validating database DWRepository on SQL Server ABC503KKKMAAIND
        06:25:46:Validating SQL Instance ABC503KKKMAAIND
        06:25:46:SQL Server: ABC503KKKMAAIND
        06:25:46:SQL Server version: 10.50.1600.1
        06:25:46:Full text search installed: True
        06:25:46:Checking if ‘DSPETROFAC\admin_scsm_maa’ is Sysadmin Or (SecurityAdmin And DbCreator) on SQL Instance ABC503KKKMAAIND
        06:25:46:Validating database DWDataMart on SQL Server ABC503KKKMAAIND
        06:25:46:Validating SQL Instance ABC503KKKMAAIND
        06:25:46:SQL Server: ABC503KKKMAAIND
        06:25:46:SQL Server version: 10.50.1600.1
        06:25:46:Full text search installed: True
        06:25:46:Checking if ‘DSPETROFAC\admin_scsm_maa’ is Sysadmin Or (SecurityAdmin And DbCreator) on SQL Instance ABC503KKKMAAIND
        06:25:46:Stopping Service OMSDK on server XXX014KKKMAAIND
        06:25:48:Starting Service OMSDK on server XXX014KKKMAAIND
        06:26:54:Stopping Service OMCFG on server XXX014KKKMAAIND
        06:26:57:Starting Service OMCFG on server XXX014KKKMAAIND
        06:28:12:***ERROR*** StartService: System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
        at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
        at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.StartService(String ServiceName, String ComputerName, Boolean Restart)
        06:28:12:The System Center Management Configuration service could not log on with its current credentials. Verify the credentials and retry upgrade.
        06:28:12:*** Pre-Upgrade checks failed ***

  2. Are you logged an as
    1. Local admin of the DW Machine.
    2. This same account must have the required rights for the SQL Database

  3. Rejeesh says:

    yes ..

  4. cgu says:

    Any update on this?? I have the same error in my log: Failed to check for Local account:The requested name is valid, but no data of the requested type was found.
    I’m using local admin and db_owner in SQL.

    • The only thing I can suggest is, ensure that the account you are using has the required rights within SQL and is a LOCAL admin of both the Management Server and the Data Warehouse Server.

  5. Vitaly says:

    well, I got same issue.
    But it appears when I configure my SRSS as remote for date warehouse server.
    And you know, after configuring rssrvpolicy.config and rsreportserver.config I wasn’t able even open to get inside reporting directory http://servername/Report.

    There was an error: unsure that this SRSS is compatable. Strange stuff. Installation DW master tells me that SRSS is unsupportable. However, if I’m leaving this two files by default – the installation and pre-checks goes smoothly.

    Advice please

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s