Contents
There are some good tools out there. SharePoint 2013 correlation ID location: Usually, ULS logs are located at 14/15 hive’s LOGs folder. E.g: “C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\15\LOGS”.
By default, ULS logs are located in the SharePoint hive. For example, the default location for SharePoint 2016 ULS logs is %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\16\Logs.
What is JMS correlation ID?
A correlation ID is used to correlate response messages with request messages when an application invokes a request-response operation. With WebSphere® MQ and WebSphere MQ JMS, you can correlate using either a correlation ID or a message ID.
Why do I get a correlation ID error?
When a user try to create a new form or edit/view exiting one they get the following error with a correlation ID: There has been an error while loading the form. Click Try again to attempt to load the form again. If this error persists, contact the support team for the Web site.
If the problem persists, please contact your administrator”. It also provides a correlation ID (very helpful). This is where having that correlation id is so handy. When searching for errors in the ULS logs it is extremely hard to find what you need, unless you know what you are looking for.
After migrating from SharePoint 2010 to SharePoint 2016 using the detach attach method using SharePoint 2013 in between, we have noticed that libraries using InfoPath forms not working anymore. When a user try to create a new form or edit/view exiting one they get the following error with a correlation ID:
When does claims authentication does not validate user in SharePoint?
If the error message indicates that the user does not have access to the site, then the authentication was successful and the authorization failed. To troubleshoot authorization, try the following solutions: