GetUserAvailability errors with non-DST timezones using the Exchange Managed API 1.0.

If you see “The Month parameter must be in the range 1 through 12.” thrown using the 1.0 version of the Exchange Managed API when dealing with non-DST timezones, then you should look at upgrading to the 1.1 version of the Exchange Managed API – the issue should be fixed in that version.

Comments (4)

  1. Chris says:

    I have this error using Exchange2007_SP1. It works fine with all user calendars in Sydney timezone, but when calling GetUserAvailability for a Brisbane user's calendar, I get this error. What can I do to fix this?

  2. Webdav101 says:

    Hello Chris;

    The problem is caused by the 1.0 version of the Exchange Managed API and not with Exchange itself.  If you move to the 1.0 version of the API, the problem should go away.  Have you tried the 1.1 version of the API?

  3. Amit says:

    Hi Deniel,

    Thanks for the answer to chris as i was also struggling with the same issue. And now it seems ok. But in addition to the time zone issue i have another problem. I am using exchnage webservice in one of my website and it is hosted in "Sydney, Austrelia" timezone, so when we are booking an appointment to the email id which is in the "Brisbane, austrelia" timezone then the time difference is coming 1hr. because of the daylight saving is running at this point. So i need when user create the appointment it should always create with the sync of Brisbane timezone. Currntly i did a fix by adding 1hr to the time while creating the appoinmtment in the exchnage server. but this fix will not work after the day light saving of Sydney as both Sydney and Brisbane time will be same after the Sydney daylight saving.

    Please help me, as it is bit urgent for me.

  4. Webdav101 says:

    Hello Amit;

    Its best to open a case for that one – its likely going to take time to figure-out.  Oh, be sure to be on the latest service packs and updates so that you have all fixes (including timezone and DST releated).