- A State Service Application has no database defined (SharePoint 2013)
- Accounts used by application pools or service identities are in the local machine Administrators group (SharePoint 2013)
- All State Service databases are paused for a State Service Application (SharePoint 2013)
- Alternate access URLs have not been configured (SharePoint 2013)
- Application pools recycle when memory limits are exceeded (SharePoint 2013)
- Business Data Connectivity connectors are currently enabled in a partitioned environment (SharePoint 2013)
- Cached objects have been evicted (SharePoint 2013)
- Critical state of this rule indicates that the Word Automation Services is not running when it should be running (SharePoint 2013)
- Content databases contain orphaned Apps (SharePoint 2013)
- Database has large amounts of unused space (SharePoint 2013)
- Databases exist on servers running SharePoint Foundation (SharePoint 2013)
- Databases require upgrade or not supported (SharePoint 2013)
- Databases running in compatibility range, upgrade recommended (SharePoint 2013)
- Databases used by SharePoint have outdated index statistics (SharePoint 2013)
- Databases within this farm are set to read only and will fail to upgrade unless it is set to a read-write state (SharePoint 2013)
- SPHA rule: Dedicated crawl target configuration has one or more invalid servers (SharePoint 2013)
- Distributed cache service is not enabled in this deployment
- Drives used for SQL databases are running out of free space (SharePoint 2013)
- Expired sessions are not being deleted from the ASP.NET Session State database (SharePoint 2013)
- Firewall client settings on the cache host are incorrect (SharePoint 2013)
- Immediate translations for the Machine Translation service are disabled (SharePoint 2013)
- InfoPath form library forms cannot be filled out in a Web browser (SharePoint 2013)
- InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured (SharePoint 2013)
- More Cache hosts are running in this deployment than are registered with SharePoint (SharePoint 2013)
- One of the cache hosts in the cluster is down (SharePoint 2013)
- One or more servers is not responding (SharePoint 2013)
- One or more web applications are configured to use Windows Classic authentication (SharePoint 2013)
- People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure (SharePoint 2013)
- Product / patch installation or server upgrade required (SharePoint 2013)
- Search – One or more crawl databases may have fragmented indices (SharePoint 2013)
- Some content databases are growing too large (SharePoint 2013)
- The Application Discovery and Load Balancer Service is not running in this farm (SharePoint 2013)
- The InfoPath Forms Services Maintenance Timer Job not enabled (SharePoint 2013)
- The Machine Translation Service is not running when it should be running (SharePoint 2013)
- The number of Distributed Cache hosts in the farm exceeds the recommended value
- The Security Token Service is not available (SharePoint 2013)
- SharePoint Health Analyzer rules reference (SharePoint 2013)
- The settings for the Machine Translation Service are not within the recommended limits (SharePoint Server 2013)
- The settings for Word Automation Services are not within the recommended limits (SharePoint 2013)
- The server farm account should not be used for other services (SharePoint 2013)
- The State Service Delete Expired Sessions timer job is not enabled (SharePoint 2013)
- The timer service failed to recycle (SharePoint 2013)
- The unattended Service Account Application ID is not specified or has an invalid value (SharePoint 2013)
- The Visio Graphics Service has a maximum cache age setting that will adversely impact performance (SharePoint Server 2013)
- The Visio Graphics Service has a maximum cache size setting that may adversely impact performance ((SharePoint Server 2013)
- The Visio Graphics Service has a maximum recalculation duration setting that will adversely impact performance ((SharePoint Server 2013)
- The Visio Graphics Service has a maximum Web Drawing Size setting that will adversely impact performance (SharePoint Server 2013)
- The Visio Graphics Service has a minimum cache age setting that may cause a security issue ((SharePoint Server 2013)
- The Visio Graphics Service has a minimum cache age setting that will adversely impact performance ((SharePoint Server 2013)
- This Distributed Cache host may cause cache reliability problems (SharePoint 2013)
- Validate the My Site Host and individual My Sites are on a dedicated Web application and separate URL domain (SharePoint 2013)
- Verify each User Profile service application has a My Site host configured ((SharePoint Server 2013)
- Verify each User Profile Service Application has an associated Managed Metadata Service Connection ((SharePoint Server 2013)
- Verify each User Profile Service Application has an associated Search Service Connection (SharePoint Server 2013)
- Verify that OAuth is configured correctly for the Machine Translation Service application in SharePoint 2013
- Verify that OAuth is configured correctly for the Machine Translation Service application proxy in SharePoint 2013
- Verify that the Activity Feed Timer Job is enabled (SharePoint 2013)
- Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted (SharePoint 2013)
- Web Applications using Claims authentication require an update (SharePoint 2013)
- Web.config file has incorrect settings for the requestFiltering element (SharePoint 2013)
- Web.config files are not identical on all machines in the farm (SharePoint 2013)
- XLIFF translations for the Machine Translation Service is disabled (SharePoint 2013)
Category Archives: Monitoring
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:
- Click the Start button and type Task Scheduler in the Start Search box.
- Select the Task Scheduler program to start Task Scheduler.
- Select the task to configure by locating the task in the task folder hierarchy. Right-click the task, and select Properties.
- On the Settings and Conditions tabs, update the task settings and conditions.
- Click OK.
Verify
To verify that the execution of a task has completed as expected:
- Click the Start button and type Task Scheduler in the Start Search box.
- Select the Task Scheduler program to start Task Scheduler.
- Select the task to run by locating the task in the task folder hierarchy.
- On the Actions menu click Run. You can also click Run in the Actions pane.
- 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.