Monitoring Splunk

February 2026 Patches - Break RPC calls to DC

ASierra
Explorer

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 

splunk-winevtlog.exe"" splunk-winevtlog - WinEventLogChannel::init: Failed to bind to DC, dc_bind_time=1579 msec

splunk-winevtlog.exe"" splunk-winevtlog - Failed to set properties for event; EventRecordID=16354 channel="Application" error=6

Fix: A restart of the UF service on the local machines fixes the issue.

Labels (3)
Tags (1)
0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

Hello @ASierra ,

 

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.

 

I hope this helps!!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...