Constant Log - event id 2050 on windows server 2019 failover Cluster

WonKi Lee 1 Reputation point Microsoft Employee
2020-10-29T06:04:49.937+00:00

I got a constant log in every 5 minutes on my failover cluster, windows server 2019.
Despite of these messages, all failover cluster features work fine.
Is it safe to ignore this?

Log Name: Microsoft-Windows-FailoverClustering/Diagnostic
Source: FailoverClustering
Event ID: 2050

Unhandled exception on the thread 6100, exception The requested operation is not supported.

where can I start with troubleshooting this message?

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,451 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
957 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xiaowei He 9,871 Reputation points
    2020-10-29T08:12:14.367+00:00

    Hi,

    Yes, we can ignore the logs. As far as I know, event 2050 exists in Cluster Diagnostic log, if the cluster is running well, the event 2050 can be ignored.

    Similar case for your reference:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/659a6c47-46f6-49ab-902a-d546fb8bc7a7/constant-log-error-id-2050-and-2051-after-added-fc-storage-and-made-it-ha-with-cvs

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments