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

full crawl takes too long to complete sharepoint search

I faced an issue with sharepoint search where full crawl takes too long to complete nearly 240 hours. Requirement was how to reduce the full crawl time.

  • Search service is working fine.
  • search components are online and heathy.
  • There is enough space in the server drive hosting search components.
  • Checked event log in the server hosting crawl component and found the below error
Event ID: 30
Description: The search service stopped the filter daemon because it was consuming too many resources. A new daemon will automatically be started, and no user action is required.
Advertisements

Also from crawl logs found most traces related to memory quota choking like as below

The filter process could not be initialized when trying to process this item. Verify that the file extension is a known type and the item is not corrupt.
Advertisements

Resolution

so as to resolve the issue, we need to made some changes in registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Global\Gathering Manager
Advertisements

Change the properties of below two items to 200 MB from the default value of 100 MB.

  • FilterProcessMemoryQuota
  • DedicatedFilterProcessMemoryQuota
Advertisements

follow the video below to get detail step by step information of the changes to do.

Advertisements

Partial Index Reset of a single content source

Partial Index Reset of a single content source

This script will remove and re-add your content source‘s start addresses.

SharePoint will more or less rebuild the index for these sources, when the next full crawl is started.

$sourceName = "Local SharePoint sites"
$SSA = Get-SPEnterpriseSearchServiceApplication
$source = Get-SPEnterpriseSearchCrawlContentSource -Identity $sourceName -SearchApplication $SSA
$startaddresses = $source.StartAddresses | ForEach-Object { $_.OriginalString }
$source.StartAddresses.Clear()
ForEach ($address in $startaddresses ){ $source.StartAddresses.Add($address) }

Similar Post