Validating File and Print Sharing network binding error

Hello,

Hopefully somebody can assist me.

Problem:  I am trying to create a 2 node failover cluster using starwind and Windows Server 2012.  While conducting validation I get a failure in the storage area, with the message of "Unexpected error while validating File and Print Sharing network binding on node (Server 1 and 2): The server threw an exception."

Setup: 2 Dell R720s with 2 software mirrored drives for the OS, and 14 additional drives (Hardware Raid 0) for data (total of 11TB).  Starwind installed, and running correctly, with iSCSI drives recognized and syncing.  4 NICS (1 for local network, 1 for heartbeat, and 2 for iSCSI traffic).  When validating or trying to create the cluster, above failure indicated.

Steps taken so far: Rebooted several times.  Since it was a storage failure, I first contacted Starwind, who worked with me for 2 hours, but after verifying their software was working, indicated they had not seen the error before.  I have verified and played with the network binding orders, and messing with the Microsoft File and Sharing on the NICS.  Still have not been able to get past this error.

Any help in resolving this would be greatly appreciated.

Thank you,

Frank

July 13th, 2013 12:37am

Anybody?
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2013 4:48pm

I've had the same issue, it was seen after our 2012 R2 cluster lost all the network connections from the Control Panel view and they had to be removed/uninstalled  from Device Manager and then manually re-created. 

The validation report shows the following error

Unexpected error while validating File and Print Sharing network binding on node XXXXXXcom: The server threw an exception.

We are also seeing the following error in the Application log each time we try and run the cluster validation test 

Faulting application name: CPrepSrv.exe, version: 6.3.9600.17111, time stamp: 0x5360a93f
Faulting module name: CPrepSrv.exe, version: 6.3.9600.17111, time stamp: 0x5360a93f
Exception code: 0xc0000005
Fault offset: 0x0000000000045887
Faulting process id: 0x2398
Faulting application start time: 0x01d01546fca9796c
Faulting application path: C:\windows\System32\CPrepSrv.exe
Faulting module path: C:\windows\System32\CPrepSrv.exe
Report Id: 3b092a26-813a-11e4-80e6-40a8f02ce351
Faulting package full name: 
Faulting package-relative application ID: 

The Validate Storage.log file show the following errors as well

00002398.0000239c::2014/12/11-13:33:14.053  FinalRelease: INFO: failed to delete the test user, error=2221

00002398.0000239c::2014/12/11-13:33:14.053  FinalRelease: INFO: failed to delete the test share, error=87

  • Edited by Bob_Marsh Thursday, December 11, 2014 1:55 PM
December 11th, 2014 4:48pm

Hello,

I am also facing the exactly same issue. Failover Cluster console shows Node1 is Up and Node2 is Down.

Cluster Event on Node2 shows "Attempting to use IPv4 for 'Microsoft Failover Cluster Virtual Miniport' network adapter failed. This was due to a failure to disable IPv4 auto-configuration and DHCP. This may be expected if the DHCP Client service is already disabled.  IPv6 will be used if enabled, otherwise this node may not be able to participate in a failover cluster."

On running the Validate Configuration test of this cluster, it throws the error: "Unexpected error while validating File and Print Sharing network binding on node Node2: The server threw an exception."

DHCP Client and Cluster Service, both of these services are running on both nodes. I have also tried restarting both of these services on Node2. Then I manually removed and reinstalled the network adapter from Device Manager on Node2. Then tried rebooting the Node2. The issue is still unresolved.

Node1 and Node2 are able to Ping each other. We are using Static IP addressing for all servers.

Please help and advice.

Thank you.

~ Hasan Bin Hasib

Free Windows Admin Tool Kit Click here and download it now
December 16th, 2014 6:50am

We have been looking at this with Microsoft support, They are still unsure of cause or solution but have suggested/requested we get the NIC drivers updated and the file and print sharing component uninstalled , server restarted and the component re-installed.

Maybe you can try this as well to see if it resolves the problem for you.

December 16th, 2014 7:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics