When your SharePoint site throws an error, it just says "Sorry something went wrong - An unexpected error has occurred" and expects the developer to put more effort into finding the exact issue. That is quite frustrating at times !!
The SharePoint Logs are stored on your Server(s) at location HIVE\LOGS, HIVE is the path containing libraries and files for the installed SharePoint version. Usually, HIVE is --> C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions
As a developer, you need to scan through all your logs, find the relevant log (based on the date-time stamp), and scan and identify all servers to find more information on the error (use the 'Date and Time' value). Then open the file and search for 'Correlation ID', this will give you more specific details about the error.
This can take up some time to locate the exact error and issue.
Is there an easier way? -Yes.
⚡️ PowerShell Merge-SPlogfile
Use PowerShell command 'Merge-SPLogFile' to filter logs from all SharePoint servers in the FARM based on the Correlation ID http://code2care.org/2015/merge-splogfile-sharepoint-correlation-id-error⚡️ SharePoint ULS Log Viewer
This is a free Codeplex tool for viewing ULS logs http://ulsviewer.codeplex.comPS - This approach does not work for SharePoint Online and will only work for on-premises installations. For SPO, reach out to Microsoft Support to get more details on the error.
This is not an AI-generated article but is demonstrated by a human.
Please support independent contributors like Code2care by donating a coffee.
Buy me a coffee!
Comments & Discussion
Facing issues? Have questions? Post them here! We're happy to help!