{"id":139,"date":"2016-01-27T17:19:11","date_gmt":"2016-01-27T17:19:11","guid":{"rendered":"http:\/\/www.mayerinformatics.com\/?p=139"},"modified":"2016-01-27T17:19:11","modified_gmt":"2016-01-27T17:19:11","slug":"system-center-operations-manager-client-failed-to-install","status":"publish","type":"post","link":"https:\/\/www.mayerinformatics.com\/?p=139","title":{"rendered":"System Center Operations Manager client failed to install"},"content":{"rendered":"<p>On a subset of similarly configured servers I had problems installing the SCOM agent. At the time I installed the client I used the NOAPM=1 switch. However, when an update came out for the client through windows update, the update would fail and the client service would stop. The error when using an interactive installer was &#8220;Product: System Center Operations Managers 2012 Server &#8212; Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).&#8221;<\/p>\n<p>I noticed when I launched perfmon.exe there were no counters available. Microsoft provided some guidance regarding this issue in\u00a0<a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/2554336\" target=\"_blank\">KB2554336<\/a>. The rebuilding of the performance counters yielded unpredictable results. Sometimes after conducting the steps I would have performance counters, other times I would not. I was able to get more reproducible results by using the code provided <a href=\"http:\/\/johansenreidar.blogspot.com\/2014\/01\/windows-server-rebuild-all-performance.html\" target=\"_blank\">Reidar Johansen&#8217;s Blog post\u00a0<\/a>. Even with the performance counters back in the Performance Monitor application the install of the SCOM agent would still fail.<\/p>\n<p>The exact error I saw in the logs is:<\/p>\n<blockquote>\n<pre>InstallAPMPerfCounters: Installing agent perf counters. \nMSI (s) (6C:F4) [10:00:45:160]: Executing op: ActionStart(Name=_Rollback_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,,)\nMSI (s) (6C:F4) [10:00:45:160]: Executing op: CustomActionSchedule(Action=_Rollback_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,ActionType=3393,Source=BinaryData,Target=UninstallServerPerfCounters,CustomActionData=C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\APMDOTNETAgent\\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll)\nMSI (s) (6C:F4) [10:00:45:160]: Executing op: ActionStart(Name=_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,,)\nMSI (s) (6C:F4) [10:00:45:160]: Executing op: CustomActionSchedule(Action=_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,ActionType=3073,Source=BinaryData,Target=InstallServerPerfCounters,CustomActionData=C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\APMDOTNETAgent\\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll)\nMSI (s) (6C:F0) [10:00:45:176]: Invoking remote custom action. DLL: C:\\Windows\\Installer\\MSI8EC8.tmp, Entrypoint: InstallServerPerfCounters\nCAPACK: Extracting custom action to temporary directory: C:\\Windows\\Installer\\MSI8EC8.tmp-\\\nCAPACK: CLR version v2.0.50727 is installed.\nCAPACK: CLR version v2.0.50727 is detected.\nCAPACK: CLR version v4.0.30319 is installed.\nCAPACK: CLR version v4.0.30319 is detected.\nCAPACK: Binding to CLR version v2.0.50727\nCalling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.InstallServerPerfCounters\nCustomAction _Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)\nMSI (s) (6C:F0) [10:00:48:520]: NOTE: custom action _Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.\nAction ended 10:00:49: InstallFinalize. Return value 3.\nMSI (s) (6C:F4) [10:00:49:723]: User policy value 'DisableRollback' is 0\nMSI (s) (6C:F4) [10:00:49:723]: Machine policy value 'DisableRollback' is 0\nMSI (s) (6C:F4) [10:00:49:723]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1211518986,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)\nMSI (s) (6C:F4) [10:00:49:723]: Executing op: DialogInfo(Type=0,Argument=0)\nMSI (s) (6C:F4) [10:00:49:723]: Executing op: DialogInfo(Type=1,Argument=Microsoft Monitoring Agent)\nMSI (s) (6C:F4) [10:00:49:723]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])\nMSI (s) (6C:F4) [10:00:49:723]: Executing op: ActionStart(Name=_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,,)\nMSI (s) (6C:F4) [10:00:49:739]: Executing op: ProductInfo(ProductKey={786970C5-E6F6-4A41-B238-AE25D4B91EEA},ProductName=Microsoft Monitoring Agent,PackageName=MOMAgent.msi,Language=0,Version=117516232,Assignment=1,ObsoleteArg=0,ProductIcon=agentgateway.ico,,PackageCode={283192C9-D69D-4E21-A33A-F9AC64EAD2A4},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)\nMSI (s) (6C:F4) [10:00:49:739]: Executing op: ActionStart(Name=_Rollback_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,,)\nMSI (s) (6C:F4) [10:00:49:739]: Executing op: CustomActionRollback(Action=_Rollback_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,ActionType=3393,Source=BinaryData,Target=UninstallServerPerfCounters,CustomActionData=C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\APMDOTNETAgent\\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll)\nMSI (s) (6C:B0) [10:00:49:739]: Invoking remote custom action. DLL: C:\\Windows\\Installer\\MSIA0AC.tmp, Entrypoint: UninstallServerPerfCounters\nCAPACK: Extracting custom action to temporary directory: C:\\Windows\\Installer\\MSIA0AC.tmp-\\\nCAPACK: CLR version v2.0.50727 is installed.\nCAPACK: CLR version v2.0.50727 is detected.\nCAPACK: CLR version v4.0.30319 is installed.\nCAPACK: CLR version v4.0.30319 is detected.\nCAPACK: Binding to CLR version v2.0.50727\nCalling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.UninstallServerPerfCounters\nCustomAction _Rollback_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76 returned actual error code 1603 but will be translated to success due to continue marking\nMSI (s) (6C:B0) [10:00:54:707]: NOTE: custom action _Rollback_Inst_APM_PerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.\nMSI (s) (6C:F4) [10:00:54:707]: Executing op: ActionStart(Name=_InstallInterceptPerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,,)\nMSI (s) (6C:F4) [10:00:54:707]: Executing op: ActionStart(Name=_Rollback_InstallInterceptPerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,,)\nMSI (s) (6C:F4) [10:00:54:707]: Executing op: CustomActionRollback(Action=_Rollback_InstallInterceptPerfCounters.A591E3B4_D228_431D_BF89_99D52C8FFB76,ActionType=3393,Source=BinaryData,Target=UninstallAPMPerfCounters,CustomActionData=C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\APMDOTNETAgent\\)\nMSI (s) (6C:00) [10:00:54:707]: Invoking remote custom action. DLL: C:\\Windows\\Installer\\MSIB415.tmp, Entrypoint: UninstallAPMPerfCounters\nUninstallAPMPerfCounters: Custom Action Data. C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\APMDOTNETAgent\\\nUninstallAPMPerfCounters: Un-installing agent perf counters. \nUninstallAPMPerfCounters: Successfully un-installed agent perf counters.<\/pre>\n<\/blockquote>\n<p><a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/300956\" target=\"_blank\">KB300956<\/a>\u00a0 indicated that the lodctr.exe command could be used to restore counters from an .ini file. I saw that a file existed in C:\\Windows\\System32 and C:\\Windows\\SysWow64 called PerfStringBackup.INI. Since my previous attempts to restore the performance counters yielded inconsistent, I tried replacing PerfStringBackup.INI with a copy from another windows 2008R2 install. I issued the following powershell commands:<\/p>\n<blockquote><p>lodctr.exe c:\\Windows\\System32\\PerfStringBackup.ini<br \/>\nlodctr.exe c:\\Windows\\SysWOW64\\PerfStringBackup.ini<br \/>\n<code>WINMGMT.EXE \/RESYNCPERF<br \/>\nrestart-service pla<br \/>\nrestart-service Winmgmt -force<\/code><\/p>\n<p>&nbsp;<\/p><\/blockquote>\n<p>After verifying the counters were present in Performance Monitor, I ran the SCOM agent installer. It completed without error and subsequent updates from Windows Update applied without failiure.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On a subset of similarly configured servers I had problems installing the SCOM agent. At the time I installed the client I used the NOAPM=1 switch. However, when an update came out for the client through windows update, the update would fail and the client service would stop. The error when using an interactive installer [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-139","post","type-post","status-publish","format-standard","hentry","category-system-center-operations-manager"],"_links":{"self":[{"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=\/wp\/v2\/posts\/139"}],"collection":[{"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=139"}],"version-history":[{"count":0,"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=\/wp\/v2\/posts\/139\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mayerinformatics.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}