UnknownError from Graph API when accessing Sharepoint documents RRS feed

  • Question

  • I have a multitenant app where multiple tenants at random gets a non-helpfull error "UnknownError", when accessing the sharepoint documents through Graph API, for several hours. This happens when listing files in a folder, uploading files, either directly or chunked, or getting file content. It looks like some sort of timeout issue. It always happens after 10 (and sometimes 20) seconds. However it's not the OverallTimeout on the C# SDK HttpProvider as it's set for 100 seconds (and that results in a timeout error instead). Sometimes when uploading a file, and an error is reported, then the file appears in sharepoint a bit later, which means it continues in the background.
    Sometimes when sharepoint is in this state, it also results in errors in the sharepoint portal: "StoreBusyRetryLater"

    Right now I have a customer (tenant id af43b8c0-b71d-43b8-8444-c8163f3780d2) that have had this error for more than 30 hours, making the app useless. Could someone please have a look at this.

    NB: I've created a SO issues a while ago, without any solution:

    UPDATE 08/05-2019:

    I looks like all UnknownError errors across all our customers are originating from DataCenter: WestEurope, Slice: SliceC (according to headers). Different Rings and Instanses though (even for same customer)

    Most of the time it's this request that is failing:



    Bo Kingo Damgaard

    Thursday, May 9, 2019 8:13 AM

All replies

  • did you try to create support ticket in MS about this problem?

    Blog -
    Dynamic CAML queries via C# -

    Thursday, May 9, 2019 3:10 PM
  • Yes, but as a developer using MS Graph, there is not support. No one has been able to point me to the proper place to get support for MS Graph - even Microsoft staff. I'm always forwarded to forums and SO, where response is either slow or absent.

    However I'm in luck this time, as the Sharepoint portal is affected by this issue, by being extremely slow, hence my ticket in wasn't rejected. Hopefully something good will come of this. I do however think that the Graph API should change it's way to handle slow upstream services

    Monday, May 13, 2019 8:26 AM