Storage Replica WinRM error

Question

_{Friday, September 18, 2015 11:23 AM}

I am trying to configure a two node stretched cluster on preview 3.The wizard runs through just fine to select all 4 disks and then throws an error at the end:

 * Failed to create replication.
ERROR CODE : 0x80131500;
NATIVE ERROR CODE : 1.
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.

But I have tried stopping the firewall on both nodes and running WinRM quickconfig gives positive results also.

I can't view the report as that is broken on all features in the new explorer, but looking at the xml on the temp folder there doesn't seem to be any more info.

All replies (18)

_{Friday, October 9, 2015 8:28 PM ✅Answered}

You can use Connect, http://connect.microsoft.com/, to submit issues in Windows Server 2016.

Steven Graves

Windows Beta Support Team

_{Friday, September 18, 2015 11:45 AM}

Trying from powershell gives the same error:

PS C:\Windows\system32> New-SRPartnership -SourceComputerName SQL06A -SourceRGName rg01 -SourceVolumeName S: -SourceLogV
olumeName M: -DestinationComputerName SQL06B -DestinationRGName rg02 -DestinationVolumeName S: -DestinationLogVolumeName
 M:

WARNING: Failed to locate cluster resource group for replication group rg01 in cleanup step. Manually remove Storage
Replica dependency between cluster disk resources in the resource group.
New-SRPartnership : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the com
puter is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access
from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers with
in the same local subnet.
At line:1 char:1

• New-SRPartnership -SourceComputerName SQL06A -SourceRGName rg01 -Sour ...

    + CategoryInfo          : ConnectionError: (MSFT_WvrAdminTasks:root/Microsoft/...T_WvrAdminTasks) [New-SRPartnersh
   ip], CimException
    + FullyQualifiedErrorId : HRESULT 0x80338126,New-SRPartnership

PS C:\Windows\system32>

_{Friday, September 18, 2015 11:56 AM}

looking at failover cluster manager while the powershell script runs, gives a hint that it is pretty far before it rolls back

_{Monday, September 21, 2015 8:23 AM}

Hi,

Please test to use the FQDN instead of NetBIOS name to see if it makes any difference. Also please noticed that it could be true that it is an issue in current version of Windows Server TP. If it will still not work I'll log the result and report. 

Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Wednesday, September 23, 2015 4:44 PM}

I just tried it with FQDN but the same error occurs and then rolls back.

My setup is two guests running preview 3, on a Windows Server 2012 R2 Hyper-V.

The shared storage is provided by using shared VHDX.

Please log this as it would be very great to get this up and running.

_{Thursday, September 24, 2015 6:46 PM}

0x80338126 (ERROR_WSMAN_NETWORK_TIMEDOUT)

 That error means WMI is not getting through and it's giving up (after 60 sec, usually). It's something to investigate in the network, firewall, third party security software, etc. Not an SR issue I can fix, sorry.

Ned Pyle [MSFT] | Principal Program Manager for Storage Replica, DFS Replication, Scale-out File Server, SMB, other stuff

_{Friday, September 25, 2015 6:25 AM}

Hmm, I hear what you say and from the WinRM error I would also have thought this.

But this is two virtual machines, running on the same physical host.

Their network cards are in the same virtual switch and they are on the same IP subnet.

They are joined to the same active directory domain.

I have completely disabled the Windows firewall on both virtual machines.

The cluster could be created with no problems and all remote management of the hosts from one to the other works.

the "winrm quickconfig" command returns it is running and ready for remote connections on both guests.

So my thinking was, something times out and then the error handler thinks it is WinRM.

I don't know what else to check on the WinRM side to rule it out.

Is there a more detailed log somewhere I can look into for the configuration of storage replica?

_{Friday, September 25, 2015 7:27 PM}

hang tight, we found a similar issue. It's a very rare repro, you are unlucky. :| I will reply when we know or need data.

Ned Pyle [MSFT] | Principal Program Manager for Storage Replica, DFS Replication, Scale-out File Server, SMB, other stuff

_{Monday, September 28, 2015 7:57 PM}

Michael, can you manually offline and online the Cluster Name resource, then try this again?

Ned Pyle [MSFT] | Principal Program Manager for Storage Replica, DFS Replication, Scale-out File Server, SMB, other stuff

_{Tuesday, September 29, 2015 9:48 PM}

Manually offline and online the Cluster Name resource unfortunately did no change.

I also tried to reboot both hosts and still I get the same error.

_{Wednesday, September 30, 2015 6:18 PM}

I has just joined the WSSC TAP program and installed the build from last week in the hopes it solved it.

But, I cant figure out how to add the storage replica feature in that build.

Is there a better way to discuss the latest TAP build?

_{Monday, July 25, 2016 8:55 PM}

I am also seeing this issue in TP5.

Test-SRTopology using the same disks/volumes works fine but when trying to set up replication in the cluster I get the error:

Failed to create replication.
ERROR CODE : 0x80131500;
NATIVE ERROR CODE : 1.
The WinRM client cannot process the request because the server name cannot be resolved.

_{Monday, July 25, 2016 9:02 PM}

I am also seeing this issue in TP5.

Test-SRTopology using the same disks/volumes works fine (tested before disks added into cluster) but when trying to set up replication in the cluster I get the error:

Failed to create replication.
ERROR CODE : 0x80131500;
NATIVE ERROR CODE : 1.
The WinRM client cannot process the request because the server name cannot be resolved.

I cannot see an option at http://connect.microsoft.com/ to log issues for Server 2016. 

_{Thursday, August 18, 2016 4:05 AM}

I am also seeing this in TP5 with a similar setup, 2 nodes, same subnet, no firewall. Test-SRTopology returns no errors, but when trying to enable replication through failover cluster manager I get.

David A. Bermingham, MVP, Senior Technical Evangelist, SIOS Technology Corp

_{Thursday, August 25, 2016 2:20 PM}

i'm getting the same error.

did someone find a fix?

_{Tuesday, June 20, 2017 9:35 PM}

I know this is an older thread, but it's the only one I've come across that matched my error.  Ultimately I fixed it, so I wanted to update.

For me, it was a situation where the Cluster Resource did not have rights to update its own DNS entry.  We will ultimately be moving to a VXLAN, but for now we're testing using DNS with a TTL set at 300 seconds for the roles and cluster node names.

There were other issues, such as not being able to access the cluster using Failover Cluster Manager on any non-cluster-node computers, nor could  I RDP into the cluster name directly, only to the nodes. My cluster resided on one of the nodes in the remote datacenter, however the DNS entry was still registered to the local datacenter subnet.  I failed to assign the cluster resource control over its own DNS record during the initial build. 

If you run into this, make sure that the IP address in DNS matches the cluster resource.  This is what was causing my WinRM issues.  Once corrected everything worked like it should.

_{Friday, June 15, 2018 12:18 PM}

I'm setup Storage Replication in test environment and all was ok. 

But when i try to setup it in production i am got the same issue. I'm noticed, when i connect from local to local server with command New-CimSession -ComputerName MyServer i got the same error with WS-Management. 

disabling ipv6 helped me, and i can setup storage replica without issues. 

reg add HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents /t REG_DWORD /d 0xff

_{Friday, August 24, 2018 6:45 AM}

I just thought I would add this in case it helps anyone else - I had exactly this situation.

The problem was actually that the template we deployed the guest VMs I was configuring as the stretch cluster members had a winhttp proxy setting in it, which these VMs could not resolve or connect to as they were on an isolated test network.

I removed that with a netsh winhttp reset proxy to set it back to direct, and then everything worked.

Peter