Failover Cluster – Node won’t join to cluster. EventID: 1135

Today, I had issue with one of the node cluster. After installing DPM agent on one of the nodes, the Server didn’t want to join to cluster. The error like this is not something to be happy about.

Cluster node ‘ServerName’ was removed from the active failover cluster membership.!

EventID 1135- Node was removed from active Failover cluster membership.

From cluster logs, I could see lot of event ID:1135

Moving protected server from one DPM to another DPM.

In this blog, we will cover moving protected server from one DPM to another.

In addition, we will refer to DPM from you want to move  as Old DPM.

In addition, we will refere to DPM you want to move as New DPM.

Event ID 1025— Cluster failed to bring clustered role “VM1” online…

Event ID 1254 and 1069.

I came across with issue of unable to start VM. The affected resource was Virtual machine configuration file was “lost”

The event shows that Event ID 1254 and 1069.

SCCM and WSUS (Cannot open Database “SUSDB”)

 

Today, I came a cross with alert on my SCCM console regarding SUP synchronization.

 

After looking into WMC.log. The error log indicates that WSUS is unable to open and connect to DB. (internal DB)

 Cannot open database “SUSDB” requested by the login. The login failed.~~Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’.~~