Collect SharePoint Error Details Before Escalation: Practical Checklist for SharePoint Owners

When a SharePoint error occurs, your first reaction might be to contact Microsoft Support immediately. Without the right information, support engineers cannot diagnose the issue quickly, and you will face repeated requests for logs and screenshots. This article explains exactly what data you need to collect before opening a support ticket. Following this checklist helps you resolve the problem faster and reduces the back-and-forth with the support team.

Why Collecting Error Details Matters Before Escalation

Microsoft Support uses specific data points to identify the root cause of SharePoint errors. Without these details, the support engineer must ask for the same information repeatedly, which delays resolution. The most common missing pieces are the correlation ID, the exact error message, and the steps that triggered the error. Collecting this data yourself ensures the support team can start working on your case immediately.

SharePoint Online and SharePoint Server generate different types of logs. For SharePoint Online, you rely on browser tools and the SharePoint admin center. For SharePoint Server on-premises, you access ULS logs and Event Viewer. This guide covers both environments.

What Is a Correlation ID

A correlation ID is a unique identifier that SharePoint assigns to every request. When an error occurs, the correlation ID appears in the error page or in the browser console. This ID allows support engineers to trace the request through SharePoint servers and locate the exact log entry that caused the failure. Without the correlation ID, finding the relevant log entry is nearly impossible.

Checklist: Data to Collect Before Opening a Support Ticket

Step 1: Capture the Exact Error Message and Screenshot

1. Copy the error text
   Select the full error message displayed on the screen. If the error is in a dialog box, press Ctrl+C to copy the text. Paste it into a text file.
2. Take a screenshot
   Press Windows+Shift+S to open the Snipping Tool. Capture the entire browser window, including the address bar and any error details. Save the image as PNG.
3. Record the URL
   Copy the full URL from the browser address bar. Include any query string parameters. This URL tells support which site and page caused the error.

Step 2: Locate the Correlation ID

1. Check the error page
   Many SharePoint error pages display the correlation ID at the bottom. Look for a line that says “Correlation ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.” Copy this GUID.
2. Use browser Developer Tools
   Open Developer Tools by pressing F12. Go to the Network tab. Refresh the page and reproduce the error. Find the failed request (status 4xx or 5xx). Click the request and look for the x-ms-correlation-id header in the Response Headers section.
3. Copy the correlation ID
   Right-click the header value and select Copy value. Paste it into your text file alongside the error message.

Step 3: Collect HTTP Request and Response Details

1. Open Network tab
   Press F12 and click the Network tab. Ensure the recording is enabled (red circle icon).
2. Reproduce the error
   Perform the exact action that caused the error. The Network tab will list all requests.
3. Export the HAR file
   Right-click any request and select Save all as HAR with content. Save the .har file to your desktop. This file contains all request and response headers, cookies, and timestamps.

Step 4: Gather Site and Tenant Information

1. Open SharePoint admin center
   Go to https://admin.microsoft.com and navigate to SharePoint admin center. Select Active sites.
2. Find the affected site
   Search for the site URL you recorded. Click the site name to open the details panel.
3. Copy site details
   Note the Site ID, Template, Storage used, and Storage quota. Also check the Sharing settings and any applied policies.
4. Check tenant health
   In the SharePoint admin center, go to Health > Service health. Verify that no active incident affects SharePoint.

Step 5: Collect ULS Logs (SharePoint Server Only)

1. Open ULS Viewer
   On the SharePoint server, run UlsViewer.exe from the SharePoint root directory (usually C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\BIN).
2. Set a filter
   In ULS Viewer, go to Edit > Filter. Enter the correlation ID you collected. This filters logs to show only entries related to the error.
3. Export logs
   Select all filtered entries. Press Ctrl+C to copy them. Paste into a text file and save it as ULS_Logs.txt.

Step 6: Check Event Viewer (SharePoint Server Only)

1. Open Event Viewer
   Press Windows+R, type eventvwr.msc, and press Enter.
2. Navigate to Application log
   Expand Windows Logs and select Application. Look for events with Source containing “SharePoint” or “Windows SharePoint Services.”
3. Filter by time
   In the Actions pane, click Filter Current Log. Set the time range to match when the error occurred. Copy any events with Level Error or Warning.

Step 7: Reproduce the Error Step by Step

1. Write down the exact steps
   List every click and keystroke from the moment you opened the browser until the error appeared. Include the browser type and version.
2. Test with another browser
   Try reproducing the error in a different browser. Record whether the error persists. This helps identify browser-specific issues.
3. Test with a different user
   Ask a colleague with the same permissions to reproduce the error. Note whether the error occurs for them too.

If SharePoint Still Has Issues After Collecting Data

Error Message Does Not Include a Correlation ID

Some SharePoint errors, especially those from custom code or third-party add-ins, may not display a correlation ID. In this case, open the browser Developer Tools, go to the Console tab, and look for JavaScript errors. Copy the full stack trace. Also check the Network tab for failed requests and note the request URL.

HAR File Export Fails

If the Network tab does not allow saving a HAR file, take a screenshot of the Network tab showing the failed request. Expand the request headers and response headers so the support team can see the status code and correlation ID. Alternatively, use Fiddler or another HTTP debugging proxy to capture the traffic.

ULS Logs Are Empty for the Correlation ID

If filtering ULS logs by correlation ID returns no results, the error may have occurred on a different server in the farm. Repeat the error multiple times and check ULS logs on each SharePoint server. Also verify that the ULS log level is set to Verbose for the affected category. You can adjust log levels in Central Administration > Monitoring > Configure diagnostic logging.

Item	SharePoint Online	SharePoint Server
Correlation ID location	Error page or Network tab headers	Error page, ULS logs, or Event Viewer
Log file format	HAR file from browser	ULS logs (.txt) and Event Viewer (.evtx)
Site information source	SharePoint admin center	Central Administration or PowerShell
User account required	Global admin or SharePoint admin	Farm admin or server local admin
Typical error types	403, 404, 500, throttling	Database connection, timer job, configuration

After you collect all the items in this checklist, open a support ticket at the Microsoft 365 admin center. Attach the text file with the error message and correlation ID, the screenshot, the HAR file, and the site details. Include the step-by-step reproduction notes in the ticket description. This complete package lets the support engineer start troubleshooting immediately without requesting additional information.

For frequent errors, consider setting up SharePoint alerts to notify you when specific error events occur. You can also use PowerShell scripts to automate the collection of ULS logs and site details. The less time you spend gathering data manually, the faster you can resolve issues and restore productivity for your users.