Configuration Troubleshooting Upgrade

SCOM 2012 SP1 – “Unable to Proceed” Troubleshooting Upgrade Error

Posted on Author stefanroth Comments(8)

As I already have learned in many ways – Don’t assume anything, proof it! Another rule is – What you see is not always what you get. With those two quotes in mind we have to start troubleshooting in IT.

Today I spent quite some time troubleshooting an SCOM SP1 upgrade installation. I wanted to upgrade a SCOM 2012 management group as I did few times for other customers – without any pain. This time after starting the setup I faced this dialog…

1

I spent a lot of time figuring out what this is all about.

First I made sure the database server for the data warehouse is up and running. Because there were multiple instances running I checked all the permissions for the database engine and reporting services and so on. Everything was wonderful. Next, I checked the DNS resolution for the SQL server instance and tuned of the firewall. Well, the problem persisted.

Now it’s time to ignited the second booster of the rocked and I dived deeper into troubleshooting.

If you want to find the setup logs for the SCOM setup wizard you need to go to the following directory…

%LocalAppData%\SCOM\Logs

this is the place where the good information lives…

OpsMgrSetupWizard.txt => This is the actual setup log file of the wizard
SCOMPrereqCheck.txt => Prerequisite checker log
OMConsole.txt => OM console install log
OMServer.txt => OM server install log
Setup[0-X].txt => Every time you start the setup a new setup log is generated

image

I was interested in the OpsMgrSetupWizard.txt log and there I found the following error…

image

at the end of the log some more error hints…

image

These error forced me to re-check the permissions and services on the SQL server instance etc. I couldn’t find any misconfiguration at all, therefore after some time I decided to concentrate on the network layer. In order to see what the wizards might see if he queries the SQL server I used portqry.exe to check the ports and instances. I downloaded the tool from here  and ran the command to query the SQL server for the instances and to make sure the server and ports are reachable…

portqry.exe –n [SQL server name] -p UDP -e 1434

image

This output means everything is ok with the network and SQL layer because you can resolve the names and get the instances back. Next, I focused on the Operations Manager settings. Therefore, I opened the registry on one of the failing management servers and went to the registry key…

HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup

image

By just looking at it I didn’t notice anything special, until I looked closer at the DataWarehouseDBServerName key. The key was  [Server]\DWHSCOM01 and it supposed to be [Server]\SCOMDWH01 .

After changing to the correct SQL server instance name in the registry the setup wizard ran correctly.

6

I hope I could give you some tips on troubleshooting and fixing this problem…

stefanroth
http://www.stefanroth.net

Related Articles
Troubleshooting

SCOM 2012 – Reporting Server Install Error

Posted on Author stefanroth

Recently I ran into a problem while installing the reporting components of SCOM 2012. Everything went well until selecting the SQL Server instance and clicking “Next”. The error below hit my screen.
Azure Configuration OMS Performance

OMS – Monitor Windows Services / Processes

Posted on Author stefanroth

One thing I am missing in OMS is, to monitor windows services and processes easily. Well, there are many ways to monitor such components with OMS like: Run some sort of PowerShell script on the server to check the windows service or processes status and then use the HTTP Data Collector API to ingest the […]
Configuration Management Pack Script

SCOM 2012 – Import Multiple Management Packs (Import-SCOMManagementPack)

Posted on Author stefanroth

There are maybe certain situation where you need to import multiple management packs using the “Import-SCOMManagementPack” command. How do you accomplish that? It is easy! Because the command is taking care of the dependencies we just have to provide ALL of the needed management packs in an array. In my example I want to import […]

8 Replies to “SCOM 2012 SP1 – “Unable to Proceed” Troubleshooting Upgrade Error”

  1. Thanks for a very useful post. I had a similar problem that ultimately turned out to be the user I was trying to install the upgrade from.
    Eventually I logged on as the person who installed the program originally (luckily we still had an account for him) and it worked!
    I had a similar problem adding the license key to update it from an eval version! I must admit this kind of thing is very frustrating from MS!.

    Thanks again.

    Reply

  2. Thanks a lot for your blog.. I had faced the same problem as you did, and had to spend lot of time getting to your blog.. but patience was definelty fruitful..
    Thanks once again…

    Reply

  4. Hello, Stefan
    I am a customer and I’m having the same problem follow in his footsteps and log OpsMgrSetupWizard found this:
    16:05:16]: Info :: Info: Using DB command timeout = 1800 seconds.
    [16:05:16]: Error :: GetManagementGroupInfoFromDB: Error: {0}: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: The EXECUTE permission was denied on the object ‘p_MOMManagementGroupInfoSelect’, database ‘OperationsManager’, schema ‘dbo’.
    [16:05:16]: Error :: StackTrace: at System.Data.SqlClient.SqlConnection.OnError (SqlException exception, Boolean breakConnection)
    For the characteristic of error is a permission problem in the database.
    I have a User who is a local administrator of the server.
    The suggestion is this User to have local administrator pemissões as sysadmin in Sql Server 2008 R2? Sql server is installed on the same server as SCOM 2012.
    Thank you for your attention.

    Reply

  5. Hello,
    I also have problem to uprgrade from SCOM 2012 to SCOM 2012 SP 1. I can read in OpsMgrSetupWizard:
    [17:57:36]: Info: :Info:Using DB command timeout = 1800 seconds.
    [17:57:36]: Error: :GetManagementGroupInfoFromDB: Error: {0}: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: The EXECUTE permission was denied on the object ‘p_MOMManagementGroupInfoSelect’, database ‘OperationsManager’, schema ‘dbo’.
    [17:57:36]: Error: :StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
    at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader()
    at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.OperationsManagerHelpers.GetManagementGroupInfoFromDB(String sqlServer, Nullable`1 sqlPort, String omDatabaseName, String& strMGName)
    [17:57:36]: Error: :Error:Management Group Name is missing.
    [17:57:36]: Info: :Info:Using DB command timeout = 1800 seconds.
    [17:57:36]: Error: :failed to get DB version from OM DB: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: The SELECT permission was denied on the object ‘__MOMManagementGroupInfo__’, database ‘OperationsManager’, schema ‘dbo’.
    [17:57:36]: Error: :StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
    at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader()
    at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetDBVersionFromOMDB(SqlConnection connection, String& dbVersion)
    [17:57:36]: Error: :Error:Failed to detect RC server upgrade scenario
    [17:57:36]: Always: :End: Rationalize Operations Manager Server upgrade.
    [17:57:36]: Error: :RationalizeComponents blocked because: Failed to detect server scenario for upgrade case.
    [17:57:36]: Always: :End: Rationalize server component.
    [17:57:36]: Error: :Error:Could not rationalize OMSERVER and thus setup is blocked.
    [17:57:36]: Debug: :OMForwardToStartPageTrackPageHandler: Moving to page UpgradeInvalidStartPage
    [17:57:36]: Always: :Entering Page: UpgradeInvalidRootPage
    [17:59:35]: Always: :Begin: Property bag dump.
    [17:59:35]: Always: :SetupStartTime = 1/8/2014 5:57:34 PM
    [17:59:35]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
    [17:59:35]: Always: : [0] = ActionAccountPassword
    [17:59:35]: Always: : [1] = DASAccountPassword
    [17:59:35]: Always: :DefaultLogName = C:UsersXXXAppDataLocalSCOMLogsOpsMgrSetupWizard.log
    [17:59:35]: Always: :DefaultLogPath = C:UsersXXXAppDataLocalSCOMLogs
    [17:59:35]: Always: :path = C:Sys_Ctr_Ops_Manager_Svr_2012_wSP1_English_X18-56723SetupAMD64
    [17:59:35]: Always: :setupexepath = C:UserswroothrAppDataLocalSCOM
    [17:59:35]: Always: :ArchitectureIs64Check = True
    [17:59:35]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
    [17:59:35]: Always: : [0] = OMCONSOLE
    [17:59:35]: Always: : [1] = OMSERVER
    [17:59:35]: Always: : [2] = OMWEBCONSOLE
    [17:59:35]: Always: : [3] = OMREPORTING
    [17:59:35]: Always: :OMServerInstalled = True
    [17:59:35]: Always: :RTMUpgrade = 1
    [17:59:35]: Always: :installpath = C:Program FilesSystem Center 2012Operations Manager
    [17:59:35]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
    [17:59:35]: Always: : [0] = OMCONSOLE
    [17:59:35]: Always: : [1] = OMSERVER
    [17:59:35]: Always: : [2] = OMWEBCONSOLE
    [17:59:35]: Always: :EulaFilesPath = C:UsersXXXAppDataLocalSCOM
    [17:59:35]: Always: :SendCEIPReports = 0
    [17:59:35]: Always: :SqlServerInstance = svr-scom1
    [17:59:35]: Always: :DatabaseName = OperationsManager
    [17:59:35]: Always: :ManagementServer = localhost
    [17:59:35]: Always: :WebsiteName = Default Web Site
    [17:59:35]: Always: :WebConsoleAuthorizationMode = Mixed
    [17:59:35]: Always: :ScreensLoaded = 1
    [17:59:35]: Always: :BlockReason = Failed to detect server scenario for upgrade case.
    [17:59:35]: Always: :InstallSuccess = 1
    [17:59:35]: Always: :End: Property bag dump.
    [17:59:35]: Always: :Application Ended: Successful
    [17:59:35]: Always: :
    [2014-01-08T17:59:35.1158874+01:00]: Always: Trace Session Ended

    Reply

    1. Hi

      Make sure the account you are executing the upgrade from has full permission on the SQL Server backend. It seems that your setup can not Access management group name in the database and therefore crashes. Run the setup in elevated (Run as Administrator) permission.

      [17:57:36]: Error: :failed to get DB version from OM DB: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0×80131904, Exception.Message: The SELECT permission was denied on the object ‘__MOMManagementGroupInfo__’, database ‘OperationsManager’, schema ‘dbo’.

      Cheers,

      Stefan

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.