locked
Failure on Disaster recovery of OpsMgr RMS RRS feed

  • Question

  • Hi,

    I have the following configuration

    one Server , RMS : MS Server 2008 R2

    one SQL : SQL 2008 R2

    SQL Database name : OperationManager ( default )

    My admin account that is performing the installation is local admin on the server and sysadmin on the SQL instance.

    This configuration worked before, only the server of the RMS needed reinstallation because of failures.

    When I install Operation Manager 2007 R2 , I de-select the database and web console option and continue with the installation

    My SQK account is SVC-SCOM-SDK

    My Action account is SVC-SCOM-ACTION

    At the end of the installation , a rollback will be performed and following error message will appear "the setup failed. Do you want to open the setup log file (search for "value 3" int he file for locating the failure)?

    Here is a partial printout of the installation file

    === Verbose logging started: 26/12/2011 9:21:08 Build type: SHIP UNICODE 5.00.7601.00 Calling process: D:\SetupOM.exe ===
    MSI (c) (FC:4C) [09:21:08:516]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (FC:4C) [09:21:08:516]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    .....

    MSI (s) (68:7C) [09:25:36:337]: Pathbuf: 0, pcchPathBuf: 0
    MSI (s) (68:7C) [09:25:36:337]: MsiProvideAssembly is returning: 1607
    MSI (s) (68:7C) [09:25:36:353]: Note: 1: 2318 2:
    MSI (s) (68:7C) [09:25:36:353]: No System Restore sequence number for this installation.
    MSI (s) (68:7C) [09:25:36:353]: Unlocking Server
    MSI (s) (68:7C) [09:25:36:368]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
    Action ended 9:25:36: InstallFinalize. Return value 3.
    Action ended 9:25:36: INSTALL. Return value 3.
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductCode = {26D71F0F-82B4-418B-96AC-BB9E54CED283}
    Property(S): ProductLanguage = 1033
    Property(S): ProductName = System Center Operations Manager 2007 R2
    Property(S): ProductVersion = 6.1.7221.0
    Property(S): UpgradeCode = {17058653-A628-4C03-8F80-5E2B179ECD55}
    Property(S): LocalizationLanguageCode = en
    Property(S): TraceFileFlags = -1610610882
    Property(S): ServerSKU = Select
    Property(S): SPUPGRADE = 0
    Property(S): XPlatPresent = 0
    Property(S): PIDKEY = GJHQMVGWHXVKRV6KY6G4MVFY4
    Property(S): PIDTemplate = 91389<````=````=````=````=`````>@@@@@
    Property(S): MPC = 02000
    Property(S): PID = 02000-169-2503272-70808
    Property(S): TRACE_FLAGS1 = 1
    Property(S): TRACE_FLAGS2 = 1
    Property(S): TRACE_FLAGS3 = 39999
    Property(S): TRACE_FLAGS4 = 9999
    Property(S): TRACE_FLAGS5 = -1
    Property(S): NetFxVersion = v2.0.50727
    Property(S): TraceLevelFlags = 1610612497
    Property(S): TraceModeFlags = 1610612497
    Property(S): INSTALLLEVEL = 100
    Property(S): ALLUSERS = 1
    Property(S): ARPNOREPAIR = 0
    Property(S): ARPURLINFOABOUT =
    http://www.microsoft.com/mom
    Property(S): ARPURLUPDATEINFO =
    http://www.microsoft.com/mom
    Property(S): ARPHELPLINK =
    http://support.microsoft.com
    Property(S): SET_SQL_PROPERTIES_UI = 0
    Property(S): MSSQL_CSDVERSION = 0
    Property(S): MSSQL_VERSION = 0
    Property(S): ROOT_MANAGEMENT_SERVER_PORT = 5723
    Property(S): IS_MOM_GATEWAY = 0
    Property(S): MSIRESTARTMANAGERCONTROL = Disable
    Property(S): SDK_SERVICE_DESC = Microsoft System Center Data Access service.
    Property(S): CONFIG_SERVICE_DESC = Microsoft System Center Management Configuration service.
    Property(S): VSS_WRITER_DESC = This service is responsible for the backing up and restore of System Center data.
    Property(S): QUEUE_ERROR_REPORTS = 1
    Property(S): PREREQ_COMPLETED = 1
    Property(S): MOMDATABASENAME = OperationsManager
    Property(S): SQL_PORT = 1444
    Property(S): DbSizeGood = 1
    Property(S): DbFileOptionsGood = 1
    Property(S): DbFilesSpaceGood = 1
    Property(S): DbNameGood = 1
    Property(S): SqlServicesStarted = 1
    Property(S): _IsMaintenance = Change
    Property(S): IsSDKAccountAdmin = 0
    Property(S): IsValidMOMDBServer = 0
    Property(S): IsValidMOMDBVersion = 0
    Property(S): IsActionAccountDomainAdmin = 0
    Property(S): BrowseFolderDlgType = 0
    Property(S): SDK_USE_COMPUTER_ACCOUNT = 0
    Property(S): ACTIONS_USE_COMPUTER_ACCOUNT = 0
    Property(S): DB_SIZE = 1000
    Property(S): SQL_SERVICE_ACCOUNT_IS_SYSTEM = 0
    Property(S): WEB_CONSOLE_AUTH_TYPE = 1
    Property(S): SEND_CEIP_REPORTS = 0
    Property(S): ErrorDialog = SetupErrorDlg
    Property(S): ProgressType1 = Installing
    Property(S): ProgressType2 = installed
    Property(S): ProgressType3 = installs
    Property(S): ProgressType0 = install
    Property(S): AgreeToLicense = No
    Property(S): LAUNCH_MOMCONSOLE = 1
    Property(S): LAUNCH_SECURESTORAGEWIZARD = 1
    Property(S): DlgTitleStyle = {\DlgTitleStyle}
    Property(S): DlgTitleStyleNoContrast = {\DlgTitleStyleNoContrast}
    Property(S): DlgTextStyle = {\DlgTextStyle}
    Property(S): TahomaContrastBlack8 = {\TahomaContrastBlack8}
    Property(S): DlgTextStyleA = {\DlgTextStyleA}
    Property(S): DlgTextStyleB = {\DlgTextStyleB}
    Property(S): DlgTitleStyleA = {\DlgTitleStyleA}
    Property(S): FixedStyle = {\FixedStyle}
    Property(S): ButtonTextStyle = {\ButtonTextStyle}
    Property(S): DefaultUIFont = DlgTextStyle
    Property(S): PreReq_Status = PreReq_Requirements_Not_Met



    C:\MSSQL\Database\
    Property(C): DatabaseModuleDir.8B971A95_4A1B_4552_AF45_A14DE010402F = C:\MSSQL\
    Property(C): MOMDBINSTALL = 1
    Property(C): ADMIN_ROLE_GROUP_FORDB = BUILTIN\Administrators
    Property(C): CLIENTPROCESSID = 1788
    Property(C): CLIENTUILEVEL = 0
    Property(C): CURRENTDIRECTORY = D:\
    Property(C): ComputerName = ESSENTV-SCOM-02
    Property(C): SystemLanguageID = 2067
    Property(C): ScreenX = 1224
    Property(C): ScreenY = 858
    Property(C): CaptionHeight = 19
    Property(C): BorderTop = 1
    Property(C): BorderSide = 1
    Property(C): TextHeight = 16
    Property(C): TextInternalLeading = 3
    Property(C): ColorBits = 16
    Property(C): TTCSupport = 1
    Property(C): Time = 9:26:56
    Property(C): Date = 26/12/2011
    Property(C): MsiNetAssemblySupport = 4.0.30319.1
    Property(C): MsiWin32AssemblySupport = 6.1.7601.17514
    Property(C): RedirectedDllSupport = 2
    Property(C): MsiRunningElevated = 1
    Property(C): DATABASE = C:\Users\adm-mva\AppData\Local\Temp\3\eff060a.msi
    Property(C): OriginalDatabase = D:\server\AMD64\MOM.msi
    Property(C): SOURCEDIR = D:\server\AMD64\
    Property(C): MediaSourceDir = 1
    Property(C): VersionHandler = 5.00
    Property(C): UILevel = 5
    Property(C): ACTION = INSTALL
    Property(C): EXECUTEACTION = INSTALL
    Property(C): ROOTDRIVE = C:\
    Property(C): CostingComplete = 1
    Property(C): OutOfDiskSpace = 0
    Property(C): OutOfNoRbDiskSpace = 0
    Property(C): PrimaryVolumeSpaceAvailable = 0
    Property(C): PrimaryVolumeSpaceRequired = 0
    Property(C): PrimaryVolumeSpaceRemaining = 0
    Property(C): AGENTSERVERCOMPATIBLE = 1
    Property(C): PIDRET = 0
    Property(C): IsActionsAccountGood = 1
    Property(C): IsSDKAccountGood = 1
    Property(C): ROOT_MANAGEMENT_SERVER_DNS = ESSENTV-SCOM-02.ESSENT-BE.NET
    Property(C): ROOT_MANAGEMENT_SERVER_AD = ESSENTV-SCOM-02.ESSENT-BE.NET
    === Logging stopped: 26/12/2011 9:26:56 ===
    MSI (c) (FC:0C) [09:26:56:085]: Note: 1: 1708
    MSI (c) (FC:0C) [09:26:56:085]: Product: System Center Operations Manager 2007 R2 -- Installation operation failed.

    MSI (c) (FC:0C) [09:26:56:085]: Windows Installer installed the product. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

    MSI (c) (FC:0C) [09:26:56:101]: Grabbed execution mutex.
    MSI (c) (FC:0C) [09:26:56:101]: Cleaning up uninstalled install packages, if any exist
    MSI (c) (FC:0C) [09:26:56:101]: MainEngineThread is returning 1603
    === Verbose logging stopped: 26/12/2011 9:26:56 ===

    I already tried to remove the SQL accounts for SCOM , but this did not help.

    Thanks for the help

     

     

    Monday, December 26, 2011 9:06 AM

Answers

  • In the end I retried the new installation. ( Installation of new DB on SQL and installation of SCOM on the Server)

    This time it worked.

    When I copied a restore of my database and restored the encryption key, SCOM failed again. (bumpt into authentication failure )

    This makes me believe that my encryption key was faulty.

    As a result of this I had to redo the installation of my SCOM setup from scratch.

    • Marked as answer by Graham Davies Monday, March 26, 2012 6:23 PM
    Tuesday, January 3, 2012 2:43 PM

All replies

  • Hi,

     

    Please see this thread, it's seems the same problem like you:

    http://social.technet.microsoft.com/Forums/hu-HU/operationsmanagerdeployment/thread/9cfd2fdd-4127-4ce5-83aa-1133885cdc06


    Best Regards
    Monday, December 26, 2011 9:41 AM
  • Verify if FQDN and netbios ping is ok.

    Check if Webmtest goes fine from RMS to database server.

    Make sure you remove every bits of previously installed SCOM component.

     

    I feel, the database connectivity is failing to get authenticated with the accounts.

     


    Check my blogs at http://blogs.technet.com/chandanbharti ============================================================ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, December 26, 2011 7:12 PM
  • Thanks for your response Chandan,

    the SQL instance in FQDN and NETBIOS name are ok, also if I login onto the SQL machines and I ping FQDN and NetBios name of the SCOM server.

    Also the physical SQL servers are pingable from the SCOM server

    I completely reinstalled the SCOM RMS server , I even removed the AD containers with the momADAdmin tool.

    I'm not really sure what you mean by Webmtest.

    During the installation, the SQL logging does not generate any error. I do see that the SDK and Action account are created in SQL ( so the connectivity with the SQL seems to be OK ).

    This is my extra TS:

    I  created a new DB with the DBCreateWizard on SQL , with the same Management Group name and still the "value 3" error keeps coming up.

    I also installed a SQL Express 2008 R2 locally on the server. I use the same SDK account and Action account , and this works...


    • Edited by MvanWambeke Tuesday, December 27, 2011 1:23 PM
    Tuesday, December 27, 2011 10:02 AM
  • In the end I retried the new installation. ( Installation of new DB on SQL and installation of SCOM on the Server)

    This time it worked.

    When I copied a restore of my database and restored the encryption key, SCOM failed again. (bumpt into authentication failure )

    This makes me believe that my encryption key was faulty.

    As a result of this I had to redo the installation of my SCOM setup from scratch.

    • Marked as answer by Graham Davies Monday, March 26, 2012 6:23 PM
    Tuesday, January 3, 2012 2:43 PM