Jump to content

Recommended Posts

Posted

I have setup a new Server 2016 Hyper-V Failover Cluster on a Dell VRTX. Both hosts are running Server 2016, passed all cluster validation tests, and seem to be working properly.

However, on each boot of either host, they log a Kernel-EventTracing error, event id 2:

 

Session "{598c599e-80ee-4b3a-81fc-59f151341b28}" failed to start with the following error: 0xc0000035.

 

This error also occurs if I manually restart the Cluster Service service.

 

From my initial research, it seems this error code sometimes indicates some type of name collision in the performance monitor event trace sessions. I located an event trace session called {598c599e-80ee-4b3a-81fc-59f151341b28}. If I delete this event trace session and restart the Cluster Service, the error does not get logged, but it does recreate the event trace session which will cause the error to occur next time.

 

Any ideas on how to resolve this? It logs as an error, which clutters up the event logs.

 

Thanks!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...