I have CloudSync running and it crashes with the below error:
Bdrive server returned an error. If the issue persists, please contact CloudSync support. Error Code: 502 and a Tracking ID:
The application remains running for 24-48 hours max before it crashes. I have seen previous Topics on this same subject for various OS’s. Is there a fix coming for this? I can’t keep this running to backup my data if the application doesn’t remain running. I am running the latest version 2.2.327.0
Went into Event Viewer and discovered the faulting module is .dll. The file is located in C:\Windows\System32. Is this a dll you dropped on the system as part of the cloudsync installation? If yes, can you please create a different version and provide a new installer?
I have attempted to install this beta 2.3.505 version of CloudSync and it says it is installing. It even tells me it has to reboot my server. I have now attempted to install this twice and twice it has not installed. The ONLY thing that has changed are the dates of the folders in the C:\Programs Files (x86)\bdrive\CloudSync folders are now all with today’s date. All of the files in there and other places are still dated 2018 and older. I open CloudSync itself and the About still shows as 2.2.327 which was released 04/06/2018
There is clearly something wrong with the beta you gave me. This is something to be installed over an existing install, correct? I am running 2.2.327.
The previous link is for installer which downloads latest ‘Public’ version. So it downloaded and installed previous version. Sorry I gave you the wrong link.
It is not a crash message. CloudSync does not crash when this message is displayed. It’s a message box which means a API call to our server returned 502 error. We are looking for the cause of this issue.
I’m sorry there was not enough explanation on the issue.
We uses AWS RDS database to store informations including user’s CloudSync license information and final sync status. After sync CloudSync tries to communication with our server which is running on AES EC2 instances and the server communicates with DB on AWS RDS. While trying to connect to the DB our server experiences DNS resolution error. It’s not related to any of user files.
It seems that the issue does not show up for a day now.