Server 2022 Cluster Validation Network - Invalid Namespace

Braddo 41

I am trying to setup my first Failover Cluster running Server 2022
all looks ok during setup, however when Validation runs, i get an error with
Switch Enabled Teaming Configurations
Unable to connect to Server A via WMI, this may be due to networking issues or firewall rule configuration on Server A
Invalid Namespace

i have 2 network adaptors on each server
1 for Cluster only, 10.25..
1 for network, 10.190..

Jack, Digrad 6 Reputation points

2021-10-22T08:41:26.227+00:00

+1
We're having the same problem.
New 2022 cluster setup, and we're getting the "Invalid Namespace" error during cluster validation.
We get the same error when running the validation against just one of the two servers that are suppose to be in the cluster.
We can ignore the error and continue creating the cluster, but the cluster seems to be instable (giving us BSOD when accessing the shared SAS storage, for example).
Sorry to say, we have not found any solution to this error yet.
jam7 6 Reputation points

2021-10-26T18:06:33.797+00:00

@Limitless Technology @Jack, Digrad @Braddo

We are also facing the same issue with brand new hardware and Server 2022. Anyone come up with a cause / solution, yet? We have built and re-rebuilt the servers on Windows 2022 Datacenter and Windows 2022 Standard.

Before creating the NIC teams we ran the validation test to see if the network portion would still fail even with the most basic network configuration possible, and it still does.
Braddo 41 Reputation points

2021-10-27T01:44:59.803+00:00

surely someone has a working 2022 server cluster that can assist us?
Aspall IT 436 Reputation points

2021-10-29T20:00:26.713+00:00

I'm getting this too also on Server 2022.
Can't find anything online to explain what this is actually trying to validate or what the cause of this error is.

I have checked WinRM and WMI configs and all seems ok.
We are not using NIC teaming and only have 2 NICs, one for cluster and one for client traffic.

Must be some kind of bug in 2022?

Has anyone deployed a cluster even after getting this error to confirm the cluster still operates correctly?
jam7 6 Reputation points

2021-10-29T20:09:27.753+00:00

@Aspall IT Welcome to the club. We have also consulted with Dell Pro Support and they do not see any issues with our configuration or hardware either. Dell is suspecting a 2020 bug also. Other than the validation failure, the cluster is operating how we expect a cluster to operate.

While it is not ideal to deploy to a production environment with a known failure, if we do not uncover any functional issues from our end user testing, we will likely promote the cluster to production. Fingers crossed for Microsoft to acknowledge and fix before we cutover.
Braddo 41 Reputation points

2021-10-29T20:36:18.087+00:00

ii'm gonna try and configure teaming on 2 nics to see if this is what it requires..
i can't put our cluster into prod, as this is for SQL, and the SQL install validatres the cluster and as it fails, SQL cannot install
jam7 6 Reputation points

2021-10-29T20:50:22.353+00:00

Our configuration is for SQL too. We do have teaming and we are able to get SQL 2019 to install without issue. SQL appears to be absolutely fine with the cluster. Other than the validation issue, our IT side testing has produced no issues. We are going to introduce end user testing next week.
Braddo 41 Reputation points

2021-10-30T05:01:56.447+00:00

during the install it questions the cluster validation, and isn't able to continue?
jam7 6 Reputation points

2021-11-11T18:40:21.687+00:00

As a matter of an update:

We have engaged Microsoft on the issue and do not have a solution on the CV namespace error.

In regards to our SQL 2019 Enterprise installation with this cluster, our testing has surfaced consistently inconsistent assertion errors. We have also engaged Microsoft on that issue and are awaiting guidance on that too. Until we have confidence in a solution, our deployment plans are on hold.
Braddo 41 Reputation points

2021-11-11T20:02:41.83+00:00

i too have engaged MS and they are not being very helpful at all
i have had remote sessions with them, and sent logs etc.
they even sent me commands to run, Sfc and dism commands, the basic of all basic - no good

they are 'trying to replicate' it in their own environment.
hopefully the more people that try and use this clustering in 2022 will contact MS when it fails
Jay Antoney 16 Reputation points

2021-11-12T02:35:46.157+00:00

I've logged a Partner Support Case & escalated with my account manager and I'm commenting here mostly so if you have an update I get a notification as well.
My setup is 2 x brand new Server 2022 Data Centre edition with LUN passthrough attached disks.
The cluster is running fine, we can failover and it's all working - but this NameSpace error is preventing me installing SQL 2019 cluster.

In the event there is a Microsoft Rep looking at this in the future, then I'll make sure the solution is attached to my case number 2111120060000396 - so look that up.
Jay Antoney 1 Reputation point

2021-11-12T03:06:28.443+00:00

Hey all - Any chance you could post up your Microsoft Support case numbers please?

I would like to escalate with my account manager and see if they can say 'Hey there might actually be a problem here' to the engineering team.
Braddo 41 Reputation points

2021-11-12T11:41:22.277+00:00

Hi
i haven't raised mine with premier support as yet as it isn't business critical

here is my support case however

Incident title: isse validating cluster, network fail, WMI, invalid namespace
Support request number: 2110310060000236
Severity rating: C

cheers
Brad
jam7 6 Reputation points

2021-11-12T13:44:15.197+00:00

Our Case Number is 2111100040005807
Angel M 1 Reputation point

2021-11-14T23:02:37.097+00:00

Dear all,

Same error in my case deploying two WS2022 in cluster mode. I hope that Microsoft fix it with an update.
I will follow your comments.

Many thanks for your help.
Good luck.

Regards,
Jay Antoney 16 Reputation points

2021-11-25T02:12:10.717+00:00

Hey everyone - Got an update from Microsoft today and this has been confirmed as a bug in Server 2022 where the solution isn't deployed on a HyperV server.
Basically, it's not checking to see if it's a HyperV server before running the checks and is therefore just running (and failing) the HyperV checks anyway.

A patch is being developed and will be released soon.

If you are deploying SQL cluster, then there is a work around here:
https://learn.microsoft.com/en-us/troubleshoot/sql/failover-clusters/error-install-sql-server-windows-server-cluster#workaround

I'll let you know once the patch has been released.

Jay
jam7 6 Reputation points

2021-11-25T02:19:40.087+00:00

Thanks Jay
Mu'ath Al-Kayyal 1 Reputation point

2021-12-16T12:34:41.517+00:00

Hi gemidriver,

Is there any update regarding above issue, We are running with windows 2022 on VMware and trying to configuring the Failover cluster for File sharing servers.
Mu'ath Al-Kayyal 1 Reputation point

2021-12-16T12:35:22.81+00:00

Hi gemidriver,

Is there any update regarding above issue, We are running with windows 2022 on VMware and trying to configuring the Failover cluster for File sharing servers.
Erik Tank 21 Reputation points

2022-03-26T04:52:06.06+00:00

Well I too have been dealing with this on and off for a few weeks now. Even if I do not use SET at all and have just one 10gb NIC assigned per function without any teaming or SET at all - I still fail the validation test when trying to validate the switch enabled teaming configurations...

Validating Switch Embedded Teaming Settings.
An error occurred while executing the test.
The given key was not present in the dictionary.

Even from scratch on three HP DL380 Gen10 systems with 4 10gb ports and 4 1gb ports.

I setup 1 NIC for live migration, 1 nic for cluster traffic, 1 nic for management, and two 10gb nics for MPIO iSCSI connections. All have separate VLANs and all can ping and transfer data per IP properly - validation always passes when I skip SET validation, but ALWAYS fails regardless of actually using SET or not.

What hardware is everyone using? If it helps solve anything my HPE servers have one Flexilom 10gb dual port 534FLR card and one PCIE 562SFP+ card (dual ports). The 1 gig ports are the standard built-in 331i HP brand NICs.

I have tried with RDMA on and off, with SR-IOV on and off (both via drivers, and disabling in BIOS), Jumbo frames on and off, and tried with teaming on and off in some situations - also with NO virtual NICs (just the switch with $false for management OS connectivity). I THINK I have tested every combination here - with three servers as well as just two in hopes it was a trifecta bug... I'm spent - not sure what to do here.

6 answers

Braddo 41 Reputation points

2021-11-17T22:20:05.333+00:00

here is the latest info i got from MS
not an answer for me - we are using ESX, and not HyperV

Currently I found the reason for the validation failure in our official documentation, it's because the LBFO technology in Windows Server 2022 has been deprecated and SET Team needs to be used instead.

You can use the following PowerShell(run in the host) to set up SET Team and disable LACP on the switch side.

New-VMSwitch -Name SETswitch -NetAdapter "Ethernet1", "Ethernet2" -EnableEmbeddedTeaming $true

Add-VMNetworkAdapter -SchalterName SETswitch -Name SMB_01

Add-VMNetworkAdapter -SchalterName SETswitch -Name SMB_02

Document

=================================

Features removed or no longer developed starting with Windows Server, versions 1903 and 1909
https://learn.microsoft.com/en-us/windows-server/get-started/removed-deprecated-features-windows-server-1903-1909
Feature Explanation
Hyper-V vSwitch on LBFO In a future release, the Hyper-V vSwitch will no longer have the capability to be bound to an LBFO team. Instead, it must be bound via Switch Embedded Teaming (SET).

Please use the above command and change the network infrastructure as the NIC group option of Server Manager is not available on the 2022 server, and we recommend that you test it in a test environment.
Please sign in to rate this answer.

1 person found this answer helpful.
Prabhjot Singh 1 Reputation point

2022-01-11T17:20:53.777+00:00

Dear Experts,

I have only one ethernet on both servers in cluster. My windows VM are running on ESX host. Kindly help me, How should I set up SET Team on the switch side.
Or
I need to follow other instructions.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN22FCIN2
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Tunnel adapter Local Area Connection* 10:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-90-0E-21-21-B7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5d0f:2c1:fec0:2324%4(Preferred)
IPv4 Address. . . . . . . . . . . : 169.254.2.26(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0

Ethernet adapter Ethernet0 2:

DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.96.80(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 172.16.100.1
DHCP Server . . . . . . . . . . . : 172.16.0.55
DHCPv6 IAID . . . . . . . . . . . : 369101865
DNS Servers . . . . . . . . . . . : 172.16.101.140
Primary WINS Server . . . . . . . : 172.16.0.55

Your help is much appreciated.
Sign in to comment
Ankush Bansal 6 Reputation points

2022-05-16T17:24:10.627+00:00

Hello Guys,

Found the fix here for the issue.
I have patched my machine completely still getting the issue.
I checked and found that Microsoft has released some Preview updates which does not get installed automatically:

https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

I Installed the April Patch released by the Microsoft and seems this resolved my issue.
https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

You can download it from the Microsoft Catalog update and install it on the Nodes and then restart them.
Once applied on both the Nodes, perform the cluster validation and it has worked for me as I am also using VMWare 7.1

Please let me know your feedbacks and likes if it works so that I could try to check and help you with another resolution which might help.

Thanks
Please sign in to rate this answer.

1 person found this answer helpful.
Ben Rosenqvist 21 Reputation points

2022-05-19T10:51:44.51+00:00

I have updated my 2022 cluster with the 2022-05 CU, and the first validation is now completing. Nothing in the release notes though...

https://support.microsoft.com/en-us/topic/may-10-2022-kb5013944-os-build-20348-707-05509703-187a-4d5b-97f5-8793dbb22991

Ankush Bansal 6 Reputation points

2022-07-15T10:05:50.34+00:00

According to the Preview update which has a bug fix for the RPC Errors that we are getting which is related to Name Spaces:
https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

Which is later Included in the May Patch to fix all the machines facing this issue:
https://support.microsoft.com/en-us/topic/may-10-2022-kb5013944-os-build-20348-707-05509703-187a-4d5b-97f5-8793dbb22991

Fix in the Preview Update:
Addresses an issue that causes Kerberos authentication to fail, and the error is “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This occurs when a client machine attempts to use the Remote Desktop Protocol (RDP) to connect to another machine while Remote Credential Guard is enabled.

I believe this helps understand why we can install this update and check if the issues are fixed.
As Kerberos authentication is needed for the RPC Service to validate the Namespaces.
Sign in to comment
Limitless Technology 39,331 Reputation points

2021-10-15T19:55:41.83+00:00

Hi @Braddo

Attempt to start the cluster service on all nodes in the cluster so that nodes with the latest copy of the cluster configuration data can first form the cluster. This node will then be able to join the cluster and will automatically obtain the updated cluster configuration data. You can find the logs and resolution here cross-verify your log and try out the possible resolution for it.
Failover Clustering system log events https://learn.microsoft.com/en-us/windows-server/failover-clustering/system-events

------
--If the reply is helpful, please Upvote and Accept as answer--
Please sign in to rate this answer.
Braddo 41 Reputation points

2021-10-15T20:39:50.027+00:00

hi, my cluster is up and running. however during validation i get the network error
i have a 2019 cluster setup and working for years. this new validation has only appeared in server 2022
there are no errors in the cluster event log

Braddo 41 Reputation points

2021-10-21T10:25:33.623+00:00

is anyone able to advise any thing to try?
Sign in to comment
Jay Antoney 1 Reputation point

2021-11-15T00:36:07.957+00:00
Small update for everyone.
This isn't an Answer - It's just too big to be a comment apparently. Sorry in advanced :(

After having spent some time on the phone with Microsoft support and a fair amount of debugging, we think we've found the call that the process is making and failing on.
I've also passed on your other Microsoft support case numbers so hopefully they can get as many examples as possible of issues.

Here are the tests that my case managers asked me to do and upload. I have no idea if you doing it as well and uploading to your case would help them, but for the sake of documenting here they are.

CMD PROMPT (not powershell)

fltmc instances > c:\fltmcnode--%computername%.txt

reg save HKLM\Cluster c:\cluster--%computername%.hiv

tasklist /svc > c:\tasklist--%COMPUTERNAME%.txt

Capture a trace - Again CMD not PowerShell

Run the following 5 commands logman create trace "wmi-trace" -ow -o c:\wmi-trace--%COMPUTERNAME%.etl -p "Microsoft-Windows-WMI" 0xffffffffffffffff 0xff -nb 16 16 -bs 1024 -mode Circular -f bincirc -max 200 -ets
logman update trace "wmi-trace" -p {1418EF04-B0B4-4623-BF7E-D74AB47BBDAA} 0xffffffffffffffff 0xff -ets
logman update trace "wmi-trace" -p {2CF953C0-8DF7-48E1-99B9-6816A2FBDC9F} 0xffffffffffffffff 0xff -ets
logman update trace "wmi-trace" -p {1FF6B227-2CA7-40F9-9A66-980EADAA602E} 0xffffffffffffffff 0xff -ets
logman update trace "wmi-trace" -p {8E6B6962-AB54-4335-8229-3255B919DD0E} 0xffffffffffffffff 0xff -ets

Run the Validation of the Windows Failover Cluster. Personally I only ran the test that was failing as per screen shot below.

Stop the trace using logman stop "wmi-trace" -ets

Upload the 4 files in the root of C to the case.

From this, they found the following line in the traces that seems to be the issue.

32749 [5] 0B1C.0890::11/12/21-13:42:56.4140835 [latest] wbemname_cpp8984 CWbemNamespace::UniversalConnect() - NewScope = \\{COMPUTERNAME}.xx.xx.xx\root\virtualization\V2 UserName=xx\{USERNAME} ClientMachineName={COMPUTERNAME} ClientProcessID=3004 … 32801 [5] 0B1C.0890::11/12/21-13:42:56.4143114 [latest] crep_cpp1841 CRepository::OpenScope() - HR_Return == 8004100e 32802 [5] 0B1C.0890::11/12/21-13:42:56.4143166 [latest] wbemname_cpp584 CWbemNamespace::Initialize() - HR_Return == 8004100e 32803 [5] 0B1C.0890::11/12/21-13:42:56.4143309 [latest] wbemname_cpp746 CWbemNamespace::Initialize() - HR_Return == 8004100e 32804 [5] 0B1C.0890::11/12/21-13:42:56.4143321 [latest] wbemname_cpp774 CWbemNamespace::~CWbemNamespace() - 32805 [5] 0B1C.0890::11/12/21-13:42:56.4143376 [latest] wbemname_cpp9142 CWbemNamespace::UniversalConnect() - HR_Return == 8004100e 32806 [5] 0B1C.0890::11/12/21-13:42:56.4143408 [latest] wbemname_cpp9239 CWbemNamespace::PathBasedConnect() - HR_Return == 8004100e 32807 [5] 0B1C.0890::11/12/21-13:42:56.4143561 [latest] coresvc_cpp911 CCoreServices::GetServices3() - HR_Return == 8004100e 32808 [5] 0B1C.0890::11/12/21-13:42:56.4143595 [latest] login_cpp1267 CWbemLevel1Login::LoginUser() - HR_Return == 8004100e
Please sign in to rate this answer.
Prabhjot Singh 1 Reputation point

2022-01-13T16:36:43.43+00:00

I'm getting the same error, and my machines are on VMware ESX host using single NIC. It would be great if you can guide me to resolve the issue.

AlteredAdmin 121 Reputation points

2022-02-01T12:27:49.32+00:00

Good morning @Braddo @Prabhjot Singh @Jack, Digrad @jam7 @Aspall IT @Mu'ath Al-Kayyal @Limitless Technology @Jay Antoney ,

Pinging everyone that is in this conversation.

We just stood up 3 Clusters 2 noes each using windows 2022 and we are having the same issue.

Validate Switch Enabled Teaming Configurations Cluster Validation Failure

Both nodes are server 2022 fully patched.

Both nodes are running on VMware ESXI/vSphere.

Validate Switch Enabled Teaming Configurations Description: Validate that Switch Enabled Teaming configuration, if present, is consistent between cluster nodes. Start: 1/31/2022 12:34:31 PM. Validating Switch Embedded Teaming Settings. An error occurred while executing the test. Unable to connect to SQL22-DEV-N01.DOMAIN.org via WMI. This may be due to networking issues or firewall configuration on SQL22-DEV-N01.DOMAIN.org. Invalid namespace Stop: 1/31/2022 12:34:31 PM.

.From reading this post it appears that its a bug in WMI Namespace and it cannot validate the cluster because of this?

Has anyone else been able to find a solution or a work around for this issue?

Has any one from Microsoft Acknowledged the issue?

Installing SQL on the cluster is not an option when it cant be validated.

Thoughts?

Braddo 41 Reputation points

2022-02-01T19:36:38.27+00:00

I installed via command line ignoring validation
MS know is an issue, but don't seem to be doing anything about it

AlteredAdmin 121 Reputation points

2022-02-01T21:17:35.333+00:00

Thanks, yea ignoring validation is not an option for us. But wanted to make sure Microsoft is aware of the issue.

Ben Rosenqvist 21 Reputation points

2022-02-16T09:59:30.61+00:00

assuming no one has heard anything yet? Would love to get these new clusters online

Ankush Bansal 6 Reputation points

2022-05-16T17:27:39.333+00:00

Found the fix here for the issue.
I have patched my machine completely still getting the issue.
I checked and found that Microsoft has released some Preview updates which does not get installed automatically:

https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

I Installed the April Patch released by the Microsoft and seems this resolved my issue.
https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

You can download it from the Microsoft Catalog update and install it on the Nodes and then restart them.
Once applied on both the Nodes, perform the cluster validation and it has worked for me as I am also using VMWare 7.1

Please let me know your feedbacks and likes if it works so that I could try to check and help you with another resolution which might help.

Thanks
Sign in to comment
Braddo 41 Reputation points

2021-12-02T22:16:15.967+00:00

i have feedback from MS, and that is this only works with HyperV vms. doesn't work with vmware..

According to the information from product team, I got a report that we have received a few cases with the same symptom recently. We are basically sure your issue exactly matches this known symptom.

SET is skipped when I run the verification in my environment because the node is a virtual machine, what I was told by the product team is that this is normal because SET verification is done on the physical machine to detect if the hyper-v virtual machine role is installed on the physical machine.

But we see that your node is identified as a physical machine, at which point SET starts validation, but since your virtual platform is VMware, this results in the validation showing a failure.

So we can currently unvalidate the SET when validating the cluster or wait for the next update of server 2022, although the timing of the update is uncertain, but I will keep following up.

Again I apologize for any inconvenience this issue has caused to you. If there is anything else I can assist you with, please feel free to let me know. Have a nice day!
Please sign in to rate this answer.
Mu'ath Al-Kayyal 1 Reputation point

2021-12-16T12:26:17.957+00:00

Hi gemidriver,

Is there any update regarding above issue, We are running with windows 2022 on VMware and trying to configuring the Failover cluster for File sharing servers.

Braddo 41 Reputation points

2021-12-16T19:26:17.76+00:00

My update is that I installed sql via command line ignoring validation tests
Until MS can fix it to work with VMware

Ankush Bansal 6 Reputation points

2022-05-16T17:27:27.227+00:00

Found the fix here for the issue.
I have patched my machine completely still getting the issue.
I checked and found that Microsoft has released some Preview updates which does not get installed automatically:

https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

I Installed the April Patch released by the Microsoft and seems this resolved my issue.
https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d

You can download it from the Microsoft Catalog update and install it on the Nodes and then restart them.
Once applied on both the Nodes, perform the cluster validation and it has worked for me as I am also using VMWare 7.1

Please let me know your feedbacks and likes if it works so that I could try to check and help you with another resolution which might help.

Thanks
Sign in to comment