Critical Non Impact

Medium Priority Events

SharePoint Access Denied For Writing To Registry
    This alert condition indicates that the service account for the IIS application pool that SharePoint Foundation 2010 does not have appropriate access permissions to write to a registry key. Registry keys might not be correctly updated to reflect configured settings.
SharePoint Configuration Database Is In Suspect Mode
    This alert condition indicates that the configuration database is in suspect mode. The timer service terminated unexpectedly in SharePoint or terminated with a service-specific error.
SharePoint Event Handler Failed To Load
    This alert condition indicates that the custom event receiver assembly or The SharePoint Foundation 2010 cannot be found, or is corrupted. The workflow may not function correctly.
Sharepoint Failed To Create A SharePoint Site
    This alert condition indicates that the create new SharePoint site feature is not working. Windows SharePoint Services enables administrators to create new SharePoint sites. Site owners and (depending on the site settings) site visitors can also create sub-sites.
Sharepoint Failed To Load Index
    This alert condition indicates that the Windows SharePoint Services Search (SPSearch) service could not load the index.
Sharepoint Failed To Load Protocol Handler
    This alert condition indicates a protocol handler load failure. Windows SharePoint Services uses protocol handlers to access the content that you want to crawl. This condition indicates that the protocol handler cannot be loaded. This indicates that documents that require the protocol handler cannot be crawled.
Sharepoint Failed To Load Safe Control Assembly Path
    This alert condition indicates a safe control assembly path load failure. A Web Part can be registered as a safe control for use in Windows SharePoint Services. To register a Web Part as a safe control, add a SafeControl element in the SafeControls block that specifies the Web Part in the top-level web.config file of the virtual server. When you add and delete Web Part packages or solutions using the stsadm.exe tool, this registration is usually handled during the deployment process.
Sharepoint Insufficient Disk Space
    This alert condition indicates that there is insufficient disk space on the resource. When crawling one or more content sources, the Windows SharePoint Services Search (SPSearch) service updates the index, which is stored in the file system of the search server. If a hard disk that contains this index has inadequate free space to update the index, this alert occurs and the crawl is paused.
SharePoint Insufficient Permissions To Write To The Configuration Data Cache
    This alert condition indicates that the configuration cache directory has security settings which prevent write access to its contents. Although configuration objects can be updated farm-wide, the objects are not updated locally.
Sharepoint Internal Plug In Error
    This alert condition indicates an internal plug-in error. A plug-in is a component of the search server that is used to process content and properties from crawled items. When this error occurs, a Dr. Watson report is typically created and an entry that contains the call stack of the exception is written to the Windows NT Event log.
Sharepoint IRM Manifests Are Invalid
    This alert condition indicates that IRM manifests are invalid. In order for Windows SharePoint Services to use Windows Rights Management Services (RMS), the RMS client application must be installed on every front-end web server in the web farm.
Sharepoint Locale ID Has Changed
    This alert condition indicates that the Locale ID has changed. Every web site based on Microsoft Windows SharePoint Services can be customized to use specific regional settings that apply to the users of your site. One of these settings, Locale ID, controls the numbering, sorting, calendar, and time-formatting for the web site
SharePoint Master Merge Error
    This alert condition indicates a master merge error. A master merge is the process of merging a group of indexes into a single index. If this alert occurs repeatedly, the Windows SharePoint Services Search (SPSearch) service will eventually be unable to index new documents.
Sharepoint Plug In Failed To Connect To SQL Server
    This alert condition indicates that a plug-in failed to connect to SQL Server. A plug-in is a component of the search server that is used to process content and properties from crawled items. This alert indicates that an error occurred in the Windows SharePoint Services Search (SPSearch) service. The plug-in did not connect to the SQL Server instance listed in the Windows NT Event log, and the update of the content source cannot continue.
Sharepoint Rights Management Services (RMS) Client On A Computer Running Windows SharePoint Services Registered An Error With Its Environment
    This alert condition indicates that Information Rights Management (IRM) relies on the underlying Rights Management Services (RMS) framework, which includes the Windows RMS client application, to create issuance licenses and perform the actual encryption and decryption of rights-managed content. Every front-end web server in a Windows SharePoint Services web farm must have the Windows RMS client installed to access the RMS APIs.
Sharepoint SharePoint Administration Service Is Disabled
    This alert condition indicates that the SharePoint Administration service is disabled. Several features of Microsoft Windows SharePoint Services rely on scheduled background processes called timer jobs. Administrators can configure and schedule timer jobs by using Central Administration.
SharePoint SharePoint Lists Cannot Receive Email Rule
    This alert condition indicates that SharePoint lists are not receiving incoming email. This issue indicates that the SharePoint timer service does not have read/write permission on the drop folder or the drop folder specified in the incoming email setting does not exist. The SharePoint list cannot receive incoming email or a duplicate item appears in list that is receiving incoming email.
Sharepoint SQL Server Database Login Failed
    This alert condition indicates that the SQL login has failed. The user name or password for the service account was invalid before the session or became invalid during the session. Users will be unable to access SharePoint sites.
Sharepoint The Active Directory Organization Unit Registered In Windows SharePoint Services Does Not Exist
    This alert condition indicates that the Active Directory organizational unit registered with Windows SharePoint Service does not exist. When Windows SharePoint Services is in Active Directory account creation mode, any user added to a site is automatically added to the Active Directory organizational unit identified for use by SharePoint.
SharePoint 2007 Error Backing Up Registry To Shared Services Provider Database
    This alert condition indicates that an error occurred because the Office Search service could not write the registry keys to the SSP database. Possible causes include: A connectivity issue between the index server and the computer running SQL Server that contains the Shared Services Provider database, the disk on which the SSP database is stored is full, the connection to the SQL Server database is timing out, the Shared Services Provider database has reached the maximum database size set in the computer that is running SQL Server, or the service account used to communicate with the computer running SQL Server has inadequate permissions. The site’s Search function may not work as expected.
SharePoint 2007 Plug In Failed To Connect To SQL Server
    This alert condition indicates that a plug-in did not connect to the computer that is running the SQL Server instance, and the update of the content source cannot continue. The plug-in is a component of the search indexer that is used to process content and properties from crawled items.
SharePoint 2007 Site Directory Scan Job Failed
    This alert condition indicates that the timer job that scans for broken links in the site directory has failed.
SharePoint 2007 Synchronization Of User Profiles
    This alert condition indicates that a site collection or a content database has moved from one web application to another without running the preparetomove http://technet.microsoft.com/en-us/library/cc262122.aspx command first. Without running the preparetomove command, the SSP thinks the site is new and tries to insert data into the UserMemberships table that already exists. This causes SQL to throw a duplicate key error and causes the profile synchronization job to fail.
SharePoint 2010 Access Denied For Writing To Disk
    This alert condition indicates that the service account for the IIS application pool that SharePoint Foundation 2010 uses does not have appropriate permissions to write to a file or folder in the NTFS file system. Files may not be updated correctly to reflect configured settings.
SharePoint 2010 Alternate Access Mapping Update Failed
    This alert condition indicates that the alternate access mapping specified in the configuration cache was not applied to the IIS settings of the local machine. This may cause incorrect links to be stored or returned to users while accessing the SharePoint site.
SharePoint 2010 An Exception Occurred When Trying To Issue A Security Token ID 3242
    This alert condition indicates that an exception occurred when trying to issue a security token ID 3242. This issue occurs when the search query logging thread reuses expired credentials, which produces less-relevant search results when performing a search request.
Sharepoint 2010 An Operation Failed Because Certificate Has Validation Errors
    This alert condition indicates that an administrator has deleted the local trust relationship of the farm from the Security section of the Central Administration web site. Users may be unable to log in to claim-based web apps and may be restricted from activating/deactivating any feature to a site collection under a claims-based web application.
SharePoint 2010 Backup Failed Due To Insufficient Permissions
    This alert condition indicates that the account that is performing the backup does not have sufficient permissions to write to the backup folder. The SQL server service and/or SharePoint timer service account do not have Full Control access to the backup folder. The SharePoint backup job will fail.
Sharepoint 2010 Backup Failed Due To Insufficient Permissions
    This alert condition indicates that a backup failed due to insufficient administrator permissions. This issue can occur when a website backup fails because the administrator has inadequate permissions to perform a backup to a file share or folder on the local server or SQL Server database.
SharePoint 2010 Business Data Connectivity Service SQL Exception
    This alert condition indicates that the Business Data Connectivity Service has an SQL exception issue. Possible causes: the metadata database server is down or inaccessible due to network issues, the connection information for the Business Data Connectivity (BDC) service is incorrect, or the BDC service was not provisioned correctly. SharePoint will be unable to fetch external data.
Sharepoint 2010 Cannot Connect To SMTP Host
    This alert condition indicates that SharePoint Foundation 2010 cannot connect to the Simple Mail Transfer Protocol (SMTP) host.
SharePoint 2010 Cannot Resolve Name Of The Outbound SMTP Server
    This alert condition indicates that SharePoint Foundation 2010 either cannot connect to the SMTP host or cannot resolve the name of the outbound SMTP server. Users will not receive SharePoint alert emails, subscription alert emails, emails regarding exceeded quotas, or administrator email notifications.
SharePoint 2010 Excel Calculation Services Configuration Database Access Failed
    This alert condition indicates that the Configuration database may be offline or unavailable
SharePoint 2010 Excel Calculation Services Internal Error
    This alert condition indicates that the Excel Services Application server experienced an unexpected failure.
SharePoint 2010 Excel Calculation Services Is Not Running Locally
    This alert condition indicates that the load-balancing scheme is set to Local but Excel Services Application is not running on that Web front end computer.
SharePoint 2010 Excel Calculation Services Localized File Not Found
    This alert condition indicates that a localized template workbook file was not found. The localized template file was not correctly installed on the computer, or is corrupt. The file must be reinstalled. The easiest method for reinstalling the template is to repair the installation.
SharePoint 2010 Excel Calculation Services Machine No Longer Available
    This alert condition indicates that the front-end Web application sent a request to a specific server for Excel Services Application and did not get a response.
SharePoint 2010 Excel Calculation Services Maximum Memory Configured Has Been Exceeded
    This alert condition indicates that the Excel Services application has exceeded its MaxPrivateBytes setting value. Requests to the server are being denied as a result.
SharePoint 2010 Excel Calculation Services Unexpected Workbook Failure
    This alert condition indicates that a corrupted workbook file was loaded on the Excel Services Application server.
SharePoint 2010 Excel Calculation Services Workbook Disk Cache Cannot Be Created
    This alert condition indicates that the Excel Calculation Services Workbook disk cache cannot be created.
SharePoint 2010 Exception In Execute Method Of Job Definition
    This alert condition indicates that the Microsoft SharePoint Foundation 2010 timer job has thrown an exception. The third-party timer job or the Microsoft SharePoint Foundation 2010 timer job either cannot be found or is corrupt.
SharePoint 2010 InfoPath Forms Services An Illegal Cross Domain Submit Data Connection Was Attempted
    This alert condition indicates that the form template security level is not set to full trust.
SharePoint 2010 InfoPath Forms Services Business Logic Exception Occurred While Loading A Form
    This alert condition indicates that an unhandled business logic exception occurred while loading a form template.
SharePoint 2010 InfoPath Forms Services Form S Are Being Reloaded Frequently In Memory
    This alert condition indicates that low-memory conditions exist or a form is consuming a large amount of memory.
SharePoint 2010 Issue With Index Propagation
    This alert condition indicates that the SharePoint 2010 Search Query component has been disabled and needs to be restarted. This issue may be due to index corruption. Searches may not function properly for new contents buy may work for old contents.
SharePoint 2010 No Search Result For Anonymous Users
    This alert condition indicates that application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance. Search is not configured properly. When users search for content they will not receive search results.
SharePoint 2010 Search Index Corrupted
    This alert condition indicates that an index corruption was detected in a catalog. This issue can occur corruption is present on the hard disk or the index. No newly-added content will be crawled as the crawling job will not run until the issue is fixed.
SharePoint 2010 Search Indexer Initialization Index Failed
    This alert condition indicates that the Content index could not be initialized. Possible causes: The index files on the disk are inaccessible, there is not enough available memory, or the index itself is corrupt. The crawl or search query that involves the component will stall and processing will stop.
SharePoint 2010 Search Propagation Communication Error
    This alert condition indicates that a Crawl Component for the search application could not communicate with the query server. Possible causes: the crawl component might have expired credentials, network issues are preventing communication, or the the query server may be unresponsive. The crawl does not progress and appears to stall. The crawl log shows no new crawled documents. Users may be unable to view applications in their browsers, or the service may otherwise be unavailable.
SharePoint 2010 Secure Store Proxy Unexpected Exception
    This alert condition indicates that a Secure Store proxy unexpected exception occurred. Possible causes: the application server may be down or inaccessible due to network issues, or the secure store service application may not be provisioned correctly. If the secure store service application is enabled on more than one SharePoint server, client computers will not be affected. Otherwise, computers relying on the secure store credential database will fail to authenticate and will be unable to access the SharePoint site.
SharePoint 2010 Secure Store Reencrypt Credentials Failed
    This alert condition indicates that the Secure Store reencrypt credentials failed. Possible causes: the master encryption key is not valid, the secure store database failed while it was being encrypted, or the secure store database is corrupted. Computers relying on the secure store credential database will fail to authenticate and will be unable to access the SharePoint site.
SharePoint 2010 Secure Store SQL Exception
    This alert condition indicates that the Secure Store Service application connects to the credential database for reading or writing credentials. This event is logged when the service application fails to connect to the database. Possible causes: the database server is down, there is no access to the database server due to network issues, the secure store service application database connection information is incorrect, or the secure store service application metadata database was not provisioned correctly. Computers relying on the secure store credential database will fail to authenticate and will be unable to access the SharePoint site.
SharePoint 2010 Site Synch Failed
    This alert condition indicates a failure in syncing site for ContentDB WebApp . This issue can occur when a site collection or a content database is moved from one web application to another without running the Preparetomove command first. This causes the profile synchronization job to fail.
SharePoint 2010 The Application Has An Invalid AppPoolID Set
    This alert condition indicates that application /_vti_bin/sts belonging to site site ID has an invalid AppPoolID set. The application will be ignored as a result. IIS is configured incorrectly. The site to which the application belongs may not function as expected.
SharePoint 2010 The Application Pool Account Has Insufficient Permissions To Add User Accounts To Active Directory
    This alert condition indicates that the application pool account does not have the permissions needed to add new user accounts to Active Directory. Account creation mode will not work correctly and user data will be prevented from being added or read. User accounts will not be automatically created in Active Directory.
SharePoint 2010 The Application Pool Account Must Be Registered As A Kerberos Service Provider
    This alert condition indicates that the Web application pool account is not a registered security provider name. If the site is using either forms-based authentication or Web single sign-on, the authentication provider could not be loaded because no membership provider name was specified. If you’re using Kerberos v5 authentication, the Web application pool account is not a registered security provider name. The application pool may not work as expected.
SharePoint 2010 The Management Agent Failed
    This alert condition indicates that the management agent failed. This failure occurred as the result of incorrect settings in FIM Synchronization Service Manager (SSM). As a result, Active Directory profile imports will fail and Full or Incremental Profile Synchronizations will not successfully complete.
SharePoint 2010 The Start Address Cannot Be Crawled
    This alert condition indicates that a start address cannot be crawled. The crawler does not have access to a site or a website is inaccessible. The content which cannot be crawled will be unavailable in the web site search results.
SharePoint 2010 The User Profile Synchronization Service Is Not Starting
    This alert condition indicates that, when attempting to start the User Profile Synchronization Service from the Central Administration site, the service starts but remains in a Starting state for a few minutes before returning to a Stopped state. The User Profile service is not starting as the recursive triggers enabled property for the model database is set to True in the SQL instance. The user profile service will be unable to synchronize user profile information from Active Directory.
SharePoint 2010 Timer Job To Update Central Admin Failed
    This alert condition indicates that the Microsoft SharePoint Server 2010 timer job to update Central Administration on a specific URL was not created, or the local registry-based URL for the Central Administration was not updated. This failure may be caused by a communication failure with the configuration database while the configuration object was created. It may also be due to a central administration URL registry location on the local server that failed to be updated because of registry key permission issues. The central administration web site may be inaccessible.
SharePoint 2010 Unable To Write To Trace Log
    This alert condition indicates that the tracing service cannot create a new log file. SharePoint will be unable to write detailed information to a log file.
SharePoint 2010 User Profile Service Create MySite Failure
    This alert condition indicates a naming conflict caused by the Site Naming Format setting. Users will receive an error message that their My Site could not be created.
SharePoint 2010 Visio Graphics Service Was Unable To Connect To A Requested Data Provider
    This alert condition indicates that visio Services in Microsoft SharePoint Server 2010 cannot connect to a data provider that was referenced by a user in a Visio diagram. Diagrams may not refresh data.
SharePoint 2010 Windows SMTP Service Is Not Running Rule
    This alert condition indicates that automatic configuration for incoming email is enabled but the Windows SMTP service is not running. This issue indicates that the Windows SMTP service is not installed or not running on one or multiple servers. Users will not receive SharePoint alert emails, subscription alert emails, emails about exceeded quotas, or administrator email notifications.
SharePoint 2010 Word Services Timer Job Failed
    This alert condition indicates that SharePoint Document Conversion jobs may not execute because the timer job 1 for the service application 2 does not appear to be active. Either an administrator has disabled the Word Automation Services timer job or an error has occurred in provisioning it. The existing word automation timer job will not complete and, if a new job is successfully added to the database, the conversion job will not start.
SharePoint 2010 Word Viewing Service Backend Not Reachable
    This alert condition indicates that the Application Manager on the application server has stopped unexpectedly. It is possible that the Word Viewing service application or the file conversion service may have stopped working. Users will receive an error when they try to view a Word document that has not been viewed before and may be unable to convert an open file to a different format.
Sharepoint Database Capacity Warning Reached
    This alert condition indicates that the SharePoint database has reached capacity. The content databases in this cluster are full. You cannot add more web sites until you change the content database web site capacity settings or add more content databases. When this alert is received, system administrators should increase database capacity or add more content databases.
SharePoint Search Host Controller Not In Running State
    SharePoint Search Host Controller- Not In Running State
SharePoint Search Host Controller Not In Running State [Unexpected]
    SharePoint Search Host Controller- Not In Running State [Unexpected]
Sharepoint Search Index Is Corrupt
    This alert condition indicates that the Windows SharePoint Services Search (SPSearch) service content index is corrupt. This issue can occur on either an index server or a query server. When this error occurs on an index server, the SPSearch service automatically attempts to reset and start a full update of the content index. The hard drive containing the content index is out of space or a hardware problem has corrupted the index. The search may not work as expected.
Sharepoint Server : Backup Failed Due To Timer Job Failure
    This alert condition indicates that a SharePoint backup failed as the result of a timer error. SharePoint Administrators can configure and schedule a timer job to create a backup of each web application using the stsadm command.
Sharepoint Service Instance Provisioning Failed
    This alert condition indicates that service instance provisioning failed. When you use the Services on Server page in Central Administration to start or stop a service, a timer job is used to perform this action. This error indicates that the service could not be started or stopped.
SharePoint Services A Content Query Web Part Failed To Return Content
    This alert condition indicates that a web part failed to return content on the query for which it has been configured. A web part property setting could be incorrect or the database that is serving the content for the web site may be unavailable.
SharePoint Services A Runtime Exception Occurred In The Business Data Catalog Database Adapter
    This alert condition indicates that the query or stored procedure that is associated with a method in the Business Data Catalog application definition file could not be run.
SharePoint Services Administration Site For The Shared Service Provider Is Missing
    This alert condition indicates that the administration site of the Shared Services Provider (SSP) is not available.
SharePoint Services Business Data Catalog Web Service Adapter Transport Error
    This alert condition indicates that a transport error occurred while Microsoft Office SharePoint Server 2007 was trying to connect to the Web service that is specified in the Business Data Catalog application definition file.
SharePoint Services Content Database Synchronization Failed
    This alert condition indicates that profile and membership synchronization was abandoned for this content database. The profile synchronization timer job will attempt to synchronize this content database the next time it is run. Possible causes include: Network failure between the computer running SQL Server and other servers in the farm, the profile synchronization timer job used for synchronization has insufficient permissions to the content database, or a timeout occurred while the profile synchronization timer job was communicating with the computer that is running SQL Server.
SharePoint Services Crawler Cannot Read From Registry
    This alert condition indicates that the search crawler was unable to read from the registry in order to load configuration information that the OSearch service needs. The crawler component of search uses the Office SharePoint Server Search (OSearch) service to read its settings from the Windows registry of the index server.
SharePoint Services Encountered Errors While Indexing Anchor Text
    This alert condition indicates that an error in the ranking calculation occurred while the Office SharePoint Server Search (OSearch) service was updating the content index. The OSearch service discovers the anchor text for each page that is crawled and stores this information in the computer that is running SQL Server. It then uses this anchor text as part of the ranking calculation that is used to determine how close to the top of search results pages particular pages will appear. This alert occurs at the end of a crawl that contains anchor text calculation errors for any page that was crawled. The severity of this error is dependent on how many pages are affected. This ranking calculation error only affects pages on which the anchor text calculations failed.
SharePoint Services Error Communicating With Excel Calculation Services
    This alert condition indicates that the front-end Web server attempted to establish a connection to Excel Calculation Services, but a communication error occurred.
SharePoint Services Exception Occurred During Business Data Catalog Web Service Proxy Generation
    This alert condition indicates that Microsoft Office SharePoint Server 2007 could not generate a Web Services Description Language (WSDL) proxy for the web service that is specified in the Business Data Catalog application definition file.
SharePoint Services Exception Occurred In The Business Data Catalog Database Adapter Connection
    This alert condition indicates that the Business Data Catalog database adapter that Microsoft Office SharePoint Server 2007 uses cannot connect to the backend database that is specified in the Business Data Catalog application file.
SharePoint Services Failed To Load Protocol Handler
    This alert condition indicates that the protocol handler cannot be loaded. As a result, documents that require the protocol handler cannot be crawled.
SharePoint Services Index Is Corrupt
    This alert condition indicates that the Office SharePoint Server Search (OSearch) service has detected that the content index is corrupted. This can occur on either an index server or a query server. When this error occurs on an index server, the OSearch service automatically attempts to reset and start a full update of the content index.
SharePoint Services InfoPath Forms Services Event Counter Mismatch
    This alert condition indicates that the current version of session state does not match the version that a server running InfoPath Forms Services expected.
SharePoint Services My Site Creation Failure
    This alert condition indicates that a My Site could not be created for the user specified in the exception message.
SharePoint Services Publication Of Ranking Information Failed
    This alert condition indicates that publication of anchor text failed. In this case, the index might be available, but the relevance of search results will be diminished. Possible causes include: the Index server is out of memory, the drive volume on the index server that contains the content index has inadequate space, or hardware failures while writing to the hard drive volume that contains the content index.
SharePoint Services Query Server Removed From Rotation
    This alert condition indicates that a query server has been removed from the load-balanced rotation. Possible causes include network connectivity issues, or a corrupt query server index. Search queries may not work as expected.
SharePoint Services Search Service Unable To Index New Documents
    This alert condition indicates an issue with index propagation from the index server. If this alert occurs repeatedly, the Office SharePoint Server Search (OSearch) service will eventually be unable to index new documents. Possible causes include: Inadequate disk space on the hard drive volume that contains the content index, hardware problems occurring on any server running the OSearch service, or the server is out of memory. The content index is corrupt.
SharePoint Services Shared Services Provider Synchronization Failed
    This alert condition indicates that a Shared Services Provider (SSP) failed to synchronize information with the configuration database. The service accounts used to access the computer running SQL Server may have changed since the server farm was deployed and, because of this, the SSP service could not write to the configuration database. There may also be network connectivity issues between the computer that is running SQL Server and all other servers in the farm. An individual service within the SSP could not synchronize its properties with the configuration database.
SharePoint Services Site Synch Failed
    This alert condition indicates that a particular site collection encountered a failure during profile and membership synchronization. Possible causes include: Network failure between the computer running SQL Server and other servers in the farm, the profile synchronization timer job used for profile and membership synchronization has insufficient permissions to the content database, or a SQL Server computer timeout occurred while the profile synchronization timer job used for profile and membership synchronization was communicating with the computer running SQL Server.
SharePoint Services SQL Server Database Error
    This alert condition indicates that an unexpected SQL Server database error occurred while the Office SharePoint Server Search (OSearch) service that is running on the index server attempted to communicate with the database. Possible causes: A connectivity issue between a server in the server farm running the Office SharePoint Servers Search (OSearch) service and the computer running SQL Server, the disk on which the database is stored is full, the connection to the SQL Server database is timing out, or the service account used to communicate with the computer running SQL Server has inadequate permissions. The Search service may not function properly.
SharePoint Services Sweep Synch Failed
    This alert condition indicates that a failure was encountered while synchronizing user profiles for new active users on a content database. Possible causes include: Network failure between the computer running SQL Server and other servers in the farm, the profile synchronization timer job used for synchronization has insufficient permissions to the content database, or a timeout occurred while the timer job was communicating with the computer that is running SQL Server.
SharePoint Services The Launcher Cannot Register With The Load Balancer
    This alert condition indicates that the Office Document Conversions Launcher Service (DCLauncher) cannot register with the Office Document Conversions Load Balancer Service (DCLoadBalancer). The Office Document Conversions Load Balancer Service (DCLoadBalancer) service is not running. The document conversion process will not work.
SharePoint Services The Start Address Cannot Be Crawled
    This alert condition indicates that the start address cannot be crawled. Access is denied. Verify that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205) Event Information.
Sharepoint SQL Server Database Error
    This alert condition indicates a SQL Server database error. In a search-enabled server farm, the search server periodically writes to or reads from the SQL Server database. This alert indicates that an unexpected SQL Server database error occurred while the Windows SharePoint Services Search (SPSearch) was attempting to communicate with the database.
Sharepoint Timer Jobs Failure
    This alert condition indicates a Timer Jobs failure. Several features of Microsoft Windows SharePoint Services rely on scheduled background processes referred to as timer jobs. Administrators can configure and schedule timer jobs by using HTML Administration pages in Central Administration.
Sharepoint2010 Access Denied For Writing To Registry
    This alert condition indicates that registry access was denied for a registry key or file folder update. This condition indicates that registry access was denied when the application pool used by SharePoint Foundation 2010 attempted to update a registry key or file folder because the service account used by the application pool has inadequate permissions.
Windows SharePoint Services : An Error Occurred While Communicating With The SMTP Server
    This alert condition indicates that an error occurred while communicating with the SMTP server. Microsoft Windows SharePoint Services sends alerts and other administration messages by using an SMTP mail server. You can specify which SMTP server to use, and you can set the email address to use for sending alerts and receiving replies for all sites, by using the Outgoing Email Settings page in Central Administration.
Last modified April 17, 2020