Forum Discussion
Internal Server 500 Error Sharing Document Library
- Dec 05, 2016
Our organization ended up opening a support ticket with Microsoft to help with this problem. We didn't necessarily correct the issue, but we tracked it back to a custom site column that had a calculated default value associated with it. The column was setting a default value for the current Fiscal Year based on the current date. For some reason if the user did not have at a minimum site-level access the page would return the Internal 500 Server error.
To work around this we simply removed the default calculated value for this particular document library that needs to be shared out to the "Everyone" group.
Internal Server Errors is something Microsoft will need to investigate. You shouldn't get them even if you're doing something "wrong" :) Open up a support case within the O365 Admin Portal.
- Riley HaleDec 05, 2016Brass Contributor
Our organization ended up opening a support ticket with Microsoft to help with this problem. We didn't necessarily correct the issue, but we tracked it back to a custom site column that had a calculated default value associated with it. The column was setting a default value for the current Fiscal Year based on the current date. For some reason if the user did not have at a minimum site-level access the page would return the Internal 500 Server error.
To work around this we simply removed the default calculated value for this particular document library that needs to be shared out to the "Everyone" group.
- Wessel Du PlooyJun 22, 2017Copper Contributor
Ensuring the time zone in Office 365 (Check file attachment time in SharePoint, if you have no access to Office365 setup) is the same as the time zone used on the VM that runs your AOS should solve the problem. It worked for me.