Learn about the Exchange 2010 Developer Story Today!


We’ve just finished our 6 part series of webcasts on six key topics that developers need to know about as they start planning for moving their applications to Exchange 2010.  Those webcasts are now available as on-demand webcasts.  We’ve updated the webcast links below to point to our on demand videos so check them out today!  If you’d like a bit more human contact than these webcasts, then come join us at TechEd in Germany or Exchange Connections in Las Vegas next week; or the Microsoft Professional Developers Conference in LA November 17-19th where we’ll have great Exchange 2010 Web Services sessions and program managers from the Exchange Web Services team there to answer your questions and get your applications Exchange 2010-ready.


Comments (2)

  1. RobertoMurray says:

    Hello All,

    I am using the GetUserAvailability call for an attendee that is in a timezone (Mumbai,New Deli time zone)that does not have daylight savings time. as a result I get an exception raised when I use the Exchange2007SP1 server version. If I make the service version 2010 format it seems to work without issue.

    Also if I get the service wsdl and use that generated client proxy code to make the request, it works and there seems to be a difference in the GetUserAvailabliltyRequest where it also lets me set a timezoneinfo property and when I set that to the timezone I want my result returned in (Mumbai/New Deli) it works as well.

    I am not sure if this is where I should submit this, but any help you could offer would be great.

    Thank you.

    Rob

    Caught Exception

    System.ArgumentOutOfRangeException: The Month parameter must be in the range 1 through 12.

    Parameter name: month

      at System.TimeZoneInfo.TransitionTime.ValidateTransitionTime(DateTime timeOfDay, Int32 month, Int32 week, Int32 day, DayOfWeek dayOfWeek)

      at System.TimeZoneInfo.TransitionTime.CreateTransitionTime(DateTime timeOfDay, Int32 month, Int32 week, Int32 day, DayOfWeek dayOfWeek, Boolean isFixedDateRule)

      at System.TimeZoneInfo.TransitionTime.CreateFloatingDateRule(DateTime timeOfDay, Int32 month, Int32 week, DayOfWeek dayOfWeek)

      at Microsoft.Exchange.WebServices.Data.LegacyAvailabilityTimeZoneTime.ToTransitionTime()

      at Microsoft.Exchange.WebServices.Data.LegacyAvailabilityTimeZone.ToTimeZoneInfo()

      at Microsoft.Exchange.WebServices.Data.WorkingHours.TryReadElementFromXml(EwsServiceXmlReader reader)

      at Microsoft.Exchange.WebServices.Data.ComplexProperty.LoadFromXml(EwsServiceXmlReader reader, XmlNamespace xmlNamespace, String xmlElementName)

      at Microsoft.Exchange.WebServices.Data.ComplexProperty.LoadFromXml(EwsServiceXmlReader reader, String xmlElementName)

      at Microsoft.Exchange.WebServices.Data.AttendeeAvailability.LoadFreeBusyViewFromXml(EwsServiceXmlReader reader, FreeBusyViewType viewType)

      at Microsoft.Exchange.WebServices.Data.GetUserAvailabilityRequest.ParseResponse(EwsServiceXmlReader reader)

      at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadResponse(EwsServiceXmlReader ewsXmlReader)

      at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadResponse(HttpWebResponse response)

      at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.InternalExecute()

      at Microsoft.Exchange.WebServices.Data.GetUserAvailabilityRequest.Execute()

      at Microsoft.Exchange.WebServices.Data.ExchangeService.GetUserAvailability(IEnumerable`1 attendees, TimeWindow timeWindow, AvailabilityData requestedData, AvailabilityOptions options)

      at Microsoft.Exchange.WebServices.Data.ExchangeService.GetUserAvailability(IEnumerable`1 attendees, TimeWindow timeWindow, AvailabilityData requestedData)

  2. Dan says:

    Hello Roberto – Try the 1.1 version of the Exchange Managed API – it should be fixed in that version.