Internal Server Error on FIleHandler

Question

When opening any document library we experience an 500 Internal Server error on a call to GetByType('FileHandler'). We assumed this was due to our development of a custom type handler.

However, this problem is reproducible on all SharePoint online instances  we have access to, not just our development instance. We have asked on external person to verify this as well and he was able to reproduce as well.

The _api/apps/GetByType('FileHandler') call results in the following error message:

{"odata.error":{"code":"-1, Microsoft.Azure.ActiveDirectory.GraphClient.AuthorizationException","message":{"lang":"en-US","value":"Insufficient privileges to complete the operation."}}}

Can you please investigate?

Please let us know if we can provide you with additional information to diagnose this issue.

Screenshot: 

[Personal information is masked by Jiaxing Bian MSFT]

Answer 1

Hi All,

We have received updates from our escalation team that the issue has been resolved and the ticket has been closed. Therefore, we’d like to share a summary here.

============

Description:

When accessing SharePoint document libraries in Chrome, you can see the “GET https://contoso.sharepoint.com/\_api/apps/GetByType('FileHandler') 500 (Internal Server Error)” from the Chrome Development Tool.

Solution:

Our engineering team has provided a fix to resolve this issue.

============

If you have any other questions feel free to post us a new thread, we will continue to assist you from there.

Regards,

Spike

Answer 2

Hi All,

We have engaged our related team to investigate this issue.

@Siimav Your Office 365 global admin will be contacted via email for further troubleshooting.We will share the solution to the community once you have confirmed that the issue has been resolved. Community member will be benefited from the outcome of this issue.

Regards,

Spike

Answer 3

Hi Tom,

Thanks for your reply.

Currently there is no ETA available. We will verify with related team and update in the thread once we receive any further information from them.

Thanks for your patience.

Spike

Answer 4

Thanks Spike! We are looking forward to your reply. Do you have any ETA?

Answer 5

Hi All,

@Tom & Siimav, thanks for your information.

As Tom mentioned, the issue is related to the suiteextensions.js file. We will be engaging the related team and continue to provide any updates here. Your patience is highly appreciated.

@ Balu, for further investigation, please provide your global admin’s contact information to us in private message. You can access it via the link below:

https://answers.microsoft.com/en-us/privatemessages/list

Regards,

Spike