1

Resolved

Error while backing up file (500) Internal Server Error

description

I am trying to backup a Server 2003 SP2 server and created a test file on the root of the C: drive and modified the .config file as shown in the documentation and I get the following error:

Error While backing up file C:\backuptest\AzureBackup.msi: The remote server returned an error: (500) Internal Server Error.

I can see that the attempted backup job created a container in my Azure storage using the name of my backup job, test, although there is no data there as it obviously failed.

The changes made to the .config file was the name of my Storage in Azure as well as inputing the primary access key.

Please see the attached log file.

file attachments

comments

bitNine wrote Apr 8, 2014 at 2:52 PM

This is extremely old, but did you make sure that the command window in which AzureBackup is running, is in administrator mode? Seeing that it created the container, means that it connected properly, but the 500 error is confusing. The only thing I can think of is that the file is in the root of C, and inaccessible by AzureBackup in some strange way.

bitNine wrote Apr 18, 2014 at 10:02 PM

I just ran into this error on one of my servers. I will now be able to look much closer at the issue and hopefully fix it.

bitNine wrote Jan 16, 2015 at 6:59 PM

I've figured out the problem here. This isn't necessarily a bug, but the error message is quite misleading.

When uploading a file to Azure, it provides the server with a reasonable timeout period for uploading the specific file to the server. This is calculated based on the value provided in the upload speed option within the xml config file for azurebackup.

I noticed that our connection speed from one of our servers was quite slow one day, and was only uploading at around 384KB/sec, and not the theoretical 50Mbit speeds we should see. Some files failed every time, and they were usually the smaller ones.

Lower the upload speed in your XML config file to something more reasonable... Maybe even just set it to 1. That should fix the issue.

wrote Jan 16, 2015 at 10:25 PM