/
Analyzing the SharePoint Logs

Analyzing the SharePoint Logs

The SharePoint infrastructure includes a comprehensive logging system, often referred to as the Unified Logging System ("ULS"), which the Legacy SharePoint Connector for Confluence uses to report errors and exception conditions.

In the event of errors or other unexpected behavior, examining the SharePoint logs can often provide clues as to the source of the problem.

 

Locating the Log Files

The log files from the Unified Logging Service are located in the SharePoint "Hive" directory, which varies depending on the version of SharePoint you have installed. Consult the table below to identify the location of your log files.

SharePoint Version

Log File Location

SharePoint Version

Log File Location

SharePoint 2007

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS

SharePoint 2010

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS

SharePoint 2013

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

SharePoint 2016

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\LOGS

The Unified Logging Service uses a 'rolling' log file system, so the LOGS folder is likely to contain multiple log files, each representing the log messages generated during a specific period. It may be helpful to sort the files by Last Modified Date so that the most recent log file appears at the top of the folder.

UNKNOWN ATTACHMENT

 

Alternative location of Log Files

If the ULS log files aren't stored in the above-mentioned folder, you can check in the Central Administration where the files are located:

  1. Open the Central Administration

  2. Click on Monitoring

  3. Click on Configure diagnostic logging

  4. Scroll down to the Path

    1. There is an Input field where the path of the ULS log files is set.

Analyzing the Log Files

Locating pertinent information in SharePoint log files can be challenging due to the sheer volume of content. When searching for information from the Legacy SharePoint Connector in the log, you should search for lines that contain the text "Atlassian Confluence", which will prefix every line generated by the Legacy SharePoint Connector.

The example below shows a log message generated by the Legacy SharePoint Connector:

01/01/2001 12:00:23.23 w3wp (0x18F8) 0x0390 Atlassian Confluence Web Part Error CSIz Exception System.Web.Services.Protocols.SoapException: com.atlassian.confluence.rpc.RemoteException: The user 'test' does not exist.

Related Articles