Configure diagnostic logging SharePoint 2016

The SharePoint Server 2016 environment might require configuration of the diagnostic logging settings after initial deployment, after upgrade, and if a change is made to the environment, such as adding or removing a server.

The guidelines in the following list can help you form best practices for the specific environment.

* Change the drive to which the server writes logs:

By default, SharePoint Server 2016 writes diagnostic logs to the same drive and partition on which it was installed. Because diagnostic logging can use a large amount of drive space and compromise drive performance, you should configure SharePoint Server 2016 to write to another drive on which SharePoint Server 2016 is not installed.

You should also consider the connection speed to the drive on which SharePoint Server 2016 writes the logs. If verbose-level logging is configured, the server records a large amount of data. Therefore, a slow connection might result in poor log performance.

* Restrict log disk space usage:

By default, the amount of disk space that diagnostic logging can use is unlimited. Therefore, restrict the disk space that logging uses, especially if you configure logging to write verbose-level events. When the disk reaches the restriction, SharePoint Server 2016 removes the oldest logs before it records new logging data.

* Use the Verbose setting sparingly:

You can configure diagnostic logging to record verbose-level events. This means that SharePoint Server 2016 records every action that it takes. Verbose-level logging can quickly use drive space and affect drive and server performance. You can use verbose-level logging to record more detail when you are making critical changes and then reconfigure logging to record only higher-level events after you make the change.

* Regularly back up logs:

Diagnostic logs contain important data. Therefore, back up the logs regularly to ensure that this data is preserved. When you restrict log drive space usage, or if you keep logs for only a few days, SharePoint Server 2016 automatically deletes log files, starting with the oldest files first, when the threshold is met.

* Enable event log flooding protection:

When you enable this setting, SharePoint Server 2016 detects repeating events in the Windows event log, and suppresses them until conditions return to a typical state.

You can set the level of diagnostic logging for the event log and for the trace log. This limits the types and amount of information that are written to each log.

The following tables define the levels of logging that are available for the event log and trace log.

event-log-levels

trace-log-levels

Configure diagnostic logging by using Central Administration :

  1. In Central Administration, on the home page, click Monitoring.
  2. On the Monitoring page, in the Reporting section, click Configure diagnostic logging.
  3. On the Diagnostic Logging page, in the Event Throttling section, configure event throttling as follows:To configure event throttling for all categories:
    1. Select the All Categories check box.
    2. Select the event log level from the Least critical event to report to the event log list.
    3. Select the trace log level from the Least critical event to report to the trace log list.

    To configure event throttling for one or more categories:

    1. Select the check boxes of the categories that you want.
    2. Select the event log level from the Least critical event to report to the event log list.
    3. Select the trace log level from the Least critical event to report to the trace log list.

    To configure event throttling for one or more subcategories (you can expand one or more categories and select any subcategory):

    1. Click the plus (+) next to the category to expand the category.
    2. Select the check box of the subcategory.
    3. Select the event log level from the Least critical event to report to the event log list.
    4. Select the trace log level from the Least critical event to report to the trace log list.

    To return event throttling for all categories to default settings:

    1. Select the All Categories check box.
    2. Select Reset to default from the Least critical event to report to the event log list.
    3. Select Reset to default from the Least critical event to report to the trace log list.
  4. In the Event Log Flood Protection section, select the Enable Event Log Flood Protection check box.
  5. In the Trace Log section, in the Path box, type the path of the folder to which you want logs to be written.
  6. In the Number of days to store log files box, type the number of days (1-366) that you want logs to be kept. After this time, logs will automatically be deleted.
  7. To restrict the disk space that logs can use, select the Restrict Trace Log disk space usage check box, and then type the number gigabytes (GB) you want to restrict log files to. When logs reach this value, older logs will automatically be deleted.
  8. After you have made the changes that you want on the Diagnostic Logging page, click OK.

Configure diagnostic logging by using Windows PowerShell :

  1. Verify that you have the following memberships:
  • securityadmin fixed server role on the SQL Server instance.
  • db_owner fixed database role on all databases that are to be updated.
  • Administrators group on the server on which you are running the Windows PowerShell cmdlets.

An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint Server 2016 cmdlets.

  1. On the Start menu, click All Programs.
  2. Click SharePoint 2016.
  3. Click SharePoint 2016 Management Shell.
  4. To change the drive to which the server writes logs, at the Windows PowerShell command prompt, type the following command:

Set-SPDiagnosticConfig -LogLocation D:\DiagnosticLogs

  1. To restrict log disk space usage, at the Windows PowerShell command prompt, type the following command:

Set-SPDiagnosticConfig -LogMaxDiskSpaceUsageEnabled

Or assign the maximum disk space for logs:

Set-SPDiagnosticConfig -LogDiskSpaceUsageGB 500

  1. To view the current logging level, at the Windows PowerShell command prompt, type the following command:

Get-SPLogLevel

  1. To change the logging level, at the Windows PowerShell command prompt, type the following command:

Set-SPLogLevel -TraceSeverity Monitorable

To set all categories back to default levels, at the Windows PowerShell command prompt, type the following command, and then press ENTER:

Clear-SPLogLevel

9. To enable event log flooding protection, at the Windows PowerShell command prompt, type the following command:

Set-SPDiagnosticConfig -EventLogFloodProtectionEnabled

Advertisements

Windows Server Appfabric: Installation error SharePoint 2016

If you are installing SharePoint 2016 Prerequisites manually downloading the files and after that run the “Install Software Prerequisites” from SharePoint 2016 installation file to verify everything installed manually is correct, you may face error like this

“Windows Server Appfabric: Installation error“.

sp2016

This is a generic MSI error message and does not give any indication about how to get the issue fixed. Uninstall or reinstalling only makes it worse.

Resolution :

The reason being the prerequisites installs the file and configure it automatically. If we install manually, then we are trying to bypass the configuration, so that error will be received.

The issue can be caused due to the following:

  •  The path to the PowerShell executable that is needed for the AppFabric installation is incorrect.
  •  In some scenarios, repeated uninstallation and re-installation does not fix the issue. This is because the installer does not remove the PSModulePath entry in Environment

  •  Variables during uninstallation and the installation fails because the entry already exists.
    If you are trying to install all the prerequisites manually as the server does not have a connection to internet.

Note:

Appfabric installation and configuration has to be done by the prerequisite installer ONLY and not in a stand-alone manner.You should follow the manual process of installation  if there is error in automatic process by following Install Prerequisite (prerequisiteinstaller.exe) .

You can implement any one of the two solutions listed below

Solution 1

Append the following path to PSModulePath entry in the environment variables – %SYSTEMROOT%\System32\WindowsPowerShell\v1.0

  • Go to My Computer, right-click Properties
  • On the System page click Advanced System Settings on the left-side pane.
  • If you receive a UAC prompt, click on Yes to launch the System Properties dialog box
  • From the Advanced tab, click Environment Variables
  • Within the System Variables section in the lower half, select PSModulePath and click on Edit (or double-click PSModulePath‘)
  • Append the following path to PSModulePath entry in the environment variables
    %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
  • Ensure that the PSModulePath entry looks like this:
    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules

Solution 2

  • There are chances that other applications might be referencing the same variable and may fail if it is deleted. This is what we can do if solution 1 does not help.
  • Remove the PSModulePath entry from the ‘Environment Variables’ and re-run the installer. Once it completes successfully, ensure that the PSModulePath entry looks the same as mentioned in solution 1.

Reference :

https://msdn.microsoft.com/en-us/library/dd878326(v=vs.85).aspx

Failed to create configuration database exception SharePoint 2016

Error :

There was an error while running Install Prerequisite (prerequisiteinstaller.exe)  “Failed to create configuration database. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.

psconfigsharepoint2016

Solution:

you may face this issue while installing manually instead of using the prerequisiteinstaller.exe

Uninstall WcfDataServices and then reinstalling the WcfDataServices using the prequisiteinstaller.exe automatically or using command with the appropriate parameter.

prerequisiteinstaller.exe /wcfdataservices56: WcfDataServices.exe location

Then delete two databases from SQL Server which are created by previous psconfiguration and run Products Configuration Wizard again, it will be successful.

amazon  amazonsp2016  amazonsp2016_2

Program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing SharePoint2016

This program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing from your computer.” error while running SharePoint Products Configuration Wizard.

api-ms-win-crt-heap-l1-1-0

*Missing update patches “Windows 10 Universal Runtime update” for Windows Server 2012 R2.

  • Installation of Windows Server 2012 R2 patch KB299926 is required so as to resolve this issue.

But  “The update is not applicable to your computer.” error came after that as below.

kb2919355

This is because Windows 10 Universal C Runtime KB2999226 is dependent on a Windows Server 2012 R2 Cumulative Update package in KB2919355.

Check windows updates, install patch KB2919355 and “The update is not applicable to your computer.”error will be resolved and after which there will be no error in installation of  the Windows 10 Universal C Runtime.

Have a look into my previous post Install Prerequisite (prerequisiteinstaller.exe) SharePoint 2016.

Unable to install Microsoft Information Protection and control Client 2.1 error SharePoint 2016