The cluster identity may lack permissions required to update the object

Vphan;

It's a relief to read your comment.!!!.

Indeed, look;

I believe that everything is correct, to level SID.

Now, Re Join PWGIRSQL2 to Cluster and Pray that everything works out!!!.

What do you Think?

Vphan

Never finish the Installation!!!

What do you Think?

Hi Lucas,

First, this is actually great news regarding the SIDs. I have reviewed your screenshots, and I can confirm your environment is now safe from the "Identity Crisis":

PWGIRSQL1: SID ends in ...1738-500.

PWGIRSQL2: SID ends in ...2762-500.

PWGIRSQL3: SID ends in ...6669-500.

You have successfully achieved unique identities for all three nodes. The root cause of your original cluster failure is gone.

Now, regarding the installation hang on PWGIRSQL2, dont worry. This is a very common side effect of a fresh Sysprep or Domain Join. The Server Manager GUI often hangs because the background "Windows Modules Installer" service is either waiting on a generic Windows Update check (which might time out if the server has no internet) or is blocked by a pending reboot flag left over from the domain join.

To unstick the Installation:

1. Force a Reboot Since the GUI is stuck, you cant cancel it gracefully.

Close the "Add Roles and Features Wizard" (use Task Manager to kill it if necessary).

Reboot PWGIRSQL2 immediately. This will clear the locked files and reset the TrustedInstaller service.

2. Install via PowerShell: Once the server is back online, dont use the GUI Wizard, it hides the actual errors. Use PowerShell, which is faster and provides real-time feedback.

Open PowerShell as Administrator on PWGIRSQL2. Run the following command:

Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools

3. What if it hangs again? If the PowerShell command hangs at "10%" or "24%", it means the server is trying to download source files from Windows Update and failing.

=> You need to mount the Windows Server ISO (the installation media) to the server (e.g., as drive D:).

Run the command specifying the local source:

Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools -Source D:\sources\sxs

Once the feature shows Success: True in PowerShell, you are ready to add the node to the cluster.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer then. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Vphan,

        Look

PS C:> Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools

Success Restart Needed Exit Code Feature Result

True No Success {Remote Server Administration Tools, Failo...

And;

Cluster network interface 'PWGIRSQL2 - Ethernet1' for cluster node 'PWGIRSQL2' on network 'Cluster Network 2' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

PWGIRSQL2, has 2 NICs

Ethernet1, is the Backup Net.

I believe the mistake is irrelevant, no

Hi Lucas,

The PowerShell output confirms the Failover Clustering feature is now successfully installed on PWGIRSQL2. You are past the installation hang!

Regarding your question about the network error, i__t is NOT irrelevant.__ While the cluster might "work" temporarily over just the primary network, ignoring this error breaks your High Availability. If your main network (Ethernet0) experiences a hiccup, PWGIRSQL2 will instantly disconnect from the cluster because it has no backup path.

In your screenshot, Ethernet1 is listed as "Unidentified network".

When a network adapter has no Default Gateway (which is correct for a Backup/Heartbeat network), Windows cannot identify the network. Windows automatically assigns "Unidentified" networks to the Public Firewall Profile. Consequently, the Public Firewall Profile blocks UDP 3343 (Cluster Heartbeat). This is why you see Event 1127, the cluster is trying to talk on that backup line, but the Windows Firewall is silently dropping the packets.

To fix (Do this immediately on PWGIRSQL2), you need to force Windows to treat that "Unidentified" network as Private so the firewall opens the ports.

Open PowerShell as Administrator on PWGIRSQL2 and run this command:

Set-NetConnectionProfile -InterfaceAlias "Ethernet1" -NetworkCategory Private

Verification:

Run Get-NetConnectionProfile. You should see Ethernet1 listed as Private instead of Public.

Go back to Failover Cluster Manager on Node 1. The error regarding Cluster Network 2 should clear up within a minute, and the interface status should turn Up.

Once that interface is green, your node has full redundancy. You are almost at the finish line!

VP