0

I'm having the same issue as Azure table storage returns 400 Bad Request, but only when deploying the webjob. When running it locally towards the same queues and table storage it works fine. As soon as I deploy it to azure it wont run and returning 400 Bad Request when I check the log stream.

  • I've checked all DateTime properties, and they should be fine now.
  • I'm doing checks that the table exists.
  • No special characters in partition or row key.
  • Insertion operation is InsertOrReplace.

Object structure:

image

Community
  • 1
  • 1
Filiwiks
  • 65
  • 1
  • 5
  • Can you please share the data you're trying to enter in the table. As mentioned in the answer you linked, 400 error is caused because of user error. – Gaurav Mantri Nov 16 '16 at 10:07
  • http://imgur.com/T72tpUq This is the object structure. – Filiwiks Nov 16 '16 at 11:29
  • 1
    I edited your question to include your image (please don't embed these in comments). At this point you should edit your question to show the pertinent snippet of code. A bit difficult to tell what's happening without seeing what you're actually doing. – David Makogon Nov 16 '16 at 11:47
  • 2
    Please try to capture the `StorageException` and log the detailed error of `StorageException.RequestInformation.ExtendedErrorInformation` when deploying to Azure. With the detailed error, we could locate this issue. – Bruce Chen Nov 17 '16 at 03:14
  • Yeah can you add the revelant code – Thomas Nov 17 '16 at 05:43

0 Answers0