How to Fix SharePoint Error Correlation ID Errors

A Correlation ID in SharePoint is a globally unique identifier (GUID) automatically assigned to every web request received by the server. When an error occurs, SharePoint displays the Correlation ID along with a timestamp. This ID is not an error code itself; instead, it is a lookup key that allows administrators to find the exact database, code, or service failure in the server logs.

This guide explains how to capture Correlation IDs, trace them through ULS logs, and resolve underlying server issues.

Understand SharePoint Correlation IDs

When SharePoint displays a correlation error, it typically points to:

1. Database Timeouts or Connection Failures: SQL Server is unresponsive or the query took too long.
2. Custom Web Part Exceptions: Broken third-party scripts, custom sandboxed solutions, or outdated web parts.
3. Permission Blocks: A security policy blocked a service account from executing a background query.
4. Timer Service Failures: Background jobs failing to process.

How to Locate the Root Cause using the Correlation ID

To fix the error, you must use the Correlation ID to find the underlying error log entry.

Step 1: Capture the Metadata

Write down or copy the exact details shown on the error screen. You will need:

• Correlation ID: e.g., 8afb3a9e-c011-80fc-1234-5678abcdef01
• Date and Time: The precise timestamp (in UTC or local server time).

Step 2: Query ULS Logs on SharePoint On-Premises

If you host your own SharePoint Server farm (SharePoint 2013, 2016, or 2019/SE), search the Unified Logging Service (ULS) logs.

# Merge logs from all servers for a specific Correlation ID
Merge-SPLogFile -Path "C:\Logs\CorrelationSearch.log" -Correlation "8afb3a9e-c011-80fc-1234-5678abcdef01"

# Alternatively, view the error details directly in the console
Get-SPLogEvent -StartTime (Get-Date).AddMinutes(-30) | Where-Object {$_.Correlation -eq "8afb3a9e-c011-80fc-1234-5678abcdef01"} | Format-List Area, Category, EventID, Message

Using ULS Viewer:

1. Download and run the Microsoft ULS Viewer tool on the server.
2. Open the active log file located by default at: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\LOGS
3. Press Ctrl + F, choose Correlation, paste the GUID, and click Find Next.
4. Read the Critical or Unexpected messages associated with that GUID.

Step 3: Investigate Correlation IDs in SharePoint Online

For SharePoint Online (Microsoft 365), you do not have direct access to ULS logs. Follow these steps:

1. Open the Microsoft 365 Admin Center (admin.microsoft.com).
2. Search the Service Health Dashboard to check if there is an active outage matching the timestamp.
3. If no outage is active, navigate to the M365 Purview Compliance Portal > Audit.
4. Search for SharePoint file or site activities matching the user and timestamp to identify permission conflicts.
5. If the issue persists, open a Microsoft Support Ticket and provide the Correlation ID, the URL, and the Timestamp.

Step 4: Restarting SharePoint IIS and Timer Services (On-Premises Only)

If the logs show that the SharePoint Timer Service is hung or that IIS application pools are failing to respond, run these commands to reset the environment.

On the SharePoint Server:

1. Open Command Prompt as Administrator.
2. Execute the following commands to recycle IIS and restart the Timer Service:

:: Reset IIS Web Server
iisreset /noforce

:: Restart the SharePoint Timer Service
net stop SPTimerV4
net start SPTimerV4

:: Restart the SharePoint Administration Service
net stop SPAdminV4
net start SPAdminV4

Summary Checklist

• Copy the Correlation ID and the exact timestamp from the error page.
• For on-premises farms, run Merge-SPLogFile in PowerShell to extract the logs.
• Open the merged log file and look for “Unexpected” or “Critical” error levels.
• For SharePoint Online, verify the tenant’s Service Health status.
• If service restarts are needed on-premises, recycle IIS and restart the SPTimerV4 service.