Sangfor SCP 6.11 failed to add VDC to Workspace (adesk)

lungluk1022 Lv1Posted Aug-06-2025 08:58

i try
Sangfor SCP 6.11 failed to add VDC to Workspace (adesk)

it show error on SCP
Failed to retrieve version information! This could be due to a network issue, the OpenAPI not being enabled in the workspace, or an unsupported workspace version.

NyxZaleTech has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Before troubleshooting, ensure the following:

Network Connectivity: Confirm network connectivity between the Sangfor SCP server and the adesk workspace.

Check for firewalls or network restrictions that might be blocking communication.

User Permissions: Verify that the user attempting to add the VDC has the necessary administrative privileges within Sangfor SCP and access to the adesk workspace.

VDC Configuration: Ensure the VDC is properly configured and ready to be added to a workspace. Review the

VDC's settings, including its network configuration and resource allocation.

Workspace Availability: Confirm that the adesk workspace is available and functioning correctly. Check for any existing errors or issues within the workspace.

Step-by-Step Troubleshooting

Check Sangfor SCP Logs: Examine the Sangfor SCP server logs for detailed error messages related to the VDC addition failure. These logs often provide specific clues about the root cause of the problem. The location of these logs will vary depending on the specific Sangfor SCP installation.
Review Sangfor Documentation: Consult the official Sangfor SCP 6.11 documentation for troubleshooting steps related to VDC management and workspace integration. The documentation might contain specific error codes or solutions.

Restart Services: Restart the Sangfor SCP server and any related services. This can sometimes resolve temporary glitches or inconsistencies.

Contact Sangfor Support: If the issue persists, contact Sangfor technical support for assistance. They can provide expert guidance and support based on your specific environment and configuration. Provide them with detailed information about the error messages, your system configuration, and the steps you've already taken.

Check for Updates: Make sure your Sangfor SCP installation is up-to-date. Outdated software can sometimes contain bugs or incompatibilities that lead to errors.

Additional Considerations

Resource Constraints: Insufficient resources on the Sangfor SCP server or the adesk workspace might prevent the VDC from being added. Monitor resource utilization (CPU, memory, storage, network) to identify potential bottlenecks.

Compatibility Issues: Ensure compatibility between the Sangfor SCP version, the adesk workspace, and any other relevant components in your infrastructure.

Configuration Conflicts: Review the Sangfor SCP and adesk workspace configurations for any potential conflicts or misconfigurations that might be interfering with the VDC addition process.
Is this answer helpful?
lungluk1022 Lv1Posted Aug-08-2025 12:14
  
I checked, maybe not support
DaaS Model               
VDI                  HCI        SCP
VDI5.9.0        HCI6.9.0        SCP6.9.0
VDI5.9.0        HCI6.9.1        SCP6.9.1
VDI5.9.0        HCI6.10.0        SCP6.10.0
VDI5.9.0        HCI6.10.0R1        SCP6.10.0R1
VDI5.9.0        HCI6.10.0R2        SCP6.10.0R1

VDI5.9.6 is not support for DaaS
Newbie337989 Lv2Posted Aug-07-2025 18:32
  
You can try these:

- Check the network connectivity via ping, traceroute or telnet to verify host and port reachability from the SCP to the workspace.

- Ensure firewalls or routing aren't blocking access.

- Ensure OpenAPI Is Enabled on the Workspace
SCP relies on RESTful API endpoints (OpenAPI) to fetch version information.

- Log into the workspace or VDC settings and confirm that API access or OpenAPI is activated.

- Verify Workspace / SCP Version Compatibility
Confirm that you're using a supported workspace version compatible with SCP 6.11.
Incompatible versions may not respond correctly or be blocked.


- Review SCP Logs and Tasks
- Log into SCP as an admin and check the "Tasks" or "Monitoring" section for detailed errors.
- Also review the system logs for API-related errors or timeouts.

- Restart SCP Services If Needed
In some cases, restarting SCP's API or microservices can resolve communication issues.

You can do this via SCP's admin UI under System > Services (if applicable).

I Can Help:

Change

Moderator on This Board

0
9
5

Started Topics

Followers

Follow

Board Leaders

lungluk...

Weekly Questioners