SharePoint Health Analyzer rules reference SharePoint 2013

Advertisements

Windows server Task scheduler Monitoring event id 111

The history of a task is tracked by events. These events can be viewed in Task Scheduler for each task to track when the task was registered, run, and when it completed or failed. The progress of a task can be monitored through its history. A task can be controlled by running or stopping the task manually (on-demand).

Event Details

Product:  Windows Operating System
ID:  111
Source:  Microsoft-Windows-TaskScheduler
Version:  6.1
Symbolic Name:  JOB_TERMINATION
Message:  Task Scheduler terminated the “%2” instance of the “%1” task due to exceeding the time allocated for execution, as configured in the task definition. Increase the configured task timeout or investigate external reasons for the delay.

Resolve

Fix task configuration settings

The task was stopped due to a configured setting. Possible causes include:
•The task ran for longer than the maximum configured run time.
•The task was configured to stop when the computer switched to battery power.
•The task was configured to stop when the computer is no longer idle.
•The task was configured to stop when a new instance of the task is triggered.

This behavior might be as expected. However, if the behavior was unexpected you can reconfigure the task configuration settings.

To update the task settings and conditions:

  1. Click the Start button and type Task Scheduler in the Start Search box.
  2. Select the Task Scheduler program to start Task Scheduler.
  3. Select the task to configure by locating the task in the task folder hierarchy. Right-click the task, and select Properties.
  4. On the Settings and Conditions tabs, update the task settings and conditions.
  5. Click OK.

Verify

To verify that the execution of a task has completed as expected:

  1. Click the Start button and type Task Scheduler in the Start Search box.
  2. Select the Task Scheduler program to start Task Scheduler.
  3. Select the task to run by locating the task in the task folder hierarchy.
  4. On the Actions menu click Run. You can also click Run in the Actions pane.
  5. Click the History tab for the task to verify that it contains events indicating the task was registered successfully. Also, ensure that the task completed successfully or that the task timed out as expected.

Windows server Task scheduler Monitoring event id 102

The history of a task is tracked by events. These events can be viewed in Task Scheduler for each task to track when the task was registered, run, and when it completed or failed. The progress of a task can be monitored through its history. A task can be controlled by running or stopping the task manually (on-demand).

Event Details :

Product:               Windows Operating System
ID:                           102
Source:                  Microsoft-Windows-TaskScheduler
Version:                 6.1
Symbolic Name:  JOB_SUCCESS
Message:               Task Scheduler successfully finished the “%3” instance of the “%1” task for user “%2”.

Resolve :

This is a normal condition. No further action is required.

Slow SharePoint improve performance without upgrading hardware

what you can do if your SharePoint is sometimes very slow.

E.g.: on the first start of a Site
Sometimes during the day a search query will take about a minute until you get results…..

Just look on that article: http://support.microsoft.com/kb/2625048

it will improve “feeled” performance (site response times) massive, if you’re going to implement both solutions.

Disabling CRL Check is just necessary if the SP Server does not have internet connectivity, that means proxy settings must be configured for the server itself

http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx, and your proxy must allow traffic from the server of course.

Delete cbs.log file its growing large ?

System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files.Run the System File Checker tool (SFC.exe) to scan your system files and to repair missing or corrupted system files.CBS.Log file is generated by the Microsoft Windows Resource Checker (SFC.exe).

The SFC.exe program writes the details of each verification operation and of each repair operation to the CBS.log file. The CBS.persist.log is generated when the CBS gets to be around 50 meg in size. CBS.log is copied to cbs.persist.log and a new cbs.log file is started.

Solution 1 :

you can try compressing the file:

1.Right click on the CBS.log file
2.Click on Properties
3. On the General tab, click Advanced
4. Check “Compress contents to save disk space” and click on OK

Solution 2 :

Another Workaround is to turn off unnecessary services that may calling into CBS;

To disable CBS log, you may change registry key in

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component
Based Servicing] EnableLog=dword:00000000

In addition,also recommended to run sfc/scannow to check the health of system files.

Solution 3 :

If you are sure your system is running fine, you can delete this file. SFC.exe will create a new one, next time it is run.

Please follow below method to delete:

  1. Stop TrustedInstaller.exe (Windows Module Installer) in Taskmanager Services tab. Additionally if you cannot, open the Taskmanager Processes tab and End Task the same process.

  2. Delete or move all the .log files in the C:\Windows\Logs\CBS directory, you can delete the .persist and .cab files as well.

  3. Start Windows Module Installer service (TrustedInstaller.exe) again