SharePoint Pain

Symptoms When one tries to open an Office Online document, SharePoint gives the “ Sorry, something went wrong ” error message with a Correlation ID. All Office Online Server members in the farm work fine via https://<officeonlineUrl>/op/generate.aspx. However, the associated Correlation ID on the SharePoint ULS shows " System.TimoutException: The open operation did not complete within the allotted timeout of 00:01:00 ", and it stems from SPApplicationSecurityTokenServiceClient : Cause Malfuction of SecurityTokenServiceApplicationPool  Resolution Recycle the SecurityTokenServiceApplicationPool on the identified server in ULS (highlighte):

Applies to SharePoint 2016; not tested on other versions of SharePoint.   Symptoms   Central Admin's Health Analyzer shows:   -         Title: One or more services have started or stropped unexpectedly. -         Explanation: The following services are managed by SharePoint, but their running state does not match what SharePoint expects: c2wts -         Remedy: To stop or start a service managed by SharePoint, use the SharePoint service management interface in the SharePoint Central Administration Site. If a service has crashed, restart the service manually on the affected servers by running “net start [service name]” from a command prompt.   Service status shows c2wts (Claims to Windows Token Service) is not running even though it’s set to “Startup type: Automatic”. When you try to start the service, it gives:   Windows could not start the c2wts service...