Help Center>
Migration Center>
FAQs>
Migration Workflows>
How Do I Fix the Error "Edge is not accessible" When a Step in the Migration Workflow Fails?
Updated on 2024-05-06 GMT+08:00
How Do I Fix the Error "Edge is not accessible" When a Step in the Migration Workflow Fails?
Edge cannot access the source servers. To resolve this problem, ensure that:
- The Edge server can access port 5985 on Windows source servers.
- The Edge server can access port 22 on Linux source servers.
- Any firewall or antivirus software has been stopped and WinRM has been enabled on Windows source servers. You can run winrm quickconfig to enable WinRM.
Parent topic: Migration Workflows
Migration Workflows FAQs
- Why the Workflow Status Is Always "Running"?
- How Do I View the Migration Progress When the Migration Workflow Is in the Running State?
- How Do I Fix the Error "Edge is not accessible" When a Step in the Migration Workflow Fails?
- How Do I Fix the Error "server require to bind credential first..." When the Migration Workflow Fails on a Source Server?
- How Do I Handle Resource Exceptions during a Batch Server Migration?
- What Are the Known Errors Related to Server Migration Workflows and How Can I Fix Them?
- What Can I Do If an Error Occurs During the Migration of a VMware Server?
- What Are the Information Mappings Between MgC and SMS?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
