Hi All,
I'm getting the server error 0 message while configuring the workload in SRM 8.1, Please someone help here.
I've changed the browser and restarted the appliance and SRM servers but nothing helped.
Anyone from VMware team can advise on this or shall i open a another case with VMware Support Team. 😞
are you running the latest release of 8.1?
last time I checked it was 8.1.0.4 with many fixes. worth considering. if you are already on that code sounds like a support call.
have you had other problems with SRM 8.1?
I'm running SRM 8.10.16 and there was no error apart from this. Last time we had a same issue but it was related to browser but this time i don't have any clue what to do.
Thanks anyway for your response.
Not familiar with that version. from the release notes 8.1.0.4 was released less than 2 weeks ago
VMware Site Recovery Manager 8.1.0.4 | 24 AUG 2018 | Build 9569154
VMware Site Recovery Manager 8.1.0.3 | 12 JUN 2018 | Build 8738384
VMware Site Recovery Manager 8.1.0.2 | 18 MAY 2018 | Build 8527244
VMware Site Recovery Manager 8.1.0.1 | 20 APR 2018 | Build 8311425
Note: VMware Site Recovery Manager 8.1.0.1 | 20 APR 2018 | Build 8311425 replaces the previously released VMware Site Recovery Manager 8.1 | 17 APR 2018 | Build 8255892
VMware Site Recovery Manager 8.1 | 17 APR 2018 | Build 8255892
Hi,
according to the Release notes for SRM 8.1.0.4 - VMware Site Recovery Manager 8.1 Release Notes this issue is fixed.
You can double check your SRM version is up to date and upgrade to 8.1.0.4 if needed, also you can try with browser Firefox.
Hope this helps,
Daniel G.
Its actually listed as fixed in 8.1.0.1
NEW When you configure virtual machines for replication, the Site Recovery user interface might show an error "Server Error Response with status: 0 for URL: null"
When you are using the Site Recovery HTML5 user interface to select VMs to replicate to the recovery site, the UI might throw an error "Server Error Response with status: 0 for URL: null"
This issue is fixed.
However as 8.1.0.4 is the newest release I would advise to go to that code.
My guess (and its only that) is that you are on the GA 8.1 release hence the problem
This issue is fixed in SRM/vSphere Replication 8.1.0.4. (it exists in 8.1.0.1)