uls logs fiddler traces verbose logging collect

collect and analyze uls logs fiddler traces verbose logging enabled is one of the most common sharepoint administrator task. If there is an issue in accessing site, webpart in sharepoint page, data source connection, application, we can follow this . We collect uls logs, capture fiddler traces by enabling verbose logging. In this post I will share the step by step process to enable verbose using powershell, debug or capture fillder trace or https traffic.

Advertisements

we need to follow these steps as below:

  • Run fiddler
  • Enable verbose logging in sharepoint server
  • Create new log file in sharepoint server.
  • Access the site having issue
  • Create log files new.
  • Disable verbose logging.
  • save fiddler trace all session
Advertisements

collect uls logs fiddler traces verbose step by step

  • Close all browsers.
  • Run fiddler to collect fiddler trace or capture https traffic.
  • Run sharepoint management shell as an administrator.
  • Enable verbose logging applying powershell command below.
Set-SPLogLevel -TraceSeverity VerboseEx
Advertisements
  • collect uls logs, new log file running below command in all sharepoint servers
New-SPLogFile
Advertisements
  • Remove all sessions from fiddler.
  • Access sharepoint site now.
  • Run below command in sharepoint management shell in all sharepoint servers.
New-SPLogFile
Advertisements
  • Disable verbose now by running command below.
Clear-SPLogLevel
uls logs fiddler traces verbose logging
Advertisements
  • Save the fiddler trace results.
File -> Save -> All Session

You can follow the post “Log management using powershell” to get more details about management of uls logs in sharepoint 2019.

Advertisements

Follow the video to get steps in detail for better understanding.

Advertisements

merge splogfile correlation id start time end time

In this post we will discuss how to merge splogfile correlation id start time end time. If you need to find all log files insharepoint between certain time duration with in which you think issue happened you can use these powershell commands. If you enabled verbose logging for certain durataion in sharepoint server, then if is very useful. Analyzing or managing sharepoint logs out of too much log files and servers is very difficult. Sometimes its quite impossible to go each server and check the log file. Using powershell, we can gather all logs in sharepoint servers at a single place in a single file. This will be easy to analyze by using sharepoint log viewer. Therefore we will use powershell to merge sharepoint log file of multiple sharepoint servers at once place.

Advertisements

merge splogfile by correlation id

Follow the powershell commands below to merge or gather or find all logs files from all sharepoint servers at a single place.

Merge-SPLogFile -Path "location to save file" -overwrite -Message "*<scope>*" -Correlation "<correlation id>"
Merge-SPLogFile -Path "C:\MergeLogFileByCorrelationID.log" -overwrite -Message "*monitored*" -Correlation "8a16579f-1d6f-208b-cc49-1604fc0dbc86" #scope included
Merge-SPLogFile -Path "C:\MergeLogFileByCorrelationidNoScope.log" -Correlation "8a16579f-1d6f-208b-cc49-1604fc0dbc86" #No Scope included
Advertisements

merge splogfile by start time end time

Follow the powershell commands below to merge or gather or find all logs files from all sharepoint servers by timestamp means to find log files created between a praticular duration of time.

Merge-SPLogFile -Path "C:\MergelogDateTime.log" -overwrite -StartTime "5/29/2020 12:20:57 PM" -EndTime "5/29/2020 12:40:57 PM"
Advertisements

Follow the video to get more detail step by step in visual view for better understanding.

merge splogfile by correlation id | start time end time in sharepoint logs using powershell
Advertisements

Enable administrative actions log in sharepoint 2019

You can Enable administrative actions log when you face any issue in sharepoint 2019 servers happens due to administative changes. Administrative actions log captures events related to below action categories.

  • Configure Accounts
  • Configure managed accounts
  • Configure Service Account
  • Configure Password change settings
  • Specify Authentication Providers
  • Manage Trust
  • Manage Web Part Security
  • Farm backup and restore operations
  • Server Administration
  • Configuration database changes
  • Site Collection Administration
  • Site Collection Content Database
  • Quota Changes
  • Feature Administration
  • Web Application Administration
  • Web Application Administration User Policy
  • Service Application
  • Form & Feature Template Administration
  • Content Database
  • Configure Groups
  • User & Group Migration
Advertisements

administrative actions log is avilable in sharepoint server 2016 feature pack 1 onwards. You need to enable administrative actions log using central admin. Follow the step by step procedure below to enable.

Advertisements

Navigate to central administration

Central admin in sharepoint server 2019
Central admin in sharepoint server 2019
Advertisements

Click on “Monitoring” form left navigation

configure usage and health data collection in sharepoint 2019
Advertisements

Click on “Configure usage and health data collection” present under “Reporting”.

enable administrative actions log event
Advertisements

You will find an option “Administrative Actions” events to log check box under event selection. Select the check box and click “OK” to make enable administrative actions event log.

Advertisements

Enable administrative actions log in sharepoint 2019 | usage and health data collection | #usagelog

Advertisements