Skip to Content
Author's profile photo Karl-Heinz Hochmuth

Windows Failover cluster log cannot be generated

Sometimes, I am unable to generate cluster logs for specific cluster nodes on Failover clusters running on Windows Server 2012 or higher.

The problem always looks like this:

The cluster log on the third cluster node “wsiv1092” cannot be generated and there are no problems with the other cluster nodes.


In this blog, I will explain how to find the root cause for the problem and the solution.


First, let’s take a closer look at the error message:

“Retrieving the COM class factory for remote component with CLSID {88E7AC6D-C561-4F03-9A60-39DD768F867D}”

There are two important things in this sentence: The COM method is being used to call the remote host and the GUID of the component: 88E7AC6D-C561-4F03-9A60-39DD768F867D

In Windows application log, you see a similar error event:

Start Windows Registry Editor and search for the GUID: 88E7AC6D-C561-4F03-9A60-39DD768F867D (in your case, the GUID is of course different !)

Open the LocalServer32 key:

That’s the application which should be contacted on the remote cluster node: CPrepSrv.exe

For some reason, this executable doesn’t work properly anymore.

Logon to the related cluster node and open Windows Taskmanager:

You should see at least one process. Kill the process! If you see two of them, kill them both.

Don’t worry! This will not affect cluster operations. If there are two processes running, then somebody generated the cluster log locally on this cluster node, which usually works fine.

Then start the generation of the cluster logs again.


get-clusterlog – destination C:\temp -uselocaltime -timespan 60


Which will now work fine! 🙂


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.