The cluster identity may lack permissions required to update the object

Lucas Peñaloza 671 Reputation points
2025-12-02T20:36:56.19+00:00

Dear;

Hi have the message:

The computer object associated with the cluster network name resource 'Cluster Name'

could not be updated in domain 'xxx.xxx.xxx.xxx.xxx' during the

Password change operation.

The text for the associated error code is: The specified network password is not correct.

The cluster identity 'CLPWGIRSQL$' may lack permissions required to update the object.

Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Please tell me what I need to check

Thank you so much!!!.

Windows for business | Windows Server | Storage high availability | Clustering and high availability
Answer accepted by question author
VPHAN 44,300 Reputation points Independent Advisor
2025-12-29T21:01:36.1466667+00:00

Hello Lucas Peñaloza,

I wanted to follow up to see if you successfully completed the upgrade of the final node (PWGIRSQL1) and failing back your resources.

To summarize our last discussion regarding your final step:

The Risk: Update-ClusterFunctionalLevel is irreversible, but it is safe as long as all nodes are online, running the new OS, and you have passed the Test-Cluster validation.

The Strategy: There is no rush. You can leave the cluster in "Mixed Mode" for a few days to verify stability before running the command to lock in the new features.

If your cluster is now fully upgraded and stable, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
VPHAN 44,300 Reputation points Independent Advisor
2025-12-18T15:55:23.51+00:00

Hi Lucas Peñaloza,

You are definitely correct to be cautious about High Availability (HA). While a Windows Cluster can technically run with one node on a new OS and two on the old OS (Mixed Mode), your approach minimizes risk significantly.

By updating both Secondary nodes (PWGIRSQL2 and PWGIRSQL3) before you ever touch the Primary (PWGIRSQL1), you ensure that when you finally perform the failover:

  1. Stability: You are failing over to a new OS node (PWGIRSQL2) that already has another new OS partner (PWGIRSQL3) ready to sync.
  2. Redundancy: If something goes wrong with PWGIRSQL2 immediately after the upgrade, you have PWGIRSQL3 (also upgraded) as a safety net.

The Approved Execution Order:

  1. Update PWGIRSQL2 (OS + SQL).
    • Result: Node 2 is healthy and syncing again.
  2. Update PWGIRSQL3 (OS + SQL).
    • Result: Node 3 is healthy and syncing again.
    • State: Now you have 2 upgraded nodes waiting in the wings.
  3. Failover the Availability Group from Node 1 to Node 2.
    • Result: Your Production is now running on the New OS.
  4. Update PWGIRSQL1 (The old Primary).

This is the safest, most professional way to execute a 3-node cluster upgrade. Proceed with confidence.

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. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
VPHAN 44,300 Reputation points Independent Advisor
2025-12-15T14:54:40.93+00:00

YES, absolutely. You must always begin your upgrade process with the Secondary Replicas. Since your cluster is now healthy, the safest rolling upgrade workflow is to upgrade the passive nodes first, leaving the active Primary (PWGIRSQL1) untouched until the very end to keep your application online.

Here is the recommended sequence:

Phase 1: Upgrade the Secondary (PWGIRSQL2)

Since PWGIRSQL2 is already a Secondary replica and you just stabilized it, it is the perfect candidate to start with.

  1. Backup: Take a full backup of your databases on the Primary (PWGIRSQL1) just in case.
  2. Suspend Data Movement (Optional but Recommended): In SSMS, you can temporarily suspend data movement for the PWGIRSQL2 replica if the upgrade will take a long time (to prevent the transaction log on the Primary from growing too large while waiting).
  3. Perform the Upgrade: Apply your Operating System updates or SQL Server patches/upgrades on PWGIRSQL2.
  4. Reboot & Validate: Restart PWGIRSQL2. Once it is back online, open SSMS on the Primary and verify that PWGIRSQL2 returns to the Synchronized (or Synchronizing) state. Phase 2: Upgrade the Next Secondary (PWGIRSQL3)

Once Node 2 is green and fully synced, repeat the process for PWGIRSQL3.

Phase 3: The Failover (Switch Roles)

Once both Secondaries (Node 2 and Node 3) are upgraded and healthy:

  1. Change the Availability Mode of PWGIRSQL2 to Synchronous Commit (if it isn't already).
  2. Perform a Manual Failover of the Availability Group from PWGIRSQL1 to PWGIRSQL2.
    • Now PWGIRSQL2 is the Primary and is running the new version.
  3. Verify applications are connecting successfully. Phase 4: Upgrade the Old Primary (PWGIRSQL1)

Now that PWGIRSQL1 is a passive Secondary, you can safely proceed to upgrade it.

VP

Was this answer helpful?

1 person found this answer helpful.
0 comments

49 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 44,300 Reputation points Independent Advisor
    2025-12-12T06:40:44.2733333+00:00

    Hi,

    You have a very sharp eye, but I can assure you: The difference in the name ("Ethernet Adapter" vs "Ethernet Adapter #2") is completely cosmetic and irrelevant. It simply means the network driver was reinstalled or the virtual NIC was removed and re-added on the other nodes at some point. Windows just increments the number (#2, #3) to avoid duplicates. It has zero impact on the cluster.

    The real problem is confirmed in your screenshot of PWGIRSQL2: NetworkCategory: Public

    Why is this killing Node 2? When a network is set to Public, the Windows Firewall applies its strictest policy: "Block all unsolicited inbound traffic." Even though Node 1 and Node 3 might be showing "Up" (likely due to existing cached sessions or specific rule exceptions from when they were built), Node 2 is a "new" member. It is trying to establish a new handshake on port UDP 3343, and the Public Firewall profile on Node 2 is silently dropping those packets.

    So here is the fix:

    You must force Windows to trust this network on the new node: Open PowerShell (Administrator) on PWGIRSQL2.

    Run this exact command to flip the switch:

    Set-NetConnectionProfile -InterfaceAlias "Ethernet1" -NetworkCategory Private

    Wait 30 seconds. Go back to Failover Cluster Manager (Image 4). You should see the status for PWGIRSQL2 on Cluster Network 2 change from Failed to Up.

    Optional: I noticed in that PWGIRSQL3 also has this network set to Public. While it is currently "working," this is risky. If that node reboots or resets its connection, it might get blocked too. Once Node 2 is fixed, I highly recommend running the same command on Node 1 and Node 3 to ensure all Heartbeat networks are correctly set to Private.

    VP

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. VPHAN 44,300 Reputation points Independent Advisor
    2025-12-12T02:57:54.54+00:00

    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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.