Overview
Client vs Server Errors help distinguish whether a connection issue originates from the local Softdrive client (user device) or from the remote desktop server (Cloud PC).
Understanding the difference allows users to take the correct next steps and helps support teams triage issues more efficiently.
Client Errors
Client errors occur when the issue originates on the user’s local device or within the Softdrive client application.
Characteristics:
Error occurs before or during connection setup
Often temporary or device-specific
May resolve by retrying, restarting, or reinstalling the client
Common examples:
Error Code 06 – ClientException
An unexpected and uncategorized error within the Softdrive client.Installation or dependency-related errors
Server Errors
Server errors occur when the issue originates from the remote desktop server or Softdrive backend services.
Characteristics:
Error occurs after connection initiation
Not dependent on the user’s local device
May affect multiple users or sessions
Common examples:
Error Code 07 – ServerException
An unexpected and uncategorized error on the remote desktop server.Temporary backend or service-side instability
What Should You Do?
| Error Type | Recommended Action |
|---|---|
| Client Error | Retry the connection, restart the client or device, reinstall Softdrive if needed |
| Server Error | Wait a few minutes and retry; contact support if the issue persists |
If you are unsure whether an issue is client-side or server-side, retrying the connection once is always recommended.
If the issue continues to occur, please contact Softdrive Support.
When opening a support ticket, include as much detail as possible:
Error code displayed
Timestamp of the issue
Cloud PC name and organization
Screenshots of the error
Email: support@softdrive.co
Providing clear details helps the Softdrive team quickly identify whether the issue is client-side or server-side.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article