Operation Manager health score range issue.
Hi,
Our vCOPs version is 5.8.4-build2199700.
In recently, when I check the vCOPs discovered a problem.
In the red box, the normal maximum score is higher than 100.
I'm looking for the documents, there is no related the "Normal Score" why more than 100.
Who can let me know, why the "Normal score" will be greater than 100 to happen?
Thanks for any help and clues.
Nat
Graph the "Badge > Health" score over the past 30 days.. zoom the Y-axis to the 90-110 range. Did the health value actually exceed 100 at any point?
Similar Messages
-
Hi guys
I am currently performing a distributed, complex upgrade with a customer:
4 management servers (1 being RMS), both databases (OM & DW) on a single SQL Server (2008 R2 SP2)
We moved over the RMS role to another server and decomissioned the old one due to it being a 2003 server.
Then we upgraded all non-RMS management servers.
We had some issues with them as well (same error in the log), but when we reinstalled the 2007 R2 binaries & patches and redid the upgrade it came through fine.
The RMS however keeps throwing the same error. Things I tried:
- Full clean of the server including momclean and msizap, then reinstall the RMS and retry the upgrade
- Reregister of the msiexec server
I am suspecting some issues with assemblies and / or GAC, but no clear proof on that, only that it crashes after performing assembly operations.
Below an extract from the RemoveMOMServer.log (the error occurs when uninstalling SCOM 2007 R2)
Can anyone help out or give me some pointers on possible causes?
Many thanks in advance!
MSI (s) (F4:CC) [15:43:55:259]: Executing op: UpdateEstimatedSize(EstimatedSize=0)
MSI (s) (F4:CC) [15:43:55:261]: Executing op: ProductCPDisplayInfoRegister()
MSI (s) (F4:CC) [15:43:55:263]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommit,,)
MSI (s) (F4:CC) [15:43:55:264]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommit,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (F4:CC) [15:43:55:266]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall,,)
MSI (s) (F4:CC) [15:43:55:266]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,CustomActionData=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe uninstall "Microsoft.EnterpriseManagement.OperationsManager,
Version=6.0.4900.00, Culture=neutral, PublicKeyToken=31BF3856AD364E35"€500€C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe uninstall "Microsoft.EnterpriseManagement.OperationsManager.Common, Version=6.0.4900.00, Culture=neutral, PublicKeyToken=31BF3856AD364E35"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe
uninstall "C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.UI.Foundation.dll"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall "C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe
update /queue€500€C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe update /queue€500)
MSI (s) (F4:CC) [15:43:55:268]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall,,)
MSI (s) (F4:CC) [15:43:55:268]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (F4:CC) [15:43:55:270]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=Feature: [1])
MSI (s) (F4:CC) [15:43:55:270]: Executing op: FeaturePublish(Feature=MOMServer,,Absent=3,Component=@+h863e0NAgaZ7OoE1)HM[lp(tNC_AUZ$SF(D`%aFTE9fFyfs=F=$JG3?U4%Jg+a[OgIJ9l,ltBUJ6}nEPr^ulwB]8CeSrDJOg^Dv6-5{b^j}@^?vz.j7,3M6C%7,*@eo93k8pr6&&N9$znhtI3,f=ds,sbkr{FsK5s,aat+W9Luq^c2T)%]NK-`Nh95Q?1j(Dg@M-ujVqmWklfnQ9{a+G7w.5xHY-FhkL+vZAB~5y'c@}'jr8WIsm`xe=5orHD{+mjmr3jr^W2UX?7PmxUa@v*Z]~U%@4u.j?-mBUeMsh74(}?767KRj@A72,VR{&Ndp=1kRf[ZQAWW2Vmir6O-EYNi`aVy0=sY*I`g=~^zgj-K41CWIAn3+(O4}ZvX8=hVDIvD^A&7iGA]RjL$JKo'QVT)b@Y@NcD-awAKEm,xN7,?,Ad7cW2b8}K?@`XVc]R`h8k*+PKa=CULr]CV`GY24=J**5wT+^.,Yw,vNCs'_A95dR?W8yIC[JXIm!nzq@5?Enk}PZewbi(r&t1H!94?5m0NzSd96@yq+0'^.?}G.RFEU^J@e`)a-_.e4@W?a@,yfmDTR]^+cbWf.=hV2Lk`!5yfUciqXO0JF?wIvuYFC{LBr*ENyKNMv9@3O~EdzJ!$jxy*dl]uq8{j_GLM1aC_g[-UdCQiC90o{ZS=lW(WUciqXme3eSKW@5fYZQ*R{[[yk0@XZAwJAUIK=yaPrb5j3zZII9*^7LD'L6,,V{p7-suLJ?`v(5R1a5&ko,1X$zkt~8Ic75fYZQ*RaE1v.2pOX8dqQ4PWI)'Vx5^d6cT~W@m1M]xA+z~*JWKX5swUG9JO-4h}&rH2H%obQfhOk?@2$kky4Qx]3yC3vPpLx@bP%U&2$(719F%lc[~}z8HzR.HDHZ)c]{SAz-boA9DSkLX$,eI5Tm1KmpVu+AzEhUp4Ka@(9k~3kSgQX@N@a@gaH@B-,TlvgYR`J9ET02Ay.r4F*v&OktBzm?8g^(@8)Udj
MSI (s) (F4:CC) [15:43:55:273]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (F4:CC) [15:43:55:273]: Executing op: CleanupConfigData()
MSI (s) (F4:CC) [15:43:55:273]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=0,Remove=0)
MSI (s) (F4:CC) [15:43:55:276]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (F4:CC) [15:43:55:280]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=80035200)
MSI (s) (F4:CC) [15:43:55:280]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager,fileVersion="6.1.7221.99",version="6.0.4900.00",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",
AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:280]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:281]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:289]: Verifying accessibility of file: Microsoft.EnterpriseManagement.OperationsManager.dll
MSI (s) (F4:CC) [15:43:55:291]: Using source file security for destination.
MSI (s) (F4:CC) [15:43:55:304]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:304]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:305]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:306]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:306]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:307]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:308]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:308]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:310]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:310]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:310]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:312]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:59:483]: Internal Exception during install operation: 0xc00000fd at 0x0000000077C24EDC.
MSI (s) (F4:CC) [15:43:59:483]: WER report disabled for silent install.
MSI (s) (F4:CC) [15:43:59:483]: WER report disabled for non-console install.
MSI (s) (F4:CC) [15:43:59:483]: Internal MSI error. Installer terminated prematurely.Thanks for you updating! For SQL related issue, please post on the following forum:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards,
Yan Li
Regards, Yan Li -
Operations Manager powershell health check on specific items
Hello,
I am trying to write up a Operations Manager PowerShell script that runs automatically and checks the current health status of a group object but only the health status of certain columns listed in the Operations Manager such as "Agent" or "Windows
Server 2008 Logical Disk". I have written up the following after setting the group object whose health I wish to check in Operations Manager to "$gp". Also note I am only looking for systems in that group object that show an unhealthy state
hence I put in the "Where-Object" to look for anything that is not showing a healthy status.
Get-SCOMMonitoringObject -Group $gp | select HealthState,Displayname | Where-Object {$_.HealthState -notlike "Success"}
This brings back the overall health state of each system in the group object but I do not want the overall health. I wish to only see the health status of say the "Windows Server 2003 Operating System" column in Operations Manager for those systems.
I would like to know if there is a simple way to accomplish this using the built in Powershell cmdlets which come with Operations Manager when it installs. If I could also get an example of what the syntax of this would look like that would be a great help.
Thanks!Thank you for the responses!
I am currently running the 2012 edition of System Center Operations Manager.
The above code posted by
Alexey Zhuravlev runs for me but it does not seem to be passing anything through for the health state. All I get is a list of the system names but no health state. I believe this is because the Get-SCOMClass cmdlet does not have a "HealthState"
field to pass. It does have a "Status" field which I am wondering if that might work for me if I pipe in maybe the name of the system I would like to view.
I will continue on and play around with what I have so far.
Any further help would be greatly appreciated! -
Operations Manager 2012 R2 Management Pack importing issue
Hi
I seem to be having an issue importing certain management packs, when i do i get the below error:
Windows Server 2008 Operating System (Monitoring) could not be imported.
If any management packs in the Import list are dependent on this management pack, the installation of the dependent management packs will fail.
Verification failed with 2 errors:
Error 1:
Found error in 2|Microsoft.Windows.Server.2008.Monitoring|6.0.7296.0|Microsoft.Windows.Server.2008.Monitoring|| with message:
Could not load management pack [ID=Microsoft.Windows.Server.2008.Discovery, KeyToken=31bf3856ad364e35, Version=6.0.7296.0]. The management pack was not found in the store.
: An error occurred while loading management pack b4bda654-49bd-6e04-ca24-e152fc227001 from the database
Error 2:
Found error in 2|Microsoft.Windows.Server.2008.Monitoring|6.0.7296.0|Microsoft.Windows.Server.2008.Monitoring|| with message:
Could not load management pack [ID=Microsoft.Windows.Server.Library, KeyToken=31bf3856ad364e35, Version=6.0.7218.0]. The management pack was not found in the store.
: Version mismatch. The management pack ([Microsoft.Windows.Server.Library, 31bf3856ad364e35, 6.0.6957.0]) requested from the database was version 6.0.7218.0 but the actual version available is 6.0.6957.0.
Please can someone advise.
Regards
AdrianHi,
Solution: An exception is thrown while importing the Red Hat Linux Management Pack for Operations Manager 2007
http://blogs.technet.com/b/operationsmgr/archive/2010/12/15/solution-an-exception-is-thrown-while-importing-the-red-hat-linux-management-pack-for-operations-manager-2007.aspx
Based on this case, the issue might be resolved by re-importing the Microsoft.Windows.Server.Library Management Pack.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
Hi Community,
I submitted this question because I'm a bit stuck with SCOM 2012 R2, I'll try to explain briefly what is happening right now in my environment, we have a DEV SCOM Deployment in which all the roles are installed in a single server, this servers is a
VMware machine running Windows Server 2008R2.
The Initial installation of the SCOM Operations Manager and all the other components was not performed by me but by a co-worker, unfortunately he doesn't remember much about the initial configuration. So i had to pickup where he left things about a year
ago, neither of us are SCOM experts, and we have almost no previous experience with previous versions of this application.
Now the problem that I'm facing is the following, all the DEV Servers are Domain Controllers and one of the indication within the "Guide for System Center Management Pack for Active Directory for Operations Manager 2012" states the following
Configuration
Supported?
Agent-less monitoring
No
After my first review I notice that our servers were being monitor by agent-less mode and given the above statement from the Operations Guide the only way that we could ever get those domain controllers monitor by SCOM would be by installing the agent on
each server, so I read somewhere (Can't remember where) that in order to install the agents in all the servers I should first remove them from the Agent-less node, which I did. Then I tried to use the discovery wizard to get the agent install in all of them
but it didn't matter how many times I try the servers never show up.
I read in a Tech Net Article that you had to modify the security settings so SCOM would let me decide if I wanted to approve it or not.
--> http://technet.microsoft.com/en-us/library/hh212853.aspx
I performed the suggested steps from the article but still the servers were not showing up, not even if I run the Discovery wizard, so I decided to go and perform the installation manually in a couple of servers I was able to install the agent in one of
the Domain Controllers, I configured the agent to use a service account that has Domain Admin rights. An hour after I installed the agent I went back to the Operations Console Manager and I check under Pending Action but the Server was not showing up. So i
went back to the Internet to try to find out if someone else had experience the same problem, and in one website some mentioned that if the servers were not showing up it was probably because they were still register in the SCOM Database, now I have no idea
of how i can check that or How can i remove them from there to have them available again, but what troubles me the most is that even after i installed the agent manually the server were not being recognize.
I went to the Event Viewer and I found one particular event that caught my attention, see below :
Log Name: Operations Manager
Source: Health Service Modules
Date: 6/12/2014 12:48:19 PM
Event ID: 11551
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MyManagementServer
Description:
Computer verification failure for Machine Name: MyManagementServe is 0x800706BA. The RPC server is unavailable.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Modules" />
<EventID Qualifiers="49152">11551</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-06-12T16:48:19.000000000Z" />
<EventRecordID>1945680</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>MyManagementServer</Computer>
<Security />
</System>
<EventData>
<Data>MyManagementServe</Data>
<Data>0x800706BA</Data>
<Data>The RPC server is unavailable.</Data>
</EventData>
</Event>
Not sure if this is related to the problem that I'm facing right now, but , I make sure that the RPC Services were running and also the related dependencies too. There's no Firewall enable in any of the servers and DNS seems to be working properly.
Ports 135 / 5723 are open and listening so since I ran out of ideas, I would like to know if some of the experts in this field could perhaps give me some guidelines.
There's one caveat that I haven't mention yet and that is related to SQL, I checked and my user just has read access to SQL i'm not sure if that could affect this but i think is worth mentioning.
My main goal is to have all the servers showing up in the Operations Manager Console.
So thanks all in advance !
Oscar LoriaSo you can ping and nslookup from your ms to these agents and vice versa right? I wouldn't do a manual install, I would push the agent from the management server. You can uninstall the agent manually, or use cleanmom to get rid of them. Then
do an install from the console. When you initiate the install from the console (management server), should it run into any issues it will dump out an error which will give you an idea of where the problem may be.
From Holmans post on this:
e MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
The MOM Server could not execute WMI Query "(null)” on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access. If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed. We need port 135 (RPC) and the DCOM port range opened for console push through a firewall.
3. Inspect WMI service, health, and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you. -
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" -
Hello,
after installing the nagios connecor and it doesn'work, i try to remove it; with the powershell command remove-SCOMConnector. After removing it, Get-SCOMConnector shows me, that it doesn't exist:
PS D:\> Get-SCOMConnector
Name : Network Monitoring Internal Connector
DisplayName : Connector for populating network devices.
Description :
Initialized : False
Name :
DisplayName :
Description :
Initialized : True
Name : SMASH Discovery Internal Connector
DisplayName : Connector for populating SMASH devices.
Description :
Initialized : False
Name : Operations Manager Internal Connector
DisplayName : A connector used by Operations Manager components to insert discovery data, please create your own connec
tor do not use this connector.
Description :
Initialized : False
But when i take a look to the connectors in Operations Manager Console, it hangs, after a while i have this error:
Date: 27.05.2014 10:04:43
Application: Operations Manager
Application Version: 7.1.10226.0
Severity: Error
Message:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.EnterpriseManagement.ConnectorFramework.EnterpriseManagementConnector.Reconnect(EnterpriseManagementGroup managementGroup)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.GetUpdate(IndexTable indexTable, QueryUpdate`1 update, CacheCursor cursor, Range range, Int32 offset, Int32 groupLevel)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.QueryCache`2.GetUpdate(IndexTable indexTable, QueryUpdate`1 update)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.QueryCache`2.GetUpdate(CacheSession session, Boolean fullUpdate)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.QueryCache`2.FireUpdateEvent(CacheSession session, DateTime updateTime, Boolean dataChanged, Boolean fullUpdate, Boolean updatesOnly, IEnumerable queryResult)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.FireUpdateEvents(CacheSession session, Boolean dataChanged, Boolean fullUpdate, ICollection`1 queryResult)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.PostQuery(CacheSession session, IndexTable indexTable, UpdateReason reason, UpdateType updateType, Boolean dataChanged, DateTime queryTime, ICollection`1 queryResult)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.InternalSyncQuery(CacheSession session, IndexTable indexTable, UpdateReason reason, UpdateType updateType)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.InternalQuery(CacheSession session, UpdateReason reason)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.TryDoQuery(UpdateReason reason, CacheSession session)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
Can somebody help me fixing this error?
Strange.. the powerShell Command "get-SCOMConnector" works.. but the console hangs (on loading) when i want to show the connectors...
Kind regards
WolfgangHi,
I agree, we may need to remove the connector from OpsDB. In addition, here is blog regarding to the similar issue, hope it helps:
Error: “Object reference not set to an Instance of an Object” System Center Operation Manager 2012 Connector.
http://blogs.technet.com/b/birojitn/archive/2012/07/07/error-object-reference-not-set-to-an-instance-of-an-object-system-center-operation-manager-2012-connector.aspx
Regards,
Yan Li
Regards, Yan Li -
Hello,
We are currently implementing a Devops solution with SCOM 2012 SP1 and TFS 2010 SP1 and we would like to synchronize APM alerts with TFS and the Operational Issue WorkItem. However we are not
able to sync anything.
Here is our environments :
Products :
SCOM
System Center Operations Manager 2012 SP1
French
OS: Windows 2012 SP1 Std x64
French
DB: SCOM SQL Server 2012 SP1 x64
Management Pack
MP Operations Manager TFS Work Item Synchronisation 7.0.9538.0
MP Alert Attachement 7.0.9538.0 (We have also try the version in the VM DEVOPSALL : 7.0.9538.1005)
TFS
Team Foundation Server 2010 SP1
French 10.0.40219.1
OS: Windows 2008 R2 SP1 Std x64
French
DB: TFS SQL Server 2008 x64
TFS 2012 Object Model Installer (We have also try the version 2010)
Here is our configuration :
TFS Platform
This a French platform with a project based on the Process Template SCRUM 1.0 alone in a Team Project collection. The Operational Issue import completed successfully. It’s possible to manipulate
Operational Issue for all of its states from TFS.
SCOM Platform
We followed the documentation at :
http://technet.microsoft.com/en-us/library/jj883936.aspx
to configure SCOM Alert Attachment and Operation Manager Tfs Work Item Synchronization. Everything seems to be ok. All configurations succeed. We did not configure Intellitrace collector.
The problem occurs when we are trying to push an APM alert to TFS. When we assigned an alert to the Engineering nothing is synchronized in TFS. There is no error in the event viewer on the TFS
server. But, on the SCOM server we get 2 exceptions raised by Microsoft.EnterpriseManagement.Modules.Apm.TfsWISync.OMModules. We provide you the log of the SCOM Server in this mail.
Detailed exceptions :
Exception message are in French. In English it could be : OEF expected. The followed elements are not closed : Source, Link.
Microsoft.SystemCenter.TfsWISync.SyncAttachments.Rule
TFS Work Item Synchronisation ServerName
{EC924637-2725-7C94-8F37-013B657F4530}
Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule
System.Xml.XmlException: Fin de fichier inattendue. Les éléments suivants ne sont pas fermés : Source, Link. Ligne 1, position 65537.
à System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
à System.Xml.XmlTextReaderImpl.ParseElementContent()
à System.Xml.XmlReader.ReadString()
à System.Xml.XmlReader.ReadElementString(String name)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.DeserializeInternal(XmlReader reader)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.Deserialize(String mappings)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule.InitializeConfiguration(XmlReader reader)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadOpenAlertsModule..ctor(ModuleHost`1 moduleHost, XmlReader configurationReader, Byte[] previousState)
Microsoft.SystemCenter.TfsWISync.SyncWorkItems.Rule
TFS Work Item Synchronisation ServerName
{EC924637-2725-7C94-8F37-013B657F4530}
Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule
System.Xml.XmlException: Fin de fichier inattendue. Les éléments suivants ne sont pas fermés : Source, Link. Ligne 1, position 65537.
à System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
à System.Xml.XmlTextReaderImpl.ParseElementContent()
à System.Xml.XmlReader.ReadString()
à System.Xml.XmlReader.ReadElementString(String name)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.DeserializeInternal(XmlReader reader)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.Common.DataItems.Links.Deserialize(String mappings)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule.InitializeConfiguration(XmlReader reader)
à Microsoft.EnterpriseManagement.Modules.Apm.TfsConnector.OMModules.ReadAlertsSyncModule..ctor(ModuleHost`1 moduleHost, XmlReader configurationReader, Byte[] previousState)
According to you, is there a possible incompatibility of the synchronization system with French environments?
Thanks for your help.
Gregory OTT => http://twitter.com/gregory_ott
ALM Engineer at Tekigo => www.tekigo.comHi,
To monitor the complete TFS infrastructure, you need additional monitoring packs that alert you about a wide range of problems with TFS components. When you import the TFS Work Item Synchronization management pack, it is a best practice to
also import and configure these monitoring packs, you can double check these:
Monitoring Integration between Operations Manager and TFS in System Center 2012 SP1
http://technet.microsoft.com/en-us/library/jj899893.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Operations manager failed to run a wmi query for wmi events (0x800706ba)
Hi everyone,
I've been working on this issue for a while and I am still no closer to finding out what the problem is. If anybody can offer any other advice or things to check, I'm all ears.
I'm running SCOM 2012 R2 with UR2, and the Cluster Management Pack v6.0.7063.0
My problem is on one particular batch of cluster servers where I am getting the following error.
Name: Operations Manager failed to run a WMI query for WMI events
Alert Description:
Module was unable to enumerate the WMI data
Error: 0x800706ba
Details: The RPC server is unavailable
Workflow name: Microsoft.Windows.Cluster.Node.StateMonitoring
Instance Name: servername.domain.local
Instance ID: {instance_id}
Management group: SCOM_Management_Grp_Name
I am getting this alert regardless of whether I run the Windows Cluster Action Account as Local System, or as a domain user with full local admin privileges on all the cluster nodes.
When looking at the management pack and the workflow in particular (Microsoft.Windows.Cluster.Node.StateMonitoring), I can see that it's trying to access
MSCluster_Node in the root\MSCLUSTER WMI namespace.
This is the workflow for your information...
<UnitMonitor> ID="Microsoft.Windows.Cluster.Node.StateMonitoring" Accessibility="Public" Enabled="onEssentialMonitoring" Target="ClusLibrary!Microsoft.Windows.Cluster.Node" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="ClusLibrary!Microsoft.Windows.Cluster.CheckState" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Cluster.Node.StateMonitoring.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>
<AlertParameter2>$Target/Property[Type="ClusLibrary!Microsoft.Windows.Cluster.Node"]/ClusterName$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Success" MonitorTypeStateID="Online" HealthState="Success" />
<OperationalState ID="Warning" MonitorTypeStateID="Partial" HealthState="Warning" />
<OperationalState ID="Error" MonitorTypeStateID="NotOnline" HealthState="Error" />
</OperationalStates>
<Configuration>
<ClusterObjectName>$Target/Property[Type='ClusLibrary!Microsoft.Windows.Cluster.Node']/NodeName$</ClusterObjectName>
<PollInterval>60</PollInterval>
<ClusterObjectClass>MSCLUSTER_Node</ClusterObjectClass>
<OnlineExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='EventNewState']</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">0</Value>
</ValueExpression>
</SimpleExpression>
</OnlineExpression>
<OnlineExpressionOnDemand>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='State']</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">0</Value>
</ValueExpression>
</SimpleExpression>
</OnlineExpressionOnDemand>
<PartialExpression>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='EventNewState']</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='EventNewState']</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">3</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</PartialExpression>
<PartialExpressionOnDemand>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='State']</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='State']</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">3</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</PartialExpressionOnDemand>
<NotOnlineExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='EventNewState']</XPathQuery>
</ValueExpression>
<Operator>NotEqual</Operator>
<ValueExpression>
<Value Type="String">0</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='EventNewState']</XPathQuery>
</ValueExpression>
<Operator>NotEqual</Operator>
<ValueExpression>
<Value Type="String">2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='EventNewState']</XPathQuery>
</ValueExpression>
<Operator>NotEqual</Operator>
<ValueExpression>
<Value Type="String">3</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</NotOnlineExpression>
<NotOnlineExpressionOnDemand>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='State']</XPathQuery>
</ValueExpression>
<Operator>NotEqual</Operator>
<ValueExpression>
<Value Type="String">0</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='State']</XPathQuery>
</ValueExpression>
<Operator>NotEqual</Operator>
<ValueExpression>
<Value Type="String">2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Property[@Name='State']</XPathQuery>
</ValueExpression>
<Operator>NotEqual</Operator>
<ValueExpression>
<Value Type="String">3</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</NotOnlineExpressionOnDemand>
<WMIFields>Name, State</WMIFields>
</Configuration>
</UnitMonitor>
I can confirm that I am able to browse the MSCluster_Node class locally, as well as remotely using WMIEXPLORER and WBEMTEST,
however it only works when I set the Authentication Level to
Packet Privacy. If I do not select Packet Privacy, a WMI event log error 5605 is logged on the remote servers application log that says...
The root\mscluster namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy
and run the script or application again.
I can confirm that all firewalls are turned off, and there are no firewalls between the management servers and the agents in question. AV exclusions have been done and appear to be in place. The nodes are all Windows 2008 R2 with SP1. As
far as I can tell there is plenty of memory available on each of the nodes in question (50%+) of RAM is available.
If I manually run the "Discover the Windows Server 2008 R2 Cluster Components" task in the Cluster Service State section of the management pack in the Monitoring Pane in the console, on the nodes in question - the discovery runs successfully.
Does anybody have any other ideas or suggestions I could try?
Many thanks in advance,
Noel.
http://www.dreamension.netHi,
Common causes of RPC errors include:
Errors resolving a DNS or NetBIOS name.
The RPC service or related services may not be running.
Problems with network connectivity.
File and printer sharing is not enabled.
For more information, please review the link below:
Windows Server Troubleshooting: "The RPC server is unavailable"
http://social.technet.microsoft.com/wiki/contents/articles/4494.windows-server-troubleshooting-the-rpc-server-is-unavailable.aspx#Identify
Troubleshooting RPC Errors
http://technet.microsoft.com/en-us/magazine/2007.07.howitworks.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Operations Manager 2007 R2 Failed RMS Promotion
Forum,
I am moving our RMS to a 64-bit computer in preparation to upgrade to Operations Manager 2012. I have followed the directions found in the How to Promote a Root Management Server and it seemed successful. After reviewing the event logs, I have found repeating
21042 and 29106 events. There appears be a problem with my Secure Storage Key. I have tried creating a new key but that doesn't help. I have tried reinstalling my RMS server but I always end up at the same place. The agents are getting the 20070 error and
are unable to communicate with the server. Is there a way to rebuild the secure storage key?
RMS OS - Windows 2012R2
RMS - Ops Manager 2007R2 CU7
21042 Event
Operations Manager has discarded 1 items in management group LCC, which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when new devices are added to the topology but the complete
topology has not been distributed yet. The discarded items will be regenerated.
29106 Event
The request to synchronize state for OpsMgr Health Service identified by "00745302-047f-944b-0542-544eb4314c22" failed due to the following exception "System.Security.Cryptography.CryptographicException: Error occurred during a cryptographic
operation.
Server stack trace:
at Microsoft.EnterpriseManagement.Mom.Internal.AesNativeTransform.DepadBlock(Byte[] block, Int32 offset, Int32 count)
at Microsoft.EnterpriseManagement.Mom.Internal.AesNativeTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
at Microsoft.EnterpriseManagement.Security.SecureStorageManager.Decrypt(Byte[] value)
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.CreateCredentialSectionsForGivenCredentialType(XmlWriter& writer, Result dbRow)
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.InsertCredentialInfo(XmlWriter& writer, ReadOnlyCollection`1 requestedGuids, List`1 dbList, TypeOfCredentialDocumentElement elementType)
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.CredentialDocumentHelper.GenerateCredentialAndCredentialReferenceDocument()
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1
modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SDKReceiver.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.EnterpriseManagement.Mom.Internal.ISdkService.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.Sender.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1
modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences,
ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.SecureDataWriter.Write(StateSyncResponseMessage response)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.WriteState(StateSyncResponseMessage response)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateSyncResponseMessage response)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateContext stateContext, ConfigurationItems configurationItems, StateSyncResponseMessage response, IConnection connection)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".
Agent Event Error 20070
The OpsMgr Connector connected to RMS ServerName, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server
has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
Thanks,
WarrenHi Warren,
May be it helps you:
http://blogs.technet.com/b/kevinholman/archive/2009/11/10/29106-event-on-rms-index-was-out-of-range-wait-what.aspx
http://scug.be/christopher/2012/08/31/scom-2007-r2-configuration-not-loaded/
http://anandthearchitect.com/2009/12/02/scom-2007-r2-%E2%80%93-rms-server-not-seeing-the-agents-or-agents-are-not-talking-to-the-server/
Natalya -
Dreaded "Operations Manager failed to start a process" error (2012 R2)
I know this error has been covered many times, and on many topics, but this time mine is slightly different. It's
NOT the
"SCOMpercentageCPUTimeCounter" error covered by Kevin Holman.
Also, I am running SCOM 2012 R2 UR4 (7.1.10226.1046) and everything seems correctly patched (MS and agents), like
suggested by Nicole Welch and Kevin Holman as well.
So my environment is a fresh installation of SCOM 2012 R2, and I am transferring to this new Management Group, the monitored servers from our old SCOM 2012 "R1" (which I did not upgrade but rather made a brand new independent install). So
all servers aren't migrated yet, but I would like to solve this error before. This error did NOT happen in "R1", nor was it overridden (I imported the exact same Management Packs anyway).
On 2012 R2, it happens on almost all new monitored machines, mainly Read-Only Domain Controllers (RODCs).
Here is the kind of alert text I am getting:
Het om 10:10:15 gestarte proces is beëindigd als gevolg van een uitvoerverzamelfout als gevolg van fout 0x80070057 :
The parameter is incorrect.
; mogelijk zijn er gegevens verloren gegaan.
Opdracht die is uitgevoerd: "C:\Windows\system32\cscript.exe" //nologo "C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 193\24788\AD_Global_Catalog_Search_Response.vbs"
RODC02.mydomain.be (objectCategory=DMD) false 4 {9E253FCB-8AAF-491F-CCA3-E632C6C2800C}
Werkmap: C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 193\24788\
Dit is van invloed op een of meer werkstromen.
Werkstroomnaam: Microsoft.Windows.Server.2008.AD.DomainController.GCSearchTime.Monitor
Exemplaarnaam: RODC02
Our servers have Belgian (Dutch) regional settings, hence the language. But check out the highlighted info in bold.
The related event Number (in Alert Context) is 21404. Most other articles about this, mention 21402 or 21403. I suppose they all must be related but still, it's a new one here.
There you have the failing VBS file. I checked all alerts and there seem to be different files concerned overall. Other examples:
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 233\22737\AD_Database_and_Log.vbs (from almost all RODCs)
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 196\19876\Microsoft.Windows.Server.Legacy.FreeSpace.vbs
(also from an RODC)
C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 5891\338282\Microsoft.Windows.Server.CPUUtilization.Monitortype.vbs 95 15
SCOM02.mydomain.be 1.4119384288787842 (this one is from my second Management Server..)
Repeat count of the alert is 1 to 2 a day, so it's not nightmareish, but still, requires to be fixed. I suspect that even if there is a different VBS file concerned, since the eventID and the alert text are the same, the repeat count will just increase,
not showing the last actual VBS concerned.
I connect to each of these servers, and browse to the directory containing the file, and the folder is there, the file is there. The error text mentions incorrect parameters but they still seem OK to me.
I found something which might be worth noting: when browsing to the directory, be it on an RODC or on the SCOM server, I get a permission popup requiring some admin rights to do so - although I am using my domain admin (+SCOM+SQL+local
admin everywhere) account:
SCOM services use the Local System account to run, on every machine. I thought Local System shouldn't be concerned with these permissions popups, but normally the domain/local admins aren't either, yet I am.
The "Health service" folder is the only one from the "C:\Program Files\Microsoft Monitoring Agent\Agent" folder to be concerned with this; I can browse without trouble to any other directory there.
After a SCOM service stop, I renamed the "Health Service state" folder (as you can see on the screenshot, there is a "Health Service State bak" folder) and let the service recreate it after a restart, to ensure it was clean and with
appropriate permissions , but it doesn't help.
Might that be a clue?
Or else what? I'm getting confused and don't find a suitable solution.
dd
BixOn Thu, 4 Dec 2014 14:20:22 +0000, Bixessss wrote:
I know this error has been covered many times, and on many topics, but this time mine is slightly different. It's*NOT* the "SCOMpercentageCPUTimeCounter" error covered by Kevin Holman <http://blogs.technet.com/b/kevinholman/archive/2010/02/23/a-new-script-error-scompercentagecputimecounter-vbs-invalid-class.aspx>.
Also, I am running *SCOM 2012 R2 UR4* (7.1.10226.1046) and everything seems correctly patched (MS and agents), likesuggested by Nicole Welch <http://nicolewelchscom.wordpress.com/2013/10/01/operations-manager-failed-to-start-a-process/>
and Kevin Holman as well.
This forum is for security issues related to Windows Server and not for
System Center questions.
Post your question in one of the following forums:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=systemcenteroperationsmanager
Thanks.
Paul Adare - FIM CM MVP
Never trust a computer you can't lift. - Stan Masor -
Operations Manager log flooded with 11903 errors due to "Virtual Hard Disk free disk space" monitor
Management Pack: Microsoft Windows Hyper-V 2012 R2 Monitoring (7.1.10104.0)
Monitor: Virtual Hard Disk free disk space
There appears to be an issue with this monitor. Every hour, each of my Hyper-V servers is reporting dozens of errors similar to the following. It seems like there is a disconnect between the expected return type (integer) and the actual type (decimal) when
checking the free space on VHDX files.
Log Name: Operations Manager
Source: Health Service Modules
Date: 2/5/2014 7:59:47 AM
Event ID: 11903
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BEAST.corp.technologytoolbox.com
Description:
The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
Property Expression: Property[@Name='Microsoft:9AC8FCAB-800D-424F-ABCB-747063E5FCF1\559D22F4-A565-4AD4-9B71-44FC5D815C0C\0\0\L.FreeSpace']
Property Value: 488033.99609375
Conversion Type: DataItemElementTypeInteger(5)
Original Error: 0x80FF005A
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.HyperV.2012.R2.VirtualDrive.FreeSpaceMonitor
Instance name: Hard Disk
Instance ID: {0C0E0759-D846-963C-21E6-3C1A1C096D5F}
Management group: HQ
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Modules" />
<EventID Qualifiers="49152">11903</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-02-05T14:59:47.000000000Z" />
<EventRecordID>32395</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>BEAST.corp.technologytoolbox.com</Computer>
<Security />
</System>
<EventData>
<Data>HQ</Data>
<Data>Microsoft.Windows.HyperV.2012.R2.VirtualDrive.FreeSpaceMonitor</Data>
<Data>Hard Disk</Data>
<Data>{0C0E0759-D846-963C-21E6-3C1A1C096D5F}</Data>
<Data>Property[@Name='Microsoft:9AC8FCAB-800D-424F-ABCB-747063E5FCF1\559D22F4-A565-4AD4-9B71-44FC5D815C0C\0\0\L.FreeSpace']</Data>
<Data>488033.99609375</Data>
<Data>DataItemElementTypeInteger(5)</Data>
<Data>0x80FF005A</Data>
</EventData>
</Event>SCOM agent is running as SYSTEM. (I used to run SCOM agents as a low-privilege domain account but eventually surrendered to "The Dark Side" due to the number of issues encountered with that approach.)
PS HKU:\.DEFAULT\Control Panel\International> dir
Hive: HKEY_USERS\.DEFAULT\Control Panel\International
Name Property
Geo Nation : 244
User Profile Languages : {en-US}
ShowAutoCorrection : 1
ShowTextPrediction : 1
ShowCasing : 1
ShowShiftLock : 1
User Profile System Backup Languages : {en-US}
ShowAutoCorrection : 1
ShowTextPrediction : 1
ShowCasing : 1
ShowShiftLock : 1 -
Operations Manager failed to start a process + UAC
Ok, I understand that there are perhaps tens of thousands of these posts, but I've not found one after an hour searching that seems to meet up with what I'm seeing.
Seeing this show up on a handful of servers, and I don't see the correlation with the servers having this issue and things they have in common. I'm seeing it on all of our Lync Front-End servers, and then on a few terminal servers. I'm going to give the
error for the Lync servers here though.
The process started at 9:00:25 AM failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0
Command executed: "C:\Windows\system32\cscript.exe" /nologo "GetSQL2012DBFilesFreeSpace.vbs" "FE-05\RTCLOCAL" "FE-05.home.ku.edu" "RTCLOCAL"
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 9359\180265\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2012.Monitoring.DBFileSpaceMonitor
Instance name: tempdb2
Instance ID: {1FFB1DA7-414F-CAA1-E3EC-07AC097A2CED}
Management group: ITES
So since I've been working through all these little annoying warnings and trying to sort them out I decided to run the script.
<Collection><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.28
55484-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conve
rsionType>PerformanceData</ConversionType><Property Name="Database" VariantType=
"8">master</Property><Property Name="FileId" VariantType="3">1</Property><Proper
ty Name="FreeSpaceMB" VariantType="5">37646.0621050745</Property><Property Name=
"FreeSpacePercent" VariantType="5">99.9912017130836</Property><Property Name="Fr
eeSpaceAutoGrowMB" VariantType="5">0.6875</Property><Property Name="FreeSpaceAut
oGrowPercent" VariantType="5">17.1875</Property></DataItem><DataItem type="Syste
m.PropertyBagData" time="2014-06-04T09:23:23.2855484-05:00" sourceHealthServiceI
d="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</Conver
sionType><Property Name="Database" VariantType="8">master</Property><Property Na
me="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" VariantType
="5">39248.5533834203</Property><Property Name="FreeSpacePercent" VariantType="5
">99.9991440853338</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5
">0.414063</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">5
5.2084</Property></DataItem><DataItem type="System.PropertyBagData" time="2014-0
6-04T09:23:23.2905518-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDD
A89CEB89"><ConversionType>PerformanceData</ConversionType><Property Name="Databa
se" VariantType="8">tempdb</Property><Property Name="FileId" VariantType="3">1</
Property><Property Name="FreeSpaceMB" VariantType="5">36681.1775486072</Property
><Property Name="FreeSpacePercent" VariantType="5">99.9923331676945</Property><P
roperty Name="FreeSpaceAutoGrowMB" VariantType="2">0</Property><Property Name="F
reeSpaceAutoGrowPercent" VariantType="2">0</Property></DataItem><DataItem type="
System.PropertyBagData" time="2014-06-04T09:23:23.2905518-05:00" sourceHealthSer
viceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</C
onversionType><Property Name="Database" VariantType="8">tempdb</Property><Proper
ty Name="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" Varian
tType="5">38307.2356943516</Property><Property Name="FreeSpacePercent" VariantTy
pe="5">99.9940044295872</Property><Property Name="FreeSpaceAutoGrowMB" VariantTy
pe="2">0</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="2">0</
Property></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:
23:23.2915509-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89
"><ConversionType>PerformanceData</ConversionType><Property Name="Database" Vari
antType="8">tempdb</Property><Property Name="FileId" VariantType="3">3</Property
><Property Name="FreeSpaceMB" VariantType="5">39745.5</Property><Property Name="
FreeSpacePercent" VariantType="5">99.988679245283</Property><Property Name="Free
SpaceAutoGrowMB" VariantType="5">120.5</Property><Property Name="FreeSpaceAutoGr
owPercent" VariantType="5">96.4</Property></DataItem><DataItem type="System.Prop
ertyBagData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1
D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionTy
pe><Property Name="Database" VariantType="8">tempdb</Property><Property Name="Fi
leId" VariantType="3">4</Property><Property Name="FreeSpaceMB" VariantType="5">3
9746.375</Property><Property Name="FreeSpacePercent" VariantType="5">99.99088050
31447</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">121.375</Pr
operty><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">97.1</Property>
</DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.291
5509-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conver
sionType>PerformanceData</ConversionType><Property Name="Database" VariantType="
8">tempdb</Property><Property Name="FileId" VariantType="3">5</Property><Propert
y Name="FreeSpaceMB" VariantType="5">39745.875</Property><Property Name="FreeSpa
cePercent" VariantType="5">99.9896226415094</Property><Property Name="FreeSpaceA
utoGrowMB" VariantType="5">120.875</Property><Property Name="FreeSpaceAutoGrowPe
rcent" VariantType="5">96.7</Property></DataItem><DataItem type="System.Property
BagData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1D980
F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><
Property Name="Database" VariantType="8">tempdb</Property><Property Name="FileId
" VariantType="3">6</Property><Property Name="FreeSpaceMB" VariantType="5">39744
.875</Property><Property Name="FreeSpacePercent" VariantType="5">99.987106918239
</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">119.875</Propert
y><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">95.9</Property></Dat
aItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2915509-
05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionT
ype>PerformanceData</ConversionType><Property Name="Database" VariantType="8">te
mpdb</Property><Property Name="FileId" VariantType="3">7</Property><Property Nam
e="FreeSpaceMB" VariantType="5">39744.9375</Property><Property Name="FreeSpacePe
rcent" VariantType="5">99.9872641509434</Property><Property Name="FreeSpaceAutoG
rowMB" VariantType="5">119.9375</Property><Property Name="FreeSpaceAutoGrowPerce
nt" VariantType="5">95.95</Property></DataItem><DataItem type="System.PropertyBa
gData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1D980F-
BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Pr
operty Name="Database" VariantType="8">tempdb</Property><Property Name="FileId"
VariantType="3">8</Property><Property Name="FreeSpaceMB" VariantType="5">39742.2
5</Property><Property Name="FreeSpacePercent" VariantType="5">99.9805031446541</
Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">117.25</Property><
Property Name="FreeSpaceAutoGrowPercent" VariantType="5">93.8</Property></DataIt
em><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2915509-05:
00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType
>PerformanceData</ConversionType><Property Name="Database" VariantType="8">tempd
b</Property><Property Name="FileId" VariantType="3">9</Property><Property Name="
FreeSpaceMB" VariantType="5">39744.5625</Property><Property Name="FreeSpacePerce
nt" VariantType="5">99.986320754717</Property><Property Name="FreeSpaceAutoGrowM
B" VariantType="5">119.5625</Property><Property Name="FreeSpaceAutoGrowPercent"
VariantType="5">95.65</Property></DataItem><DataItem type="System.PropertyBagDat
a" time="2014-06-04T09:23:23.2975503-05:00" sourceHealthServiceId="9F1D980F-BA02
-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Proper
ty Name="Database" VariantType="8">model</Property><Property Name="FileId" Varia
ntType="3">1</Property><Property Name="FreeSpaceMB" VariantType="5">39630.875</P
roperty><Property Name="FreeSpacePercent" VariantType="5">99.9944806182969</Prop
erty><Property Name="FreeSpaceAutoGrowMB" VariantType="5">0.875</Property><Prope
rty Name="FreeSpaceAutoGrowPercent" VariantType="5">28.5714285714286</Property><
/DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2975
503-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Convers
ionType>PerformanceData</ConversionType><Property Name="Database" VariantType="8
">model</Property><Property Name="FileId" VariantType="3">2</Property><Property
Name="FreeSpaceMB" VariantType="5">39248.5690084203</Property><Property Name="Fr
eeSpacePercent" VariantType="5">99.9991838953776</Property><Property Name="FreeS
paceAutoGrowMB" VariantType="5">0.429688</Property><Property Name="FreeSpaceAuto
GrowPercent" VariantType="5">57.2917333333333</Property></DataItem><DataItem typ
e="System.PropertyBagData" time="2014-06-04T09:23:23.3025532-05:00" sourceHealth
ServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData
</ConversionType><Property Name="Database" VariantType="8">msdb</Property><Prope
rty Name="FileId" VariantType="3">1</Property><Property Name="FreeSpaceMB" Varia
ntType="5">37585.1339389847</Property><Property Name="FreeSpacePercent" VariantT
ype="5">99.9579465372616</Property><Property Name="FreeSpaceAutoGrowMB" VariantT
ype="5">0.875</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5
">5.2434456928839</Property></DataItem><DataItem type="System.PropertyBagData" t
ime="2014-06-04T09:23:23.3025532-05:00" sourceHealthServiceId="9F1D980F-BA02-D35
1-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Property N
ame="Database" VariantType="8">msdb</Property><Property Name="FileId" VariantTyp
e="3">2</Property><Property Name="FreeSpaceMB" VariantType="5">36542.9860732182<
/Property><Property Name="FreeSpacePercent" VariantType="5">99.9936081094063</Pr
operty><Property Name="FreeSpaceAutoGrowMB" VariantType="5">17.289063</Property>
<Property Name="FreeSpaceAutoGrowPercent" VariantType="5">88.0971363057325</Prop
erty></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:2
3.3075515-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><C
onversionType>PerformanceData</ConversionType><Property Name="Database" VariantT
ype="8">xds</Property><Property Name="FileId" VariantType="3">1</Property><Prope
rty Name="FreeSpaceMB" VariantType="5">39628.25</Property><Property Name="FreeSp
acePercent" VariantType="5">99.990537949132</Property><Property Name="FreeSpaceA
utoGrowMB" VariantType="5">4.25</Property><Property Name="FreeSpaceAutoGrowPerce
nt" VariantType="5">53.125</Property></DataItem><DataItem type="System.PropertyB
agData" time="2014-06-04T09:23:23.3085531-05:00" sourceHealthServiceId="9F1D980F
-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><P
roperty Name="Database" VariantType="8">xds</Property><Property Name="FileId" Va
riantType="3">2</Property><Property Name="FreeSpaceMB" VariantType="5">39630.109
375</Property><Property Name="FreeSpacePercent" VariantType="5">99.9952295493541
</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">6.109375</Proper
ty><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">76.3671875</Propert
y></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.3
135527-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conv
ersionType>PerformanceData</ConversionType><Property Name="Database" VariantType
="8">rtcdyn</Property><Property Name="FileId" VariantType="3">1</Property><Prope
rty Name="FreeSpaceMB" VariantType="5">199127.125</Property><Property Name="Free
SpacePercent" VariantType="5">99.9915262322741</Property><Property Name="FreeSpa
ceAutoGrowMB" VariantType="5">983.125</Property><Property Name="FreeSpaceAutoGro
wPercent" VariantType="5">98.3125</Property></DataItem><DataItem type="System.Pr
opertyBagData" time="2014-06-04T09:23:23.3135527-05:00" sourceHealthServiceId="9
F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</Conversion
Type><Property Name="Database" VariantType="8">rtcdyn</Property><Property Name="
FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" VariantType="5"
>15768.585938</Property><Property Name="FreeSpacePercent" VariantType="5">99.649
8100227502</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">1944.5
85938</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">97.229
2969</Property></DataItem><DataItem type="System.PropertyBagData" time="2014-06-
04T09:23:23.3195540-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA8
9CEB89"><ConversionType>PerformanceData</ConversionType><Property Name="Database
" VariantType="8">rtc</Property><Property Name="FileId" VariantType="3">1</Prope
rty><Property Name="FreeSpaceMB" VariantType="5">198878.4375</Property><Property
Name="FreeSpacePercent" VariantType="5">99.8666480034548</Property><Property Na
me="FreeSpaceAutoGrowMB" VariantType="5">734.4375</Property><Property Name="Free
SpaceAutoGrowPercent" VariantType="5">73.44375</Property></DataItem><DataItem ty
pe="System.PropertyBagData" time="2014-06-04T09:23:23.3195540-05:00" sourceHealt
hServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceDat
a</ConversionType><Property Name="Database" VariantType="8">rtc</Property><Prope
rty Name="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" Varia
ntType="5">15659.34375</Property><Property Name="FreeSpacePercent" VariantType="
5">98.9594524140546</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="
5">1835.34375</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5
">91.7671875</Property></DataItem></Collection>
As you can see a boatload of data is returned, then I realized that my command prompt was running in admin mode. When I ran the same command not in admin mode, there was no data returned, which seems to fit with the error. The script ran but no data came
back.
So, my question is, should I disable UAC on all my front end servers? Or, is there a better runas account to use? I believe I chose the default LocalSystem for everybody since it doesn't require as much effort.
Any feedback is welcome :)
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.comThe agent should use LocalSystem and it is very rare to use a different account to run the agent service. This is probably a need to configure a run as account to be used by the SQL Discovery. SQL Server 2012 is much more locked down than previous versions
of SQL, so unless you gave localsystem admin rights to your instance of SQL running on this box, this script will always come back with nothing. check out kevin holmans article on how to configure run as accounts for the SQL MP, to address this issue.
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
hope this helps!
Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
Please remember to click “Mark as Answer” on the post that helps you!
my new blog om2012.wordpress.com -
SCOM 2012 Operations Manager Failed to start a process
We have recently upgraded from SCOM 2007 to SCOM 2012. We are not getting a great deal of “Operations Manager Failed to start a process”. The process varies including:
DiscoverSQL2008ASDiscovery.vbs
DiscoverSQL2008DBEngineDiscovery.vbs
DiscoverSQL2008ASDiscovery.vbs
Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs
I have researched and researched. I know that you can try to run the scripts locally on the machine but it seems the scripts never make it to the machine. I go to the path in the error, no luck. I look in the other folders as I know that SCOM moves the scripts,
and I even search the entire C drive but the scripts are not getting to the server. The folder is not even making it. For example:
Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs" SERVER true Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring
Host Temporary Files 11606\1759\
The script is not there and the folder \1759 is not there either.
I have removed and reinstalled the client.
Antivirus is fine, up to date and not blocking on any of the machines.
I have stopped the “System Center Management service” and renamed the “Health Service State” folder and it recreates fine but not long after I get the warning in SCOM about “Operations Manager Failed to start a process”.
I look in event viewer for Operations Manager on this particular one and I see a lot of:
Performance data from the Health Service could not be collected since required registry keys could not be read, the error was 2L (The system cannot find the file specified.). Event ID 6001.
I tried the fix of
"lodctr MOMConnectorCounters.ini" and "lodctr HealthServiceCounters.ini" but I get “error
encountered while updating text in registry. Status: 0”. Again I am using SCOM 2012.
Do I need to look at each failed script or is there a overall issue because the scripts are not making it to the machines. Any ideas?I guess you might need to run "mofcomp sqlmgmproviderxpsp2up.mof".
Thanks, S K Agrawal -
Microsoft Operations Manager Condolidator Module processing thread failed
Hello,
I got the error: The Microsoft Operations Manager Condolidator Module processing thread failed with an internal error and must be unload.
with event ID 11105 & 11108 but not the one in the article is it the same issue or more ...
I could not find any WMI issue as stated in http://thoughtsonopsmgr.blogspot.com/2011/01/error-consolidator-module-failed.html
Any idea?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Managertry clearing the health service cache on the agents and restart the health service to reload that workflow.
Juke Chou
TechNet Community Support
I did already twice and this did not fix the issue.
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager
Maybe you are looking for
-
ID CS6 shows low resolution on placed AI file.
I placed an AI, full vector, file into ID. Didn't see any problems until I ran preflight and it popped up with a low resolution warning. The vector is scaled down inside ID, but still shows a 90 ppi. I couldn't find any placed images in the AI file,
-
Sales Doc Overall status not updating in DSO
Hi All, In ECC status of the Sales Document has changed from B to C. However in the DSO status still shows as C. Delta has pushed through successfully. Please see the screenshot below. Why is the status not changing in DSO? How to handle this issue?
-
ITunes on pc can,t communicate with my iPad can,t restore or update
Going round in circles here and about to chuck iPad on the bin! I only discovered this problem when I tried to update my iPad via iTunes. Now not only can I not update or restore..... Same message each time update server could not be contacted, iTun
-
hi all, i need to know the control commands available in BDC. for ex: in scripts we have commands like protect.......endprotect, if......endif, address .... endaddress......... thanks & regards, suresh babu aluri.
-
El disco de la PC se colapsó y perdí la instalación de Acrobat X pro, ¿cómo puedo recuperar la instalación o licencia? Ya que el software no fue desinstalado previamente.