Good day All,
Welcome back!!!
Recently we had a urgent request to remove a 16 TB drive and after removing it from cluster we started to see the below error.
Following steps was performed:
1. Stopped all the shares which are part of sharing
2. Removed the disk from File share role and moved to available disk
3.Unassigned the drive letter and removed it from cluster
4. Asked Storage team to reclaim the disk and it all went fine.
When we logged to failover cluster then this error was showing up and then we got to Server Manager we unable to load volumes or shares.
Following errors was observed:
MS blog site was pointing to check if Winrm is all working fine or not and check the logs on it
1. Winrm qucikconfig
Winrm is already running
winrm is already set
2. winrm id -r:Server name
i saw below output but when i run the same command on the working server i got this output
So i realized that there is something wrong with Winrm not able to communicate.
https://blogs.technet.microsoft.com/askcore/2015/11/23/errors-retrieving-file-shares-on-windows-failover-cluster/
https://lokna.no/?p=1531
About article goes over different Winrm issues fixes but the logs refer to HTTP and if you see my event log it is not pointing to HTTP at all
Solution:
When i ran the below command found that it was pointing to a decomm proxy server name
netsh winhttp show proxy
So went ahead and run the below command to reset the proxy and removed the proxy
netsh winhttp reset proxy
closed the Server Manager and re-opened and it all was working fine.
To be true even though this fixed the issue i am still not clear how a working Server when a disk was removed this error showed up and removing proxy was the fix is not something corilating
If anyone can figure out then please let me know..
Hopefully this helps someone until next one you all have good day!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Welcome back!!!
Recently we had a urgent request to remove a 16 TB drive and after removing it from cluster we started to see the below error.
Following steps was performed:
1. Stopped all the shares which are part of sharing
2. Removed the disk from File share role and moved to available disk
3.Unassigned the drive letter and removed it from cluster
4. Asked Storage team to reclaim the disk and it all went fine.
When we logged to failover cluster then this error was showing up and then we got to Server Manager we unable to load volumes or shares.
Following errors was observed:
MS blog site was pointing to check if Winrm is all working fine or not and check the logs on it
1. Winrm qucikconfig
Winrm is already running
winrm is already set
2. winrm id -r:Server name
i saw below output but when i run the same command on the working server i got this output
So i realized that there is something wrong with Winrm not able to communicate.
https://blogs.technet.microsoft.com/askcore/2015/11/23/errors-retrieving-file-shares-on-windows-failover-cluster/
https://lokna.no/?p=1531
About article goes over different Winrm issues fixes but the logs refer to HTTP and if you see my event log it is not pointing to HTTP at all
Solution:
When i ran the below command found that it was pointing to a decomm proxy server name
netsh winhttp show proxy
So went ahead and run the below command to reset the proxy and removed the proxy
netsh winhttp reset proxy
closed the Server Manager and re-opened and it all was working fine.
To be true even though this fixed the issue i am still not clear how a working Server when a disk was removed this error showed up and removing proxy was the fix is not something corilating
If anyone can figure out then please let me know..
Hopefully this helps someone until next one you all have good day!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANK YOU! Needless to say, i was chasing this for hours to realize, after reading your article that this is what it was for me as well and this is something my teammate set and i would never suspect it otherwise....
ReplyDelete