This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

Windows 2012 File Server cluster - issue with adding file share

Question
0

Sign in to vote

Greetings All,

I have physical 2-node (nodes A and B) Windows 2012 Standard cluster with File Server role installed (standard SMB, no CSV/CAFS). Both nodes are alike, hardware and software-wise with the same patching level. LUNs presented for clustering are served by iscsi (EMC VNX).

The issue that I'm running into is when I try to create new shares. While running 'Add File Share -> Quick' wizard from Failover Cluster Manager on node B with file server being active on node A, I don't see my (online) volume available for selection in the 'Share location'->'Select by volume'. It is grayed out. The same when I try to run the wizard locally on the active node. Only when I run the wizard from node A with File Server being active on node B I'm able to see the volume in the wizard. Running the wizard locally on active node yields the same problem.

I'm using Domain Admin account for all above.

As a separate note, I get the following warning message on the first screen when running add file share wizard:

"Unable to retrieve all data needed to run the wizard. Error details: Cannot retrieve information from server (A or B, depending on which node I run it from). Error occurred during enumeration of SMB shares. The WinRM client sent a request to HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support WS-Management protocol"

Obviously I don't have additional roles/features installed to provide support for HTTP based requests but I don't think this is mandatory. Besides, I get the same error even in the only scenario mentioned above that allows me to create shares.

Also, when trying to create new shares from 'Server Manager-> File and Storage Services ->Shares' hangs indefinitely with "loading data...'

Any help with getting new share creation/making volume appear when running the wizard across both nodes consistently working would be greatly appreciated and rewarded.

Thanks,

Peter

Tuesday, October 15, 2013 2:15 AM

All replies

0

Sign in to vote

Hi Peter,

Please try the steps below and see if helps:
1. Update NIC drivers and Teaming Software – Very Important if there is one available

2. Make sure your switch NIC are at Same speed and Duplex levels.
3. Apply these hotfixes, to update clusres and clussvc

http://support.microsoft.com/?id=2687646
http://support.microsoft.com/?id=2795696
http://support.microsoft.com/kb/2531907/EN-US
http://support.microsoft.com/?id=2524732 - tcpip.sys

4. Add the appropriate Exclusion list for Antivirus if any, like exclude the FSW from virus scanning and also the c:\windows\cluster folder

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forum a great place.

Wednesday, October 16, 2013 4:20 PM
0

Sign in to vote

Shaon,

Thanks for the input. However, looking at the aforementioned hotfixes, they all seem to apply to Windows 2008/R2. Windows 2012 is not mentioned there. Again, I'm running the cluster on Windows 2012. Can you confirm whether they all apply to Win 2012 as well?

Regards,

Peter

Thursday, October 17, 2013 5:27 PM
0

Sign in to vote

It's my fault. I must confuse with another thread which has a Windows 2008 R2 system.

Meanwhile have you tried to search for new drivers and the other suggestions?
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forum a great place.

Monday, October 28, 2013 9:39 AM
0

Sign in to vote
I've tried all above recommendations to no avail: latest network drives, stripping NICs out of NIC teaming in Win2012 and patching with hotfixes from here: http://support.microsoft.com/kb/2784261/en-us

Any more suggestions?

Thanks
- Proposed as answer by rahulsharma7 Thursday, November 7, 2013 9:10 PM
- Unproposed as answer by rahulsharma7 Thursday, November 7, 2013 9:10 PM
Tuesday, October 29, 2013 8:08 PM
1

Sign in to vote
Hi ALL,

This issue has been resolved for peter , what you have to check if following group policy is configured on the server :-

computer configuration > administrative templates > windows components > windows remote management > winrm service > Allow remote server management through WINRM

THis is a new policy added in windows server 2012 however is not performing the way it should .

To fix the issue :-

Please remove the above mentioned group policy and and then manually configure winrm via running below command in powershell :-

"winrm qc" and say yes to onfigure the listener and it should work like a charm.
- Proposed as answer by rahulsharma7 Tuesday, November 19, 2013 3:28 PM
Thursday, November 7, 2013 9:15 PM
0

Sign in to vote

I tried the above however it didn't work , please see here for WINRM checking

https://blog.workinghardinit.work/2014/01/28/unable-to-retrieve-all-data-needed-to-run-the-wizard-error-details-cannot-retrieve-information-from-server-node-a-error-occurred-during-enumeration-of-smb-shares-the-winrm-protoc/#comment-1664

Looks like an IPv6/GPO Problem in the end I disable this across both servers and it resolved it!

Tuesday, May 26, 2015 5:20 AM
0

Sign in to vote

This may be an old thread, but I still found this answer useful in 2012 R2. When creating a clustered iSCSI target, I could not create an iSCSI virtual disk until I set that GPO and made sure it took effect on the cluster nodes. This answer should get more attention, because I can't be the only person to have that problem lately.

Wednesday, January 6, 2016 2:29 PM
0

Sign in to vote

Woow.. Thanks this worked for me.

I was creating cluster on windows 2016.

Thanks once again for your help.

Friday, June 23, 2017 6:00 AM