Hoping to get some support from Microsoft on this one: we recently launched an integration with OneDrive using the Microsoft Graph API at my company and have been somewhat frequently been getting this error upon authorization with the business/SharePoint versions of OneDrive:
error: 'temporarily_unavailable'
error_description: 'AADSTS70012: Non-retryable error has occurred.
Trace ID: a7585d82-3b6d-4552-af1f-0ce32ffc2300
Correlation ID: 4913d1c5-580d-46ce-bbbc-a28e95d7ae37
Timestamp: 2017-09-05 19:03:38Z'
This error appears to be on Microsoft's end (though perhaps it is not), was hoping to get some insight as to why this is happening to our users so frequently upon authorization and how it can be avoided. Thank you.
Related
We encountered a large amount of "Connection aborted. BrokenPipeError" responses from a specific tenant. We are using the (email) message edit and move APIs. These errors seem to be happening more frequently in certain hours. The error itself does not contain any additional information and we weren't able to find in depth documentation. Any recommendations on how to investigate and resolve these issues?
I'm trying to integrate with Priority REST API and using
https://prioritysoftware.github.io/restapi/#Service_Root_URL for this.
But when I'm trying to call some API's (for example https://www.eshbelsaas.com/ui/odata/Priority/tabmob.ini,3/usdemo/ACCOUNTS) I'm getting the error - API cannot be run for this form.
May someone explains to me what does exactly this means? Is there some permission problems?
This message says that the system administrator hasn't exposed this form in Odata.
accoding to https://prioritysoftware.github.io/tryit (which is not working currently), only few forms were enabled: ORDERS, CUSTOMERS and AGENTS
When trying to do a DELETE operation using this request https://graph.microsoft.com/v1.0/drives/{drive-id}/items/{item-id}/permissions/{perm-id}, the Microsoft Graph has started returning an HTTP 403 with this body:
{
code: "notAllowed"
innerError: {request-id: "6f8821bc-bb2a-46ba-89c8-99238765e27f", date: "2019-04-19T09:48:04"}
message: "Operation not allowed"
}
This is extremely critical since we no longer have a way to remove permissions that we have added to a folder in a SharePoint site. We see that this problem is now affecting more and more tenants. Microsoft support has not been very helpful so far so I don't know where to take this. I think the problem is caused as a side-effect of work on the permission model in SharePoint/Microsoft Teams.
The strange thing is that it works when adding the new preview permissions scope Sites.FullControl.All while Files.ReadWrite.All or Group.ReadWrite.All does not work
this was definitely a bug and we've tracked down the cause and disabled the problematic code. In the future I'd recommend creating issues over at https://github.com/OneDrive/onedrive-api-docs/issues for regressions in the OneDrive and SharePoint APIs as there are lot more eyes on it and there'll definitely be better traction.
I'm attempting to use OpsCenter 6.1 to install a new cluster. OpsCenter successfully ssh's to each of the nodes in the cluster then appears to nearly immediately error out on each node with the following message:
400 Client Error: Bad Request for url: http://<opscenter>:8888/api/v1/lcm/internal/nodes/<node-id>/package_information
When attempting to reach that page myself I receive a 404 error with this message:
{"brief": "error", "message": "{\"type\":\"ApiException\",\"code\":404,\"msg\":\"Can't find object for given parameters: {:job-id nil, :node-id \\\"<node-id>\\\"}\"}", "type": "NoSuchResource"}
Note that <opscenter> (above) is the IP address of my local install, and <node-id> is the ID of the node.
Considering that I don't receive the 400 error myself I'm assuming that I'm unable to replicate the scenario that occurs during the install because of some perviously executed steps that are rolled back.
Any insight into what might be causing this issue?
Thanks in advance!
LCM developer here... It's hard to know exactly what's wrong based on the information provided. But here are some tips:
If there's an api error during a job, the error will be recorded in opscenterd.log (usually in /var/log/opscenter in package installs, or in something like ./log/ in tarball installs).
The internal api is private and is not publicly documented. It's authenticated via a per-node secret token that's only valid during the lifetime of a job, so it's fairly challenging to try to ping internal urls manually, we've never needed to have someone try to ping internal api's to successfully diagnose issues in the past. It's not something I'd recommend spending a lot of time on.
You might get more context about LCM is doing when the error happens by turning the "lcm" logger up to debug in opscenter's logback.xml and restarting opscenterd.
I get this message when I query the API for messages on some mailboxes in my organization. It sounds like it's a temporary situation that will be fixed over time, unlike other messages like 400/not found or invalid licenses. Couldn't find any information to confirm/deny this speculation. Is it a temporary situation?
This is a bug in code. For users that don't have mailboxes in O365 cloud, sometimes instead of returning 404, the service ends up returning 503 or 500 with this error. You can safely ignore this error and treat this as a 404 mailbox not found.