locked
Internal Server (500) Error when upload to Azure Storage RRS feed

  • Question

  • We're running into a very strange problem. We have a web site running in Azure (not a VM) and an Azure storage account. When running the application locally, we are able to successfully upload objects via app (containers + blobs) to Azure storage. However, when we then deploy that solution to Azure and attempt an upload we receive a 500 error (Internal Server Error).

    We're stumped and have no idea what to do at this point. Has anyone else encountered this problem before? Any idea what we could be doing wrong??

    Thursday, March 20, 2014 8:50 AM

Answers

  • Hi,

    There could be many reasons.

    Check

    • the permission levels of Containers are set properly.
    • Try creating the containers manually and run the app, so you can distinguish what goes wrong
    • Check the URL, storage key, SHA if using it

    -----------------------------------------------------------------------------------------------------

    If you found this post useful, Please "Mark as Answer" or "Vote as Helpful". Best Regards.

    Friday, March 21, 2014 8:25 AM
  • Ok, yes - but is Azure REST service giving the 500, or is your website's code?

    If it is your website code, edit the web.config and turn customError mode to "off" and try the request again. 

    IIS will give you a nice ugly page of error information. 

    By the way, is the website in the same region as the storage account?


    Darin R.

    Monday, March 24, 2014 4:20 PM

All replies

  • Is your app code returning the Http 500 status, or are you only using the Azure storage REST API?

    Darin R.

    Thursday, March 20, 2014 8:16 PM
  • Hi,

    There could be many reasons.

    Check

    • the permission levels of Containers are set properly.
    • Try creating the containers manually and run the app, so you can distinguish what goes wrong
    • Check the URL, storage key, SHA if using it

    -----------------------------------------------------------------------------------------------------

    If you found this post useful, Please "Mark as Answer" or "Vote as Helpful". Best Regards.

    Friday, March 21, 2014 8:25 AM
  • Thanks for taking a look at this. To answer your question, we're just using the Azure storage REST API.
    Monday, March 24, 2014 4:44 AM
  • Hi,

    Are you in North Central US? According to the Dashboard (http://www.windowsazure.com/en-us/support/service-dashboard/ ) shown, Azure storage was maintained.

    Hope it helps.

    Will


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, March 24, 2014 6:46 AM
  • Thanks for your ideas.

    We've created 'public blobs' would allows read access to public, though azure doesn't specify anything regarding read access for which I assume you would need the proper keys.

    As far as the keys are concerned, we know we're working with the proper storage keys since we can upload from an app running locally, unless Azure inexplicably alters the storage keys when we deploy there (I can't imagine why it would).

    Monday, March 24, 2014 7:17 AM
  • Updating this further, we also tried creating the containers manually but unfortunately the behavior is the same.
    Monday, March 24, 2014 9:46 AM
  • Ok, yes - but is Azure REST service giving the 500, or is your website's code?

    If it is your website code, edit the web.config and turn customError mode to "off" and try the request again. 

    IIS will give you a nice ugly page of error information. 

    By the way, is the website in the same region as the storage account?


    Darin R.

    Monday, March 24, 2014 4:20 PM