Getting below error while running labels available to the organization after providing the required permission
https://graph.microsoft.com/beta/informationProtection/policy/labels
{
"error": {
"code": "UnknownError",
"message": "502 Bad Gateway",
"innerError": {
"date": "2020-11-24T07:12:06",
"request-id": "3fa2b70d-79fd-4ade-b16d-1250be2771a1",
"client-request-id": "02b1ac97-21c6-75c4-0cbb-403ab53a1108"
}
}
}
HTTP 502 tells that the API call service is unavailable at the time, when you tried calling. I would suggest you to test the same after sometime to see if it works. If you still see the issue, you can report the issue back here. Also i see that its under beta endpoint, which is not meant for production environments
Related
When I execute a request for a specific callRecord like this it works:
https://graph.microsoft.com/v1.0/communications/callRecords/{id}
But when I do this I get an error (500):
https://graph.microsoft.com/v1.0/communications/callRecords/{id}?$expand=sessions
{
"error": {
"code": "InternalServerError",
"message": "Object reference not set to an instance of an object.",
"innerError": {
"date": "2022-04-14T12:21:34",
"request-id": "{guid}",
"client-request-id": "{guid}"
}
}
}
It looks like this doesn't happen for every callRecord though. We started seeing this error in our logging around 2022-04-11T00:24:00Z, now we get thousands of those.
It was an internal issue on Microsoft's side. Everything seems to be fixed.
When accessing data using https://graph.microsoft.com/beta/teams/{id}, it is failing with 400 bad request without any error details. {id} is the value received from the response of https://graph.microsoft.com/beta/groups.
Following response is returned.
{
"error": {
"code": "AuthenticationError",
"message": "Error authenticating with resource",
"innerError": {
"date": "2021-10-15T15:01:43",
"request-id": "1d82fe40-5186-46fc-9fb7-c16341eb1ffb",
"client-request-id": "29c9e68d-bfd8-6f53-65c4-c49a82581a76"
}
}
}
We tried using MS graph SDK as well as graph explorer. All the consent are given for the end point.
What could be the reason for the error?
I'm trying to track changes on a sharepoint drive but I got an obscure error message.
Here my call:
https://graph.microsoft.com/v1.0/drives/{direvId}/root/delta
And here the response:
{
"error": {
"code": "InternalServerError",
"message": "nextLink value without skip or skiptoken",
"innerError": {
"date": "2021-02-03T16:38:03",
"request-id": "4cb9de13-817d-47c7-a0b3-2605470789b9",
"client-request-id": "4cb9de13-817d-47c7-a0b3-2605470789b9"
}
}
}
Any clue?
EDIT:
The issue is releated to the application access token.
Ok I found the issue. Using postman and having the header Prefer set as follow Prefer: apiversion=2.1 was causing the 500 error.
With no Prefer header set or using the headers suggested in the documentation everything is working as expected.enter link description here
We do run the GET call:
https://graph.microsoft.com/v1.0/teams/711fc163-0408-4649-9a30-af65a5d30b52/channels
It used to return the channels just fine, but this week it suddenly starting failing with this error:
{
"error": {
"code": "AccessDenied",
"message": "Failed to execute Skype backend request GetThreadsS2SRequest.",
"innerError": {
"request-id": "226d8e17-fa0f-4c42-8139-4776e198a3b2",
"date": "2019-08-26T19:25:10"
}
}
}
We see that the problem is happening for different teams and across different tenants. This is critical!
Thanks for reporting this issue. There was an issue going on with List Channel Graph API which has been fixed now.
I have an issue when I try to update (PATCH) a shared contact with Microsoft-Graph.
I'm getting this message:
{
"error": {
"code": "ErrorInternalServerError",
"message": "An internal server error occurred. The operation failed., This session itself is a delegated session.",
"innerError": {
"request-id": "d12ca994-a3f6-4f3a-956e-ed4dc43bf72b",
"date": "2018-08-23T22:21:05"
}
}
}
What's going on?
Update: I attach an image from Graph Explorer
Evidence
After talking with the engineering team, this scenario is not supported right now. We are going to update the documentation to explain this for future reference.