![]() Work with your network admins to unblock any connection issues. Because of the variety of firewall software that might be in use, we can't list all required firewall configurations. Check whether any firewall rules on the source machine need to be added or removed for the source machine to talk to the configuration server.Use the URI Ensure that the source machine can reach the configuration server through port 443. To resolve, connect to the configuration server IP address by using a web browser on the source machine.It also might occur if a firewall blocks TLS communication between the source machine and the configuration server. This error might occur because the configuration server certificate has expired or the source machine doesn't support TLS 1.0 or later protocols. If the string post request: (7) - Couldn't connect to server isn't found, in the same log file, look for the string request: (60) - Peer certificate cannot be authenticated with given CA certificates. When network issues are resolved, retry the registration by following the guidelines in Register the source machine with the configuration server.Ensure that the folders listed in Site Recovery folder exclusions from antivirus programs are excluded from the antivirus software.Check whether any firewall rules on the source machine block the connection between the source machine and the configuration server.Ensure that the source machine can reach the configuration server through port 443. Verify that the configuration server is reachable from the source machine by using network tools like ping, traceroute, or a web browser. Resolve the network issues between the source machine and the configuration server.Search for the string post request: (7) - Couldn't connect to server. If you don't see the ProgramData folder, in File Explorer, on the View tab, in the Show/hide section, select the Hidden items check box.) Failures might be caused by multiple issues. (The ProgramData folder might be a hidden folder. If the string Reason=>NULL isn't found, on the source machine, open the C:\ProgramData\ASRSetupLogs\UploadedLogs\ASRUnifiedAgentInstaller.log file. After you resolve the issues, follow guidelines in Register the source machine with the configuration server to retry the registration manually.This error occurs if the source machine uses an empty host to register with the configuration server. ![]() If the string No Valid IP Address found isn't found, search for the string Reason=>NULL. Run one of the following commands on the source machine to get all the IP addresses of the source machine:.For agent registration with the configuration server to succeed, the source machine must have at least one valid IP v4 address assigned to the physical NIC. Verify that the source machine has at least one IP address assigned to the physical NIC.Verify that the requested host ID is the same as the host ID of the source machine.Search for the string No Valid IP Address found. Open the C:\ProgramData\ASR\home\svsystems\var\configurator_register_host_static_info.log file. You can debug any failures during this step by following these guidelines: The source machine registers with the configuration server when you install the mobility agent. ![]() The following sections discuss the most common failures you might experience when you add a new configuration server and when you manage a configuration server. ![]() Use the configuration server to set up disaster recovery of on-premises VMware VMs and physical servers to Azure by using Site Recovery. The configuration server acts as a management server. This article helps you troubleshoot issues when you deploy and manage the Azure Site Recovery configuration server.
0 Comments
Leave a Reply. |