VMM (2012 R2) PRO/Operations Manager Integration Requires Named Instance for SSAS -- Which is Great in a NOT Clustered Environment
This is my third or maybe 4th time posting this question... surely I can't be the only person that has run into this issue...
Subject more or less captures the essence of my question... I have a clustered SQL 2012 (SP2) environment that runs on 3 nodes (active-passive-passive), one of which runs Analysis Services. As I've come to learn (and likely everyone already knows) SSAS in a
clustered configuration is _ONLY_ accessible using the hostname, FQDN, or VIP. Addressing the named instance results in a failure (I think this is partially a SQL browser bug as looking closely at the requests to SSAS using a named instance results in the
browser issuing a bogus TCP port where no service is actually running). Additionally, not providing a named instance in the VMM console UI results in an error message:
Please enter SSAS instance name
Would greatly appreciate any guidance on this issue. Thank you.
Since you're on your 4th time of asking, let me at least say I'll try to make this your last.
While I haven't got an answer this exact minute, I'll look into it tomorrow as I have access to a clustered SSAS that I can play with.
Probably the reason no-ones answered so far is that for VMM the SSAS instance must be on the same instance as the SCOM Reporting Services and since that can't be clustered most will install standalone.
Regards,
Steve
<a href="http://systemcenter.ninja/">My System Center Blog</a>
Similar Messages
-
HP Operations Manager integration pack 7.1 for SCORCH Error
Hi
I am using the HP Operations Manager integration pack 7.1 for SCORCH this is working well sending messages in both directions from SCOM2012 to HP OM and from HP OM to SCOM with the get message/acknowledge message objects but the monitor message object does
not work at all. No errors are logged and we can see the traffic in a network trace. The monitor message object just never triggers.
has anyone else seen this issue ?
ThanksThe problem that I had was with the HP OM función "Monitor Message". Web service didn´t response Orchestrator.
After all I fond the solution, If you Want the Orchestrator to monitor Messages from HPOM you should
define a filter by message group on the activity "monitor Message";
In this case that's because HPOM has the visibility of the user, configured through the atribute "Message Group".
I hope will be useful.
Regards -
Hi All, looking for some assistance with the following issue.
We are attempting to upgrade our Operations Manager 2012 SP1 environment to Operations Manager 2012 R2.
We have completed all the pre-upgrade tasks detailed here
http://technet.microsoft.com/en-us/library/dn249704.aspx
We are then following the guidance detailed here regarding upgrading distributed management groups
http://technet.microsoft.com/en-us/library/dn249721.aspx. The upgrade fails on the first management server with the following screen being displayed.
OMServer.log file is as follows.
=== Verbose logging started: 22/01/2014 10:21:27 Build type: SHIP UNICODE 5.00.9200.00 Calling process: C:\Users\scomaction\AppData\Local\SCOM\Setup\SetupChainerUI.exe ===
MSI (c) (78:34) [10:21:27:040]: Resetting cached policy values
MSI (c) (78:34) [10:21:27:040]: Machine policy value 'Debug' is 0
MSI (c) (78:34) [10:21:27:040]: ******* RunEngine:
******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
******* Action:
******* CommandLine: **********
MSI (c) (78:34) [10:21:27:040]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (78:34) [10:21:27:040]: Grabbed execution mutex.
MSI (c) (78:34) [10:21:27:071]: Cloaking enabled.
MSI (c) (78:34) [10:21:27:071]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (78:34) [10:21:27:071]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (D4:30) [10:21:27:082]: Running installation inside multi-package transaction F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
MSI (s) (D4:30) [10:21:27:082]: Grabbed execution mutex.
MSI (s) (D4:A0) [10:21:27:086]: Resetting cached policy values
MSI (s) (D4:A0) [10:21:27:086]: Machine policy value 'Debug' is 0
MSI (s) (D4:A0) [10:21:27:086]: ******* RunEngine:
******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
******* Action:
******* CommandLine: **********
MSI (s) (D4:A0) [10:21:27:175]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (D4:A0) [10:21:27:181]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (D4:A0) [10:21:27:190]: SRSetRestorePoint skipped for this transaction.
MSI (s) (D4:A0) [10:21:27:192]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (D4:A0) [10:21:27:200]: File will have security applied from OpCode.
MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi' against software restriction policy
MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi has a digital signature
MSI (s) (D4:A0) [10:21:27:354]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (D4:A0) [10:21:27:354]: MSCOREE not loaded loading copy from system32
MSI (s) (D4:A0) [10:21:27:360]: End dialog not enabled
MSI (s) (D4:A0) [10:21:27:360]: Original package ==> F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
MSI (s) (D4:A0) [10:21:27:360]: Package we're running from ==> C:\Windows\Installer\4b8344.msi
MSI (s) (D4:A0) [10:21:27:371]: APPCOMPAT: Compatibility mode property overrides found.
MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (D4:A0) [10:21:27:378]: Machine policy value 'TransformsSecure' is 1
MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisablePatch' is 0
MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (D4:A0) [10:21:27:380]: Transforms are not secure.
MSI (s) (D4:A0) [10:21:27:380]: Note: 1: 2205 2: 3: Control
MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log'.
MSI (s) (D4:A0) [10:21:27:380]: Command Line: OM_INSTALLDIR=F:\Program Files\Microsoft System Center 2012 R2\Operations Manager SEND_CEIP_REPORTS=0 MU_SETTING=0 ROOT_MANAGEMENT_SERVER_PORT=5723 SC_DB_SERVER=SCOM-XXX-AG SCDATABASENAME=OperationsManager DW_DB_SERVER=SCOM-XXX-AG DWDATABASENAME=OperationsManagerDW REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Users\scomaction\AppData\Local\SCOM\Setup CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=4472
MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{58EFE971-58C1-4DBD-A400-A7607A745475}'.
MSI (s) (D4:A0) [10:21:27:380]: Product Code passed to Engine.Initialize: ''
MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table before transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table after transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
MSI (s) (D4:A0) [10:21:27:380]: Product not registered: beginning first-time install
MSI (s) (D4:A0) [10:21:27:380]: Product {C92727BE-BD12-4140-96A6-276BA4F60AC1} is not managed.
MSI (s) (D4:A0) [10:21:27:380]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (D4:A0) [10:21:27:381]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (D4:A0) [10:21:27:381]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (D4:A0) [10:21:27:381]: Adding new sources is allowed.
MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (D4:A0) [10:21:27:381]: Package name extracted from package path: 'OMServer.msi'
MSI (s) (D4:A0) [10:21:27:381]: Package to be registered: 'OMServer.msi'
MSI (s) (D4:A0) [10:21:27:383]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableMsi' is 1
MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (D4:A0) [10:21:27:383]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (D4:A0) [10:21:27:383]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (D4:A0) [10:21:27:383]: Running product '{C92727BE-BD12-4140-96A6-276BA4F60AC1}' with elevated privileges: Product is assigned.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding OM_INSTALLDIR property. Its value is 'F:\Program Files\Microsoft System Center 2012 R2\Operations Manager'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding ROOT_MANAGEMENT_SERVER_PORT property. Its value is '5723'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Modifying SC_DB_SERVER property. Its current value is 'OperationsManager'. Its new value: 'SCOM-XXX-AG'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DW_DB_SERVER property. Its value is 'SCOM-XXX-AG'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DWDATABASENAME property. Its value is 'OperationsManagerDW'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Setup'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '4472'.
MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (D4:A0) [10:21:27:383]: RESTART MANAGER: Disabled by MSIRESTARTMANAGERCONTROL property; Windows Installer will use the built-in FilesInUse functionality.
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (s) (D4:A0) [10:21:27:383]: TRANSFORMS property is now:
MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (D4:A0) [10:21:27:395]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming
MSI (s) (D4:A0) [10:21:27:396]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Favorites
MSI (s) (D4:A0) [10:21:27:398]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (D4:A0) [10:21:27:399]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Documents
MSI (s) (D4:A0) [10:21:27:401]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (D4:A0) [10:21:27:402]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (D4:A0) [10:21:27:404]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (D4:A0) [10:21:27:406]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Local
MSI (s) (D4:A0) [10:21:27:408]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Pictures
MSI (s) (D4:A0) [10:21:27:411]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (D4:A0) [10:21:27:413]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (D4:A0) [10:21:27:414]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (D4:A0) [10:21:27:415]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (D4:A0) [10:21:27:417]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (D4:A0) [10:21:27:420]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (D4:A0) [10:21:27:421]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (D4:A0) [10:21:27:423]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (D4:A0) [10:21:27:424]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (D4:A0) [10:21:27:426]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Desktop
MSI (s) (D4:A0) [10:21:27:427]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (D4:A0) [10:21:27:428]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (D4:A0) [10:21:27:428]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (D4:A0) [10:21:27:433]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\4b8344.msi'.
MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi'.
MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'DisableRollback' is 0
MSI (s) (D4:A0) [10:21:27:434]: User policy value 'DisableRollback' is 0
MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
=== Logging started: 22/01/2014 10:21:27 ===
MSI (s) (D4:A0) [10:21:27:435]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (D4:A0) [10:21:27:436]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (s) (D4:A0) [10:21:27:438]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (D4:A0) [10:21:27:438]: Doing action: INSTALL
Action start 10:21:27: INSTALL.
MSI (s) (D4:A0) [10:21:27:444]: Running ExecuteSequence
MSI (s) (D4:A0) [10:21:27:444]: Doing action: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76
MSI (s) (D4:A0) [10:21:27:447]: PROPERTY CHANGE: Adding SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
MSI (s) (D4:A0) [10:21:27:448]: Doing action: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76
Action ended 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
MSI (s) (D4:A0) [10:21:27:450]: PROPERTY CHANGE: Adding System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\system32\'.
Action start 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
MSI (s) (D4:A0) [10:21:27:450]: Doing action: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6
Action ended 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
MSI (s) (D4:A0) [10:21:27:452]: PROPERTY CHANGE: Adding WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 property. Its value is 'C:\Windows\'.
Action start 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6.
MSI (s) (D4:A0) [10:21:27:453]: Doing action: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522
Action ended 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6. Return value 1.
MSI (s) (D4:A0) [10:21:27:455]: PROPERTY CHANGE: Adding System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 property. Its value is 'C:\Windows\system32\'.
Action start 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522.
MSI (s) (D4:A0) [10:21:27:456]: Doing action: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
Action ended 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522. Return value 1.
MSI (s) (D4:A0) [10:21:27:458]: PROPERTY CHANGE: Adding WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\'.
Action start 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
MSI (s) (D4:A0) [10:21:27:458]: Doing action: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
Action ended 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
MSI (s) (D4:A0) [10:21:27:461]: PROPERTY CHANGE: Adding SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\SysWOW64\'.
Action start 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
MSI (s) (D4:A0) [10:21:27:461]: Doing action: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
Action ended 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
MSI (s) (D4:A0) [10:21:27:463]: PROPERTY CHANGE: Adding WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\'.
Action start 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
MSI (s) (D4:A0) [10:21:27:463]: Doing action: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
Action ended 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
MSI (s) (D4:A0) [10:21:27:466]: PROPERTY CHANGE: Adding System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\system32\'.
Action start 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
MSI (s) (D4:A0) [10:21:27:467]: Doing action: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8
Action ended 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
MSI (s) (D4:A0) [10:21:27:468]: PROPERTY CHANGE: Adding WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 property. Its value is 'C:\Windows\'.
Action start 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8.
MSI (s) (D4:A0) [10:21:27:469]: Doing action: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9
Action ended 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8. Return value 1.
MSI (s) (D4:A0) [10:21:27:471]: PROPERTY CHANGE: Adding WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 property. Its value is 'C:\Windows\'.
Action start 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
MSI (s) (D4:A0) [10:21:27:472]: Doing action: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE
Action ended 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 1.
MSI (s) (D4:A0) [10:21:27:474]: PROPERTY CHANGE: Adding WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE property. Its value is 'C:\Windows\'.
Action start 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE.
MSI (s) (D4:A0) [10:21:27:475]: Doing action: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0
Action ended 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE. Return value 1.
MSI (s) (D4:A0) [10:21:27:477]: PROPERTY CHANGE: Adding ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 property. Its value is 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\'.
Action start 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
MSI (s) (D4:A0) [10:21:27:477]: Doing action: FindRelatedProducts
Action ended 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
Action start 10:21:27: FindRelatedProducts.
MSI (s) (D4:A0) [10:21:27:481]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT_AGENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _SearchOpsMgrShellPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 (condition is false)
MSI (s) (D4:A0) [10:21:27:483]: Doing action: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0
Action ended 10:21:27: FindRelatedProducts. Return value 1.
MSI (s) (D4:08) [10:21:27:501]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI847C.tmp, Entrypoint: SetMonadFilePath
MSI (s) (D4:B0) [10:21:27:502]: Generating random cookie.
MSI (s) (D4:B0) [10:21:27:505]: Created Custom Action Server with PID 4964 (0x1364).
MSI (s) (D4:34) [10:21:27:527]: Running as a service.
MSI (s) (D4:34) [10:21:27:529]: Hello, I'm your 64bit Impersonated custom action server.
Action start 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
MSI (s) (D4!DC) [10:21:27:638]: PROPERTY CHANGE: Modifying MONAD_SHELL_PATH property. Its current value is 'Error: Value Never Set. Check the CACore:SetMonadFilePath CA'. Its new value: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'.
GetRegistyStringValue: Registy key value found.. C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
MSI (s) (D4:A0) [10:21:27:640]: Doing action: _Set_CORECOMPONENTPRESENT
Action ended 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
MSI (s) (D4:A0) [10:21:27:643]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
Action start 10:21:27: _Set_CORECOMPONENTPRESENT.
MSI (s) (D4:A0) [10:21:27:644]: Skipping action: _AbortDowngradeProductAttempt (condition is false)
MSI (s) (D4:A0) [10:21:27:644]: Doing action: _AbortIncompatibleComponents
Action ended 10:21:27: _Set_CORECOMPONENTPRESENT. Return value 1.
Action start 10:21:27: _AbortIncompatibleComponents.
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5044 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1580 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5512 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 4268 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5024 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 6064 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 3396 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 2704 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5568 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5940 could not be cancelled. Error: 1168
MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1968 could not be cancelled. Error: 1168
MSI (s) (D4:A0) [10:21:27:652]: Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled to proceed.
The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled to proceed.
Action ended 10:21:27: _AbortIncompatibleComponents. Return value 3.
Action ended 10:21:27: INSTALL. Return value 3.
Property(S): DiskPrompt = Please Insert Disk 1
Property(S): UpgradeCode = {17058653-A628-4C03-8F80-5E2B179ECD55}
Property(S): SCDATABASENAME = OperationsManager
Property(S): SC_DB_SERVER = SCOM-XXX-AG
Property(S): SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
Property(S): CORECOMPONENTPRESENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
Property(S): OM_INSTALLDIR = F:\Program Files\Microsoft System Center 2012 R2\Operations Manager
Property(S): ProgramFiles64Folder = C:\Program Files\
Property(S): Privileged = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): DONOTSKIPDELETESERVICES = 0
Property(S): DONOTSKIPINSTALLSERVICES = 0
Property(S): OM_COMMON_PRODUCT_REGISTRY_PATH = SOFTWARE\Microsoft\System Center Operations Manager
Property(S): OM_COMMON_PRODUCT_RELEASE_REGISTRY_KEY = 12
Property(S): OM_COMMON_PRODUCT_DEFAULT_INSTALL_DIR = System Center Operations Manager
Property(S): NetFxVersion = v2.0.50727
Property(S): IS_OM_SERVER = 1
Property(S): InstallAPMAgent = 1
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): MSIRESTARTMANAGERCONTROL = Disable
Property(S): SQL_PORT = 1433
Property(S): DbSizeGood = 1
Property(S): DbFileOptionsGood = 1
Property(S): DbFilesSpaceGood = 1
Property(S): DbNameGood = 1
Property(S): SqlServicesStarted = 1
Property(S): _SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
Property(S): _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
Property(S): DialogWizardTitle = System Center 2012 R2 Operations Manager Setup
Property(S): MinimumOSMsg = This product must be installed on Windows Server 2008 R2 or higher.
Property(S): MOMSDKPortDesc = Operations Manager SDK.
Property(S): MOMConnectorPortDesc = Operations Manager Connector Framework.
Property(S): MOMAEMPortDesc = Operations Manager Application Error Monitoring.
Property(S): MOMSQMPortDesc = Operations Manager Customer Experience Improvement Program.
Property(S): MOMHSPortDesc = System Center Management Health Service
Property(S): SCOMV3SP1ProgramName = System Center 2012 R2 Operations Manager
Property(S): FWRulePingRequestName = Operations Manager Ping Request (Echo Request - ICMPv4 OUT)
Property(S): FWRulePingRequestDesc = Operations Manager network monitoring ping request
Property(S): FWRulePingResponseName = Operations Manager Ping Response (Echo Response - ICMPv4 IN)
Property(S): FWRulePingResponseDesc = Operations Manager network monitoring ping response
Property(S): FWRuleSnmpRequestName = Operations Manager SNMP Request
Property(S): FWRuleSnmpRequestDesc = Operations Manager network monitoring SNMP request
Property(S): FWRuleSnmpResponseName = Operations Manager SNMP Response
Property(S): FWRuleSnmpResponseDesc = Operations Manager network monitoring SNMP response
Property(S): FWRuleSnmpTrapListenerName = Operations Manager SNMP Trap Listener
Property(S): FWRuleSnmpTrapListenerDesc = Operations Manager network monitoring SNMP trap listener
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {C92727BE-BD12-4140-96A6-276BA4F60AC1}
Property(S): ProductLanguage = 1033
Property(S): ProductName = System Center Operations Manager 2012 Server
Property(S): ProductVersion = 7.1.10226.0
Property(S): SecureCustomProperties = ACTIONSPASSWORD;CORECOMPONENTPRESENT_AGENT;CORECOMPONENTPRESENT_GW;CORECOMPONENTPRESENT_RC;CORECOMPONENTPRESENT_SCE;CORECOMPONENTPRESENT_SMB2;CORECOMPONENTPRESENT_SMRTM;IS_AVICODE_AGENT_INSTALLED;IS_MOMASPAGENT_INSTALLED;MOM_DB_SERVER;MOMDATABASENAME_OLD;OM_NEWER_PRODUCT_FOUND;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650;SQL_PORT
Property(S): MsiHiddenProperties = _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;_SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;ACTIONSPASSWORD;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650
Property(S): WixPdbPath = d:\btvsts\20867\private\product\setup\wix\msi\server\om\obj\amd64\OMServer.wixpdb
Property(S): CORECOMPONENTPRESENT_AGENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
Property(S): ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): MONAD_SHELL_PATH = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Property(S): EnableEV.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = 1
Property(S): AddInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = add
Property(S): RemoveInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = remove
Property(S): WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE = C:\Windows\
Property(S): VersionNT = 602
Property(S): DW_DB_SERVER = SCOM-XXX-AG
Property(S): DWDATABASENAME = OperationsManagerDW
Property(S): OMDATABASENAME = OperationsManger
Property(S): MaximumDataAgeMinutes = 10080
Property(S): MaximumQueueSizeKB = 102400
Property(S): MOMSDKPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 5724
Property(S): MOMConnectorPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51905
Property(S): MOMAEMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51906
Property(S): MOMSQMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51907
Property(S): SDK_SERVICE_TYPE = 4
Property(S): ROOT_MANAGEMENT_SERVER_PORT = 5723
Property(S): SERVER_MANAGEMENT_GROUP_TYPE.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = 1
Property(S): MaximumForwardedVirtualQueuePercentage = 8
Property(S): QueueSendDataSinglePriority = 0
Property(S): ADMIN_ROLE_GROUP.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = Administrators
Property(S): USE_MANUALLY_SPECIFIED_SETTINGS = 1
Property(S): WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 = C:\Windows\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): CAN_REGISTER_FOR_MU = 0
Property(S): MU_SETTING = 0
Property(S): IS_ROOT_HEALTH_SERVICE = 0
Property(S): IS_MOM_SERVER = 0
Property(S): IS_MOM_GATEWAY = 0
Property(S): WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 = C:\Windows\
Property(S): WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\
Property(S): System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\system32\
Property(S): DirectoryTable100_amd64.1C11561A_11CB_36A7_8A47_D7A042055FA7 = DirectoryTable
Property(S): WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\
Property(S): SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\SysWOW64\
Property(S): DirectoryTable100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = DirectoryTable
Property(S): SEND_CEIP_REPORTS = 0
Property(S): System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 = C:\Windows\system32\
Property(S): ACS_AGENT_ACCOUNT.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 =
Property(S): WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 = C:\Windows\
Property(S): SC_COMMON_REGISTRY_PATH = SOFTWARE\Microsoft\System Center\2010\Common
Property(S): DISCOVERY_DATA_AUTHORIZATION_ENABLED = 0
Property(S): IcmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
Property(S): IcmpRequestType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 8:*
Property(S): IcmpResponseType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0:*
Property(S): SnmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 17
Property(S): SnmpPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 161
Property(S): SnmpTrapPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 162
Property(S): DirectionIn.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0
Property(S): DirectionOut.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
Property(S): SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\SysWOW64\
Property(S): System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\system32\
Property(S): ADVISOR_UPLOADFREQUENCY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
Property(S): ADVISOR_UPLOADDAY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
Property(S): ADVISOR_UPLOADTIMEHOUR_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
Property(S): ADVISOR_UPLOADTIMEMIN_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
Property(S): ADVISOR_MAXCACHESIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
Property(S): ADVISOR_MAXMAILBOXSIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
Property(S): ADVISOR_ARCHIVEPERIOD_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #5
Property(S): ADVISOR_LOGLEVEL_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #3
Property(S): ADVISOR_NEEDMPINITIALIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
Property(S): ADVISOR_LYNC_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
Property(S): ADVISOR_SHAREPOINT_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
Property(S): MsiLogFileLocation = C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log
Property(S): PackageCode = {58EFE971-58C1-4DBD-A400-A7607A745475}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): REBOOT = ReallySuppress
Property(S): CURRENTDIRECTORY = C:\Users\scomaction\AppData\Local\SCOM\Setup
Property(S): CLIENTUILEVEL = 3
Property(S): MSICLIENTUSESEXTERNALUI = 1
Property(S): CLIENTPROCESSID = 4472
Property(S): MsiSystemRebootPending = 1
Property(S): VersionDatabase = 300
Property(S): VersionMsi = 5.00
Property(S): VersionNT64 = 602
Property(S): WindowsBuild = 9200
Property(S): ServicePackLevel = 0
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsFolder = C:\Windows\
Property(S): WindowsVolume = C:\
Property(S): System64Folder = C:\Windows\system32\
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Users\SCOMAC~1\AppData\Local\Temp\
Property(S): ProgramFilesFolder = C:\Program Files (x86)\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): AppDataFolder = C:\Users\scomaction\AppData\Roaming\
Property(S): FavoritesFolder = C:\Users\scomaction\Favorites\
Property(S): NetHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = C:\Users\scomaction\Documents\
Property(S): PrintHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): LocalAppDataFolder = C:\Users\scomaction\AppData\Local\
Property(S): MyPicturesFolder = C:\Users\scomaction\Pictures\
Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(S): DesktopFolder = C:\Users\Public\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): Intel = 6
Property(S): PhysicalMemory = 8192
Property(S): VirtualMemory = 7854
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = scomaction
Property(S): UserSID = S-1-5-21-607126847-70518424-489426498-210484
Property(S): UserLanguageID = 2057
Property(S): ComputerName = SCOMMS1-VM
Property(S): SystemLanguageID = 2057
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 23
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 10:21:27
Property(S): Date = 22/01/2014
Property(S): MsiNetAssemblySupport = 4.0.30319.17929
Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): USERNAME = Windows User
Property(S): DATABASE = C:\Windows\Installer\4b8344.msi
Property(S): OriginalDatabase = F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
MSI (s) (D4:A0) [10:21:27:697]: Note: 1: 1708
MSI (s) (D4:A0) [10:21:27:698]: Product: System Center Operations Manager 2012 Server -- Installation operation failed.
MSI (s) (D4:A0) [10:21:27:698]: Windows Installer installed the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.1.10226.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (D4:A0) [10:21:27:744]: Deferring clean up of packages/files, if any exist
MSI (s) (D4:A0) [10:21:27:744]: MainEngineThread is returning 1603
MSI (s) (D4:30) [10:21:27:744]: No System Restore sequence number for this installation.
=== Logging stopped: 22/01/2014 10:21:27 ===
MSI (s) (D4:30) [10:21:27:746]: User policy value 'DisableRollback' is 0
MSI (s) (D4:30) [10:21:27:746]: Machine policy value 'DisableRollback' is 0
MSI (s) (D4:30) [10:21:27:746]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (D4:30) [10:21:27:746]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (D4:30) [10:21:27:747]: Destroying RemoteAPI object.
MSI (s) (D4:B0) [10:21:27:747]: Custom Action Manager thread ending.
MSI (c) (78:34) [10:21:27:748]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (78:34) [10:21:27:749]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/01/2014 10:21:27 ===
Any assistance anyone can provide will be greatly appreciated.Verify from permission of user that you use it in upgrade, make sure that scom machine and user that you use it in upgrade in sysadmin group in database of operationsManager and OperationsManagerDW
Also Verify from Prerequisites of Upgrade SCOM 2012 sp1 as below link
http://technet.microsoft.com/en-us/library/jj656654.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer" -
URGENTLY REQUIRE A CODE FOR FOLLOWING--WOULD BE GREAT HELP
HOW TO VALIDATE XML FILE USING SAX PARSER WITH SCHEMAS like .XSD FILES
Mankjas wrote:
URGENTLY REQUIRE A CODE FOR FOLLOWING--WOULD BE GREAT HELPNo, it wouldn't be a great help, as the next time you needed to do something like this you'd still be lost.
And no one here is just simply going to give you code anyway. We'll help you correct yours, and give you advice and tips, but we are not going to do your work for you. And urgent it is not, not to us. And your insisting that it is, is rude. We definately are not going to drop everything we might be doing to "help" you, especially when your essentially demanding that we do your work for you, with no effort on your part, besides. -
Mac Book Pro just got it, all was well for 2 weeks now Finder window does not fill whole screen, there is an 1 1/2" space of black on the right side and the Finder window had a 1" section that flipped like a rolling tv now it is a white bar! Help!
Bad video card, call Apple, get a case number and return it.
-
SCOM 2012 System Center Operations Manager has stopped working when adding Web Console.
I am trying to ad the Web console to one of my Management Servers but at the point where it asks what website to use it fails with the "System Center Operations Manager Setup has Stopped working error.
This is the included information.
Problem Event Name: CLR20r3
Problem Signature 01: setupchainerui.exe
Problem Signature 02: 7.0.9538.0
Problem Signature 03: 509042f2
Problem Signature 04: System
Problem Signature 05: 4.0.30319.18022
Problem Signature 06: 506a7689
Problem Signature 07: 1cf5
Problem Signature 08: 72
Problem Signature 09: System.UriFormatException
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 79c6
Additional Information 2: 79c63d7b6daeea05a42903612b7137d2
Additional Information 3: 88ec
Additional Information 4: 88ec54f8fa758d8069cdb2ad5cd91e2b
The only error I get in the log file is this.
Error: :Error:IsReportingValidToInstall failed SRS instance not provided
I don't understand why I would be getting an SRS error, our reports run fine.
Thanks,
GaryHi Gary,
Did you end up finding a solution to this issue? The GUI and silent/command line installer are failing for me in the same spot.
App Log Errors:
Application: SetupChainerUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.EnterpriseManagement.Common.ServiceNotRunningException
Stack:
at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(System.Exception)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings,
Microsoft.EnterpriseManagement.Common.Internal.SdkChannelObject`1<Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService>)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings,
Microsoft.EnterpriseManagement.DataAbstractionLayer.ClientDataAccessCore)
at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(Microsoft.EnterpriseManagement.EnterpriseManagementConnectionSettings, Microsoft.EnterpriseManagement.ManagementGroupInternal)
at Microsoft.EnterpriseManagement.ManagementGroup.Connect(System.String)
at Microsoft.SystemCenter.Essentials.SetupFramework.WebConsoleSite.GetValidationProperties(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Faulting application name: SetupChainerUI.exe, version: 7.0.9538.0, time stamp: 0x509042f2
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16656, time stamp: 0x5318237f
Exception code: 0xe0434352
Fault offset: 0x00000000000043c8
Faulting process id: 0x638
Faulting application start time: 0x01cf9a697847d9c8
Faulting application path: C:\Users\szb\AppData\Local\SCOM\SetupChainerUI.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c52d5d75-065c-11e4-80c2-00155dcb0b37
Faulting package full name:
Faulting package-relative application ID: -
VMM 2012: How to Configure Automatic Start and Stop Actions for a Virtual Machine?
Does somebody know how to confgure Automatic Start and Stop Actions for a Virtual Machine in VMM 2012?
I miss that option.Automatic Start or Automatic Restart actions are available for virtual machines running on a Hyper-V cluster from within Virtual Machine Manager.
From within Virtual Machine Manager, bring up the Virtual Machine's properties:
Click "Hardware Configuration"
Click "Availability"
Click "High", "Medium", or "Low" to enable automatic start/restart or
Click "Do not restart automatically" to disable automatic start/restart
Screenshot from VMM 2012 for a VM running in a Server 2012 R2 Hyper-V cluster:
VMs running on a cluster have to be marked "Highly Available" and logically, Microsoft assumes that you'll want these VMs to be running all the time when this setting is selected. If the cluster fails or needs to be restarted, you can set the priority
by which a VM restarts, or you can set the VM to not restart at all when cluster services are restored by using the settings above. -
Required Ports to connect remote SQL named Instance for SCCM 2012 R2
Hi,
I have allowed the TCP 1433,1434,135 and 80 but still unable to connect the remote SQL named instance DB for the SCCM 2012 R2... and getting below error..can you please suggest if any other port required for the same, i have turned off the windows
firewall and RPC service is running ob Remote SQL and SCCM 2012 R2 server..
CCMsetuplog
Shailendra DevDuring the installation you need more ports. You would also need the (dynamic) RPC ports. See for a complete list (section Site Server --> SQL Server):
https://technet.microsoft.com/en-us/library/hh427328.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Planning System Center Operation Manager 2012 R2 on SQL 2012 Active/Passive Cluster
Dears,
I'm planning to deploy System Center Operation Manager 2012 R2 on SQL 2012 Active/Passive Cluster which have other sql instances running for other applications. And i'm planning to create a new instance for SCOM, kindly provide me recommendation
whether i can install all sql databases for SCOM on same sql instance or does it require separate instances for opsmanger database , dw database and ACS database?
Thanks in advance..Hi,
Yes, all SCOM SQL databases can run on the same instance of SQL server.
As well, look at some helpful posts for the topic:
http://technet.microsoft.com/library/dn281933.aspx
http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.aspx
Natalya
### If my post helped you, please take a moment to Vote as Helpful and\or Mark as an Answer -
SCOM 2012 Global Architecture, One management group or multiple?
Hi Folks,
I work for a global firm, we have multiple data caters in different regions. America, UK, Australia, China etc etc. We are looking to roll out SCOM 2012 for monitoring all systems. Our environment
1,000 Windows servers
All servers on the same Active Directory domain
10 Mbps links between data centers.
My question is around whether to use multiple management groups or one? I’ve seen recommendations for both. For example
In the Infrastructure Planning and Design guide for SCOM 2012 it is stated:
“A centralized management model with large remote locations works best with a management group in each region and a local management group (which provides a consolidated view of alerts and status) in the parent location. In this case, the centralized management
group connects through the software development kit (SDK) and functions as an additional console on each of the connected management groups.”
However moderators in this forum have stated
“Each management group has its own set of SQL Servers and Management Servers \ Gateways. It also adds considerably to administrative overhead. I'd try to avoid
multiple management groups where possible.”
” It will get expensive in terms of hardware and software with multiple management groups and you will duplicate a lot of work with regards to overrides”
“If you go with multiple Management Groups then you would need to add on a fair number of SQL licenses plus additional hardware. “
“Presumably if I have multiple management groups will that mean I will have to
create rules for each Management Group- correct. Same
with overrides. It could add a lot of administrative overhead. “
It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance. I’ve heard
stories about SCOM deployments architected in this way not performing well because of network latency. i.e admins from all regions besides the region local to the SCOM deployment not wanting to use SCOM because application performance is too slow.
What would the SCOM experts recommend for this scenario?
MH1) My question is around whether to use multiple management groups or one?
Factors to consider in determine the number of Management group
• Scaling
• Agents separated from their management server by WAN-speed network links
• Political, administrative or security requirements within the organization requiring separate management groups.
• A view of AD DS topology required across multiple forests.
• A dedicated management group required for auditing purposes.
• Disaster recovery functionality required.
• Consolidated views of connected management groups required in Operations Manager.
• Operations Manager integration with the VMM console.
With refer to your situation
a) 1,000 Windows servers
b) All servers on the same Active Directory domain
c) 10 Mbps links between data centers.
It is suggest that one Management group is required.
2) It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance
It is recommend that you should deploy Gateway server in region office which has more than 10 agents.
• Gateway server reduce network bandwidth utilization. Agents located across WAN links consume network bandwidth, potentially affecting service delivery to and from the remote location. A gateway server can consolidate the traffic.
Roger -
Operations Manager failed to run a WMI query-Invalid class
Hi Team,
may of the windows 2008 R2 sp1 and sp2 servers getting below SCOM 2012 alert. Please help me to fix the same.
SCOM version : SCOM 2012 R2
Alert: Operations Manager failed to run a WMI query
Source: server Name
Path: server Name
Last modified by: System
Last modified time: 2/6/2014 8:33:22 AM
Alert description: Object enumeration failed
Query: 'SELECT * FROM MetaFrame_Server WHERE ServerName="server Name"'
HRESULT: 0x80041010
Details: Invalid class
One or more workflows were affected by this.
Workflow name: Citrix.PresentationServer.ActiveSessions.PerformanceMonitorFirst try it with WBEMTEST to see what is going with the WMI class. The error you are getting usually means WMI misses that class and you should load the mof again/ maybe rebuild the entire repository (careful as the windows files are all located
on 1 folder, but applications tend to store it in their own folders, like citrix, ibm, etc).
Try to run this command:
mofcomp "<Programfiles>\Citrix\System32\Citrix\WMI\ .Mof file for citrix"
{citrixProv.XP10FR3.mof, metaframeProv.XP10FR3.mof, and mgmt.XP10FR4.mof files}
Then, run the WBEMTest again and the namespace should be returned successfully. Then restarting the health service on agent.
Also you can refer below link
https://support.citrix.com/article/CTX122283
Please remember, if you see a post that helped you please click (Vote As Helpful) and if it answered your question, please click (Mark As Answer). -
Purpose of certificate in the Operation manager store - ADCS server.
Hello,
I do have win 2003 ADCS server. When I do mmc snap in for local computer, I can see one of the certificate under operation manager expiring soon.
Can anyone please tell me the purpose of operation manager store - ADCS server.
ThanksHi,
The Operations Manager store is used to contain certificates which are used for securing communication between Operations Manager servers across untrusted domains.
For more detailed information, please refer to this blog below:
Operations Manager - Certificates from Concept to Deployment
http://blogs.technet.com/b/denisrougeau/archive/2014/09/02/operations-manager-certificates-demystified.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] -
Issues with Thunderbolt-HDMI connection on Mid-2012 MacBook Pro
I have a 2012 MacBook Pro (non-Retina display) and just bought a thunderbolt-HDMI connector, but it's not working. A screen appears on the TV, only it's not my desktop screen, but the standard galaxy image in most Macs. Any idea how to fix this issue?
Your TV is extending your desktop. You can drag some of your windows off of the MBP internal screen onto the TV. You can control how the two screens are related spacially at System Preferences > Displays > Arrangement.
If you want the two screens to show the same picture, you should turn off "mirroring" on that same setting page. -
Operations Manager not updating IP phone location changes
We have Cisco Unified Operations Manager and we noticed that for some time IP Phone location changes were not registered and updated.
There are couple of phones in All IP Phones/Lines list which are listed as still connected to old switches, while actually moved to completely new switch on different location .
Also - in Devices>Device Management>Inventory Collection>IP Phone IP Phone Collection Status is always : "Discovery in progress..." with Last Collection Start Time and Last Collection End Time from couple of months ago...
We have discovered two old bugs CSCsw26833 and CSCsv33965, but Restart PIFServer, pdterm PIFServer followed by pdexec SRSTServer and checking of netstat connection did not change anything...
What could be a problem, how can we start IP Phone collection?Hey George, thanks for the reply!
Yes, you are absolutely correct. If I set Device Mobility Mode from Default to Off, the phone re-registers and the correct time for that time zone is displayed...!
Awesome, thanks again George. Much appreciated!
Thanks Again,
Matt -
SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster
I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
Node1: DB Engine 1 (named instance DB01)
Node2: DB Engine 2 (named instance DB02)
Node3: Analysis Services (named instance DBAS)
Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
Thank you much for reading. I appreciate any help to get this resolved.
POSSIBLY NOT RELEVANT...?
I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
help solve the issue.When connecting to SSAS in a cluster, you do not specify an instance name. In your case, you would use the name of the SSAS IP address to connect.
See:
http://msdn.microsoft.com/en-us/library/dn141153.aspx
For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
"SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
How to Cluster SQL Server Analysis Services for more information and examples.
Maybe you are looking for
-
How can I reduce a fotobook pdf size for online printing
Hello aperture, I have been creating a large customer book (33 x 28 cm) with aperture. I'm working with RAW datas and the fotobook has got around 150 pages. My online printing office accepts only PDF X3 2002 datas and I can get this with adobe acroba
-
Hello, Does anybody know how to rotate several photos at the same time? Thanks Yanina
-
I sometimes get "ghost" rating stars against tracks. how can i delete these?
sometimes get "ghost" rating stars against tracks. how can i delete these?
-
Could not load Displays preference panel?
Hi I need some help. I keep getting the following error when I try to open the Desktop & Screen save or the Displays Preference panel in the System Preferences. Ive just purchased the device and Its a new MacBook Pro (Retina, 13-inch, Mid 2014), 3 GH
-
Performance Optimization for Collection
I have a query with fetches the data as a Record Type in the form of an Array like below :- SELECT <Long_Column_List> FROM (TABLE(<Schema_Name>.<Package_Name>.<Function_Name>))y Where the Function Returns a PLSQL table type. This approach we had take