Partager via

One of the request inputs is out of range Error with Azure Table Storage

  • Article

I wanted to document this error here because I recently went nearly blind trying to solve it, and I never did find the exact cause when Bing'ing for it.  Unfortunately it's a pretty generic error so it may very well have been out there, but it seems there are several reasons for it.  In my case I created a new instance of a class that I was adding to my Azure table but it kept failing with this "One of the request inputs is out of range" error that was driving me absolutely nuts.  Fortunately some bright individual pointed out to me that my class contained a DateTime property, and I wasn't initializing it.  Apparently the default DateTime.MinValue in .NET is outside the bounds of what Azure table storage supports.  So I just put in a dummy date in my property and - voila! - everything started working again.

So just a heads up in case you see this error yourself - it seems like a pretty easy one to miss.

Hope everyone has a happy holiday season!

Comments

  • Anonymous
    January 01, 2003
    Came across this error using queues. Solution for my case: blog.codingoutloud.com/.../azure-error-one-of-the-request-inputs-is-out-of-range

  • Anonymous
    January 01, 2003
    Thank you, its useful

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Thanks for sharing this. It helped me..

  • Anonymous
    January 01, 2003
    msdn.microsoft.com/.../microsoft.windowsazure.storageclient.cloudtableclient.minsupporteddatetime.aspx

  • Anonymous
    January 01, 2003
    please share if you find any documentation on this

  • Anonymous
    January 18, 2012
    The most annoying thing is that dev storage doesn't enforce this restriction, so you get different results than running in live. There are various small corner cases like this (another is that DateTimes are silently truncated to milliseconds).

  • Anonymous
    September 28, 2012
    Thanks a lot for this. It saved a day for us.

  • Anonymous
    January 08, 2013
    The comment has been removed

  • Anonymous
    April 05, 2013
    Thanks Steve, thankfully it didn't take me too long to find what's going wrong and come across your post.

  • Anonymous
    August 02, 2013
    The comment has been removed

  • Anonymous
    September 18, 2014
    The comment has been removed