Graph API error when using calendar: getSchedule

Meriem Djouaher 41 Reputation points

Hello! We are developing a Java API to manage clients' calendars and we using calendar: getSchedule in Graph API to know if the resource is busy or free to schedule meetings later. When sending a request with multiple resources, we get a 200 HTTP status code, but once parsing the response we realize that for one of the resources we have the following error: Proxy web request failed with error ResponseCode: 5037. Message: The caller does not have access to free/busy data... Could you please help me identify what can cause this error? A more detailed response from Graph can be found on the attached file client.txt We are using delegated permission to access calendar: getSchedule. Thank you for your time, Regards, Meriem Djouaherr:

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,808 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. HarmeetSingh7172 4,811 Reputation points

    Hello Meriem Djouaher, Thanks for reaching out! When a user tries to view free/busy information for a remote user, the free/busy information isn't displayed. Instead, the user may experience one or more of the following symptoms:

    • The free/busy information for the remote user is displayed as number sign (#) characters in the Calendar.
    • In Outlook Web App, "error 5037" is displayed.
    • The Microsoft Outlook <FileName>-fb.log and <FileName>-as.log files contain an error message that resembles the following:
    • <FreeBusyResponse><ResponseMessage ResponseClass="Error"><MessageText>The caller does not have access to free/busy data.</MessageText><ResponseCode>ErrorNoFreeBusyAccess</ResponseCode><DescriptiveLinkKey>0</DescriptiveLinkKey><MessageXml><ExceptionType xmlns="">Microsoft.Exchange.InfoWorker.Common.Availability.NoFreeBusyAccessException</ExceptionType><ExceptionCode xmlns="">5037</ExceptionCode><ExceptionServerName xmlns=""> ServerName</ExceptionServerName><ResponseSource xmlns="">https://\<Server></ResponseSource></MessageXml></ResponseMessage><FreeBusyView><FreeBusyViewType xmlns="">None</FreeBusyViewType></FreeBusyView></FreeBusyResponse>

    Please follow this documentation to know about symptoms, cause and resolution for this issue. Hope this helps. If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.

    0 comments No comments

  2. Meriem Djouaher 41 Reputation points

    Hello HermeetSingh-MSFT!
    Thank your for your response!
    I had a look at the documentation you provided, and it looks like it is related to EWS (exchange) responses.
    However we are using Graph API, does the documentation still work for Graph?

    Thank you!
    Meriem Djouaher

    0 comments No comments