Identifying the Root Management Server in Operations Manager 2012
Hello,
I want to replace my primary management server.
Do i need to do the following steps if i have SCOM 2012??
https://technet.microsoft.com/en-us/library/cc540401.aspx?f=255&MSPPError=-2147217396
Promote a management server to a root management server role
Configure the reporting server with the name of the new root management server.
Configure the Web console with the name of the new root management server.
Set ENABLE_BROKER to 1 if needed
Thanks!
TechNet
Hello,
I am not sure i understand how it works.
The SQL server and the Application server are at the same domain (no firewalls) but not on the same server.
The reporting are installed on the SQL server.
We only have one domain admin account that is running on "data warehouse report deployment account"
At the reporting configuration manager, it's the correct report link.
At the reporting server i can see that at the :"c:\ProgramFiles\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer" there is a file
called "reportserver", inside this file i can see the FQDN of my primary SCOM Server under "Security" and "Authentication" sections.
Is that why the reporting URL doesn't work when the primary server is down?
Remember - i set the RMS emulator to a different server.
If i need to change that manually then the first Q i have ask is relevant also for SCOM 2012.
Thanks.
TechNet
Similar Messages
-
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" -
Unable to start Manager server using Node Manager
Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager. -
Adding patch jar file while starting Managed Server through Node Manager
Hi,
I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
Weblogic ConsultantThanks for your response.
I found another way to do this.
Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
Weblogic Consultant -
Starting managed server using node manager
When i try to start the managed server using node manager i get the following error
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Abort - core dumped
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <Waiting for the process to die: 22708>
<Sep 21, 2010 3:58:07 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The managed server lok file is deleted, port is not in use. With similar node manager settings the managed server on the redundant server starts fineHi,
I am getting same issue. Not able to start the soa_server1. Can you pleae tell me the soulution if you able to reslove the issue.
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\Oracle\MIDDLE~1\JROCKI~1.0-6\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle\Middleware\user_projects\domains\domain2\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dcommon.components.home=D:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1 -Doracle.server.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\servers\soa_server1 -Doracle.security.jps.config=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\carml -Digf.arisidstack.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=D:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djava.protocol.handler.pkgs="oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol" -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=D:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.102:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 700>
<Oct 4, 2010 6:25:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters> -
Starting Manage Server using node manager
Hi,
Hi,
I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
plz help me out in this
Thanks in advanceAn example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
"By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped." -
Can we deploy Antimalware Policy Operations Manager 2007 to Operations Manager 2012?
Can we deploy Antimalware Policy Operations Manager 2007 to Operations Manager 2012?
Hi,
Yes, you can check, you can update it to match the informaton here:
http://blogs.technet.com/b/manageabilityguys/archive/2013/11/26/system-center-2012-r2-operations-manager-anti-virus-exclusions.aspx
Reagrds,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
How to identify the installed Weblogic Server and JDK are 32bit or 64bit?
Hi everyone,
I have a question ~
Both Weblogic Server and JAVA JDK are installed on the server already, but I only know the Weblogic Server is 10.3.4.0 and JAVA JDK version is 1.6.0_25.
I know the 64bit Weblogic Server installation file is a wlsXXXX_generic.jar package and 64bit JAVA JDK needed also.
But, since the Weblogic installed already, there are no such installation files on the Linux Server now.
I have tried the "java -version" for java version and check the Weblogic version from Weblogic console.
How to identify the installed Weblogic Server and JDK are 32bit or 64bit with Linux command? Or is there any way to check it?What you can try to do is use WLST (or an MBean browser, such as JConsole or JRockit Mission Control) and connect to the adminserver.
For example when using WLST:
# set the environment by using setWLSEnv.sh (located in the ${WL_HOME}/server/bin directory).
# start WLST by using: java weblogic.WLST
# connect to the adminserver
connect('adminusername','adminpassword');
# change to the serverruntime environment
serverRuntime();
# show the attributes
ls();
# Here an attribute is shown called WebLogicVersion that shows the version of WebLogic
-r-- WeblogicVersion WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
# Note that this does not show if is 32 bits or 64 bits to retrieve this information you have obtain the JVM version
# change the directory
cd('JVMRuntime/AdminServer');
# show the attributes
ls();
-r-- Version R28.0.1-21-133393-1.6.0_20-20100512-2126-linux-x86_64
# when you have something like x86 at the you are running a 32 bit version, if you have something like x86_64 you are running a 64 bits versionAs mentioned above you can also retrieve this information by using a MBean browser. -
Problems while starting the Managed Server through Node Manager..
When I was trying to start a Managed Server using the Nodemanager , I am getting the following error :
NodeManager not configured to receive commands from host : emis-develop
I have the "nodemanager.hosts" file under the directory "c:\bea\wlserver6.1\config" and even while invoking the script for the startnodemanager , I am indicating this in the script ! Any ideas for this problem ??The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj -
While Starting the Managed server using node manager
The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328874> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328874> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Info> <WebLogicServer> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
####<Nov 24, 2010 11:12:22 AM IST> <Error> <NodeManager> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000d> <1290577342764> <BEA-300048> <Unable to start the server soa_server1 : Exception while starting server 'soa_server1'>
And the state of server is "FAILED_NOT_RESTARTABLE". Please help me in this
Regards
VeenaThe system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj -
Error when trying to start managed server from node manager
I have a managed server which is authenticated through a WeblogicAuthenticProvider. When starting the managed server from command line I need to setup certain jars in the classpath in order to start it successfully. However when I try and start the managed server from a node manager, I receive the following error.
Any ideas as to what is going on are appreciated. Is there any way to force Weblogic Node manager to invoke the actual startManagedWeblogic.cmd when bringing up the managed server
Thanks
<Jun 5, 2006 9:21:05 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server TweCluster::TaxwareServer1 ...>
<Jun 5, 2006 9:21:07 AM EDT> <Info> <NodeManager@*.*:5555> <Server TweCluster::TaxwareServer1 started, process id = 3,012>
<Jun 5, 2006 9:21:11 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://zeus3dev:7001 to check if there exists a running admin server at this URL.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://zeus3dev:7001 to retrieve the initial configuration.>
<Jun 5, 2006 9:21:16 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\bea8.1\weblogic81\common\nodemanager\TaxwareServer1\TaxwareServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/taxware/twe/util/crypto/CryptoUtil
at com.taxware.twe.auth.server.GenericPrincipalValidator.<init>()V(GenericPrincipalValidator.java:41)
at com.taxware.twe.auth.server.WeblogicPrincipalValidator.<init>()V(WeblogicPrincipalValidator.java:38)
at com.taxware.twe.auth.server.WeblogicAuthenticationProvider.getPrincipalValidator()Lweblogic.security.spi.PrincipalValidator;(WeblogicAuthenticationProvider.java:188)
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:154)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: com/taxware/twe/util/crypto/CryptoUtilFound a workaround:
Manually, add PATH (and probably the other environment variables also) to
${WLS_HOME}/common/bin/commEnv.sh. -
Stop managed server without node manager and admin server
What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AMHai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu -
Problem starting managed server using Node Manager/WL 7
I have just configured Node Manager for the first time to start a managed server,
following the documentation 'Managing Server Availability with Node Manager'. However
when I attempt to start the managed server from the Administration Console I always
get the following exception:
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <Starting
Server webdevDomain::apps ...>
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <BaseProcessControl:
saving process id of Weblogic Managed server 'apps', pid: 15094>
Starting WebLogic Server...
Connecting to http://198.242.140.49:17043...
<Jul 10, 2002 1:59:32 PM EDT> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:weblogic.management.configuration.ConfigurationException:
Exception encountered connecting to http://198.242.140.49:17043/wl_management_internal2/Bootstrap
- with nested exception:
[java.io.StreamCorruptedException: InputStream does not contain a serialized object]
java.io.StreamCorruptedException: InputStream does not contain a serialized object
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:844)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:163)
at weblogic.management.ManagedServerAdmin.bootstrapLocalServer(ManagedServerAdmin.java:212)
at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:122)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:665)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
But I am able to start the managed server using the startApps.sh script with no problems.
I am running WL 7 on Solaris 2.8. All processes are running on the same host.
Any help is appreciated!
JohnRe-installing WL Server 7.0.0.1 resolved this problem.
- John -
Starting Managed Server using Node Manager Command Line
Hi,
I've configured the Node Manager and it is connected to the Admin Server without problem. Now I wanted to start the Managed Server through the console but it is failing and my guess is the command line used syntax is not correct.
My question is, how do I change the command line that Node Manager uses to start the Managed Server? I've try using the Server Start tab configuration and it seems like not working. I've also try to update the .properties file for the Managed Server as well.
Each time I look at the Managed Server logs, it is giving me this line...
NodeManager> <Starting WebLogic server with command line: <....>
The command line shown in the logs are not what I've put in the .properties file or the Server Start tab. It is taken from somewhere and I'm not sure where. I just want to configure the command line that Node Manager uses to start a Managed Server.
Hopefully, I'm clear with my problem and someone might be able to assist. Thanks.Great stuff!!
It actually solved my problem. Thanks.
Am just wondering why it didn't work using option 1)? If anyone somehow knows the reason, if not at least it did work for me now. -
Reg: Configuration of Managed Server through Node Manager
Hello:
I have a question Regarding the System properties (-Dname= value
pairs) that are passed when starting the Managed Servers.
In the managed Server script I am passing below two name value pairs
when starting the managed server
-Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
I am able to see these variables as <java System variabales > in the
weblogic.log corresponding to managed server.
Next is starting managed server through the node manager. Now in this
case the Node managed recives the configuration
of the managed server from the Administration server and he then
starts the managed server.
Now my question is though I have changed the startup scripts of
the Managed server to include the above two name value pairs. But I am
not able to see them in the congfiguration file in NodeManagerLogs
corresponding to the Managed Server. Also even in weblogic.log
corresponding to the Managed Server.
Can any one clarify this. Also How to define the new system variables
for the Managed Server so that I can see them in the configuration
file that Adminitration Server sends to the Node Manager.
Thanks,
VijayThanks Anand.
"Anand Byrappagari" <[email protected]> wrote:
Vijay,
When you say managed server scripts do you mean startWeblogic.cmd ?
If you are using the node manger to start the managed servers then these
scripts are not executed. You should set the properties in the console.
Goto YourDomain>Servers>YourManagedServer in the console.
Select "Configuration" tab.
Then select "Remote Start" tab.
In the "Remote Start" tab enter the properties in the "Arguments" field.
-- Anand
"Vijay Kumar" <[email protected]> wrote in message
news:[email protected]..
Hello:
I have a question Regarding the System properties (-Dname= value
pairs) that are passed when starting the Managed Servers.
In the managed Server script I am passing below two name value pairs
when starting the managed server
-Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
I am able to see these variables as <java System variabales > in the
weblogic.log corresponding to managed server.
Next is starting managed server through the node manager. Now in this
case the Node managed recives the configuration
of the managed server from the Administration server and he then
starts the managed server.
Now my question is though I have changed the startup scripts of
the Managed server to include the above two name value pairs. But Iam
not able to see them in the congfiguration file in NodeManagerLogs
corresponding to the Managed Server. Also even in weblogic.log
corresponding to the Managed Server.
Can any one clarify this. Also How to define the new system variables
for the Managed Server so that I can see them in the configuration
file that Adminitration Server sends to the Node Manager.
Thanks,
Vijay
Maybe you are looking for
-
Someone please tell the solution . Is it a hardware issue or os
-
Using In Design on a MAC printing to a Canon MFP to make 8.5 X 5.5 Booklets. My design is 8.5 X 5.5 but the result when it prints is a reduced image of the pages. Any thoughts?
-
Hello, I would like to create an extention that will help to manage a glossary. First I need to decide on the structure of the xml document that will contain all glossary entries. Since I don't have much experience with XML in extention content, I wa
-
Is this a bug within the iMovie? This seems as if it should be extremely simple. I recorded a movie with my iPhone 4. iPhone records that in the standard apple MOV format. I can play the file in Quicktime. However, when I try to drag and drop it
-
Search all Database to find a word
Hello all, I want a pl sql query to find a word like "book" in all oracle database, in all tables and their contents. Thanks in advance Arvin