I used to download usercredentialusagedetails through PS and it used to work fine until few weeks ago and now it fails.
Request : GET https://graph.microsoft.com/beta/reports/userCredentialUsageDetails
More Details : https://learn.microsoft.com/en-us/graph/api/reportroot-list-usercredentialusagedetails?view=graph-rest-beta&tabs=http
Error : Invoke-RestMethod : {"#odata.context":"https://graph.microsoft.com/beta/$metadata#reports/userCredentialUsageDetails","v alue":[{"id":"79876725968494393786570221953037561096003605792378637660218099476724503735617","feature":"registration"{ "error": { "code": "InternalServerError", "message": "The property 'userPrincipalName[Nullable=False]' of type 'Edm.String' has a null value, which is not allowed.", "innerError": { "date": "2020-09-30T11:58:11", "request-id": "60bdc1d7-054f-402b-8054-e0c8db709e43", "client-request-id": "60bdc1d7-054f-402b-8054-e0c8db709e43" } } }
i have number of other queries/requests in same script and they all work fine.
Can someone pls try in their tenancy? is anyone else facing this issue?
Looks like the issue is resolved. I have got the confirmation on this Github Link. Looks like it could be an issue on the server end and its resolved now.
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.
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.
Trying to get the details of a SharePoint site using a relative url.
GET /v1.0/sites/mytenant.sharepoint.com:/sites/mvep
However if the relative path is pointing to a site that does not exist I get a 500 Internal Server Error returned with the following json:
"error": {
"code": "-1, Microsoft.SharePoint.Client.UnknownError",
"message": "Unknown Error",
"innerError": {
"request-id": "bc65a8a8-e857-4ece-9e1d-f42b5671f151",
"date": "2018-12-05T11:44:13"
}}
I tried same test against a demo tenant and the correct 404 / itemNotFound is returned.
There was a few posts here talking of a regression introduced back in Dec 2017 that was apparently fixed.
Could this patch have been missed on our SPO servers?
Or is it a new regression?
Thanks in advance.
Tested again this morning and it now works as expected.
I called the endpoint /shares/{shareId} using msgraph-sdk-php, but got response 400 as:
{
"#odata.context":"https://graph.microsoft.com/v1.0/$metadata#shares/$entity",
"id":"s!here-is-the-share-id",
"name#odata.type":"#String",
"name":{
"error": {
"code": "BadRequest",
"message": "A primitive value was specified; however, a value of the non-primitive type '' was expected.",
"innerError": {
"request-id": "3ea56b1c-acd6-4fdf-a856-c46b35e01cb7",
"date": "2017-05-25T05:26:23"
}
}
}
(Yes, I even got 4 left brackets but only 3 right brackets.)
while I can get correct response via api.onedrive.com api with the same shareId.
I really can't find any tips from documentation.
Thanks for letting us know about this #SevenOutman! This was a configuration issue that has now been resolved.