<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Forwarder 9.1.1 update failed on Domain Controller in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/679775#M13714</link>
    <description>&lt;P&gt;I'm having the same problem on our DC's. Did you find a solution?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2024 11:27:04 GMT</pubDate>
    <dc:creator>Dingetjes</dc:creator>
    <dc:date>2024-03-06T11:27:04Z</dc:date>
    <item>
      <title>Forwarder 9.1.1 update failed on Domain Controller</title>
      <link>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/670045#M13436</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The update installation of the forwarder is not running and a roll-back is being performed. During further tests I have activated the verbose logging of the MSI installer. The following error occurs here:&lt;/P&gt;&lt;P&gt;Cannot set GROUPPERFORMANCEMONITORUSERS=1 since the local users/groups are not available on Domain Controller.&lt;/P&gt;&lt;P&gt;He is probably right. But why does the installer try to set this parameter at all during an update installation? Unfortunately, I cannot set any further options here during an update. There is clearly a bug in the installer script.&lt;/P&gt;&lt;P&gt;Any Ideas?&lt;/P&gt;&lt;P&gt;Log:&lt;/P&gt;&lt;P&gt;Action 14:44:08: SetAccountTypeData.&lt;BR /&gt;Action start 14:44:08: SetAccountTypeData.&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:562]: PROPERTY CHANGE: Adding SetAccountType property. Its value is 'UseVirtualAccount=;UseLocalSystem=0;UserName=D3622070\SIEM-EVNT-READER;FailCA='.&lt;BR /&gt;Action ended 14:44:08: SetAccountTypeData. Return value 1.&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:562]: Doing action: SetAccountType&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:562]: Note: 1: 2205 2: 3: ActionText&lt;BR /&gt;Action 14:44:08: SetAccountType.&lt;BR /&gt;Action start 14:44:08: SetAccountType.&lt;BR /&gt;MSI (s) (A0:F0) [14:44:08:562]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIAC9D.tmp, Entrypoint: SetAccountTypeCA&lt;BR /&gt;SetAccountType: Error 0x80004005: Cannot set GROUPPERFORMANCEMONITORUSERS=1 since the local users/groups are not available on Domain Controller.&lt;BR /&gt;CustomAction SetAccountType returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)&lt;BR /&gt;Action ended 14:44:08: SetAccountType. Return value 3.&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:594]: Note: 1: 2265 2: 3: -2147287035&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:594]: User policy value 'DisableRollback' is 0&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:594]: Machine policy value 'DisableRollback' is 0&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:594]: Note: 1: 2318 2:&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:609]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1467512195,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:609]: Executing op: DialogInfo(Type=0,Argument=1033)&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:609]: Executing op: DialogInfo(Type=1,Argument=UniversalForwarder)&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:609]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])&lt;BR /&gt;MSI (s) (A0:60) [14:44:08:609]: Executing op: RegisterBackupFile(File=C:\Config.Msi\b08a3953.rbf)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 15:27:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/670045#M13436</guid>
      <dc:creator>zahni</dc:creator>
      <dc:date>2023-11-28T15:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder 9.1.1 update failed on Domain Controller</title>
      <link>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/679775#M13714</link>
      <description>&lt;P&gt;I'm having the same problem on our DC's. Did you find a solution?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 11:27:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/679775#M13714</guid>
      <dc:creator>Dingetjes</dc:creator>
      <dc:date>2024-03-06T11:27:04Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder 9.1.1 update failed on Domain Controller</title>
      <link>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/679777#M13715</link>
      <description>&lt;P&gt;From Splunk Support:&lt;/P&gt;&lt;P&gt;"It will be resolved in version 9.1.3 and 9.2.1 releases. "&lt;/P&gt;&lt;P&gt;As a workaround, you can uninstall the UF and install the new version&amp;nbsp; instead of upgrading.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 11:33:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Forwarder-9-1-1-update-failed-on-Domain-Controller/m-p/679777#M13715</guid>
      <dc:creator>zahni</dc:creator>
      <dc:date>2024-03-06T11:33:37Z</dc:date>
    </item>
  </channel>
</rss>

