WSFC Failover Cluster: The service has returned a service-specific error code

Hello.

I want to create a Windows Server Failover Cluster. The cluster validation is successful, with one warning, because there is just one networkadapter per machine. A second for splitting client-traffic and cluster-traffic is already in planning .

The process of the cluster creation ends through a timeout (GUI aswell Powershell).
Error: Error creating cluster “CLUSTERNAME”. The service has returned a service-specific error code

Basic conditions: 2x SQL-Server, Windows Server 2022, same subnet, fixed IPs. Virtualization with ESXi /vSphere. Onprem

Output of the Error report, executed from Node2:

Configuration of the “CLUSTERNAME” cluster is started.
Cluster “CLUSTERNAME” is initialized.
Cluster status on node “FQDN Node2” is checked.
The domain is searched for the computer object “CLUSTERNAME”.
Search for a suitable domain controller for the node FQDN Node2.
Search for a suitable domain controller for the node FQDN Node2.
Check whether the CLUSTERNAME computer object for the FQDN Node2 node exists in the domain. Domain controller \\FQDN DC.
The computer object for “CLUSTERNAME” does not exist in the domain.
Search for a suitable domain controller for the node FQDN Node2.
Create a binding to the domain controller \\FQDN DC.
Check whether the computer object FQDN Node2 for the node FQDN Node2 exists in the domain. Domain controller \\FQDN DC.
A new computer account (object) for “CLUSTERNAME” is created in the domain.
The computer object is created in the organizational unit OU-PFAD in which the node FQDN Node2 exists.
Create the CLUSTERNAME computer object on the domain controller \\FQDN DC in the OU-PFAD organizational unit.
Installation of the network FT driver on node “FQDN Node2” is checked.
Installation of the cluster disk driver on node “FQDN Node2” is checked.
Cluster service on node “FQDN Node2” is configured.
Installation of the network FT driver on node “FQDN Node1” is checked.
Installation of the cluster disk driver on node “FQDN Node1” is checked.
Cluster service on node “FQDN Node1” is configured.
Waiting for notification that the cluster service has been started on node “FQDN Node2”.
Cluster “CLUSTERNAME” is formed.
Error during the process, cleanup is attempted.
Error creating the cluster. The nodes are being cleaned up. Please wait...
Error creating the cluster. The nodes are being cleaned up. Please wait...
Error cleaning up the cluster nodes. Use “Clear-ClusterNode” to clean up the nodes manually.
Error cleaning up the cluster nodes. Use “Clear-ClusterNode” to clean up the nodes manually.
Error creating the cluster. Error creating cluster “CLUSTERNAME”.  The service has returned a service-specific error code 
Run the Configuration Verification Wizard for the servers you want to include in a cluster to resolve cluster creation issues.

Translated with DeepL.com (free version)

The Eventlog tells me nothing specific. After ignoring the errors coming up for trying cleaning the cluster and nodes there is not much left.

FailoverClustering-Manager -> Diagnose. The changes getting reversed, after some successful entires.

(...)

Validation: Computer name 'CLUSTERNAME' can be used as 'CLUSTERNAME' NetBIOS name.
[CWFX] Closing netapi handle.

That leaves:

Creating the cluster failed - System.ApplicationException: Error when creating cluster "CLUSTERNAME". ---> System.ComponentModel.Win32Exception: The service has returned a service-specific error code. --- End of internal exception batch monitoring --- bei MS.Internal.ServerClusters.Cluster.Create(String clusterName, StringCollection nodeNames, ICollection`1 ipAddresses, ClusterActionCallback callback, AdminAccessPoint managementAccessPoint, AdminAccessPointResType CNOResType) bei MS.Internal.ServerClusters.Configuration.CreateClusterConfigurationNoCno.PerformCreateCluster(ActionArgs actionArgs, ActionUpdateHelper updateHelper) bei MS.Internal.ServerClusters.Configuration.CreateClusterConfigurationNoCno.PerformAction(ActionArgs actionArgs) bei MS.Internal.ServerClusters.Configuration.CreateClusterConfigurationNoCno.InternalPerformAction(ActionArgs actionArgs)

Windows Firewall:

There are only drops for Port UDP 5355, because both Nodes spitting massively mDNS into the network while installation.

Is mDNS needed for successfully installing Failover Cluster? I could not read anything about it and have Multicast DNS disabled via GPO.

Some other Eventlog warnings:

[VER] Could not read version data from database for node NODE1 (id 2).
Runtime error in PrMgrImpl::SetKey@608, Status=The device is not in the correct state for this request.
[IM] Route from IP-NODE2:~3343~ to IP-NODE1:~3343~ is already up, not sending report
mscs::ListenerWorker::operator (): GracefulClose(1226)' because of 'channel to remote endpoint IP-NODE1:~61253~ is closed'
cxl::ConnectWorker::operator (): GracefulClose(1226)' because of 'channel to remote endpoint IP-NODE1:~3343~ is closed'
[CAM] CAMTranslateNameToSID - Could not lookup name, error c0000073
FatalError: CAM Notify Credentials failed (status = 1385)
FatalError: CAM Notify Credentials failed (status = 1385), executing OnStop
FatalError is Calling Exit Process.

Conclusion:

I did research and looked in several logs but I dont really know where to dig deeper to find the reason for this problem.

I will be very thankful for your input. Thank you!