https://community.splunk.com/t5/Monitoring-Splunk/February-2026-Patches-Break-RPC-calls-to-DC/m-p/760912#M11138 <P>Hello&nbsp;<a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/235702">@ASierra</a>&nbsp;,</P><P>&nbsp;</P><P>I don't see it in known issue of Splunk. Maybe if you are still having this issue in production, raise Splunk support case to get it fixed.</P><P>&nbsp;</P><P>I hope this helps!!</P> Wed, 13 May 2026 08:13:39 GMT VatsalJagani 2026-05-13T08:13:39Z https://community.splunk.com/t5/Monitoring-Splunk/February-2026-Patches-Break-RPC-calls-to-DC/m-p/758400#M11083 <P>There have been reports that the February 2026 MS update kills the RPC call to the Domain Controllers for various versions of the UF agent. This results in an MSRPC call storm to all domain controllers over and over until it drains resources. Check your _internal logs for&nbsp;</P><P><SPAN>splunk-winevtlog.exe"" splunk-winevtlog - WinEventLogChannel::init: Failed to bind to DC, dc_bind_time=1579 msec<BR /><BR />splunk-winevtlog.exe"" splunk-winevtlog - Failed to set properties for event; EventRecordID=16354 channel="Application" error=6<BR /><BR /></SPAN>Fix: A restart of the UF service on the local machines fixes the issue.</P> Mon, 16 Feb 2026 13:38:38 GMT https://community.splunk.com/t5/Monitoring-Splunk/February-2026-Patches-Break-RPC-calls-to-DC/m-p/758400#M11083 ASierra 2026-02-16T13:38:38Z https://community.splunk.com/t5/Monitoring-Splunk/February-2026-Patches-Break-RPC-calls-to-DC/m-p/760912#M11138 <P>Hello&nbsp;<a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/235702">@ASierra</a>&nbsp;,</P><P>&nbsp;</P><P>I don't see it in known issue of Splunk. Maybe if you are still having this issue in production, raise Splunk support case to get it fixed.</P><P>&nbsp;</P><P>I hope this helps!!</P> Wed, 13 May 2026 08:13:39 GMT https://community.splunk.com/t5/Monitoring-Splunk/February-2026-Patches-Break-RPC-calls-to-DC/m-p/760912#M11138 VatsalJagani 2026-05-13T08:13:39Z