KQP_Alert_InvalidPortalSetting
Invalid portal settings.
Problem Description:
Invalid portal settings: There might be a problem with one or more values of the e-mail headers.
Possible Cause:
- The SharePoint Server is installed in stand-alone mode and the SharePoint Alert and SharePoint Timer services are using Local system account.
Advice: - Click Start > Settings > Control Panel. Double-click Services.
- Right-click SharePoint Portal Alert service and click Properties.
- Click the Log On tab. Change the Local system account to domain account.
Follow the same procedure for the SharePoint Timer Service.
Note: The SharePoint Alert and the SharePoint Timer services have to contact Active Directory for security issues before sending an e-mail. Therefore these services must use a domain account.
This situation is supported by MSPS 2003.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'SharePoint Portal Alert Service' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 155
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_Alert_Noti_NoMAILServerRes
The SMTP Server is not functioning correctly.
Problem Description:
The alert is not working, because the SMTP Server is not functioning correctly.
Possible Cause(s):
- The SMTP Server does not allow the SharePoint Server to relay e-mails through it.
- The SMTP Server is offline.
- The antivirus software installed on the SharePoint computer is blocking the SMTP port.
- The SMTP service is not running on the SMTP Server.
- The SMTP host is not correctly configured in the Central Administration.
Advice:
Ping the SMTP Server from SharePoint computer.-
Add the SharePoint Server to the list in SMTP Server.
- Start the SMTP Server if it is offline.
- Ensure that the normal client version and not the portal edition of the antivirus software is installed on the SharePoint Server.
- Start and configure the SMTP service.
- In the Internet Information Services Manager, connect to the SMTP Server.
- Expand the server node and look for the SMTP virtual server used by Windows SharePoint Services 3.0.
- Right-click the correct virtual server and click Start.
- To configure the virtual server, click the Properties tab.
- On the Delivery tab, click Outbound Security.
- In the Outbound Security dialog box, select either the Anonymous access or the Integrated Windows Authentication. If the Integrated Windows Authentication is selected, ensure that the Windows SharePoint Services Central Administration application pool account has access by selecting the Account and Password boxes.
- Configure outbound e-mail settings in the Central Administration.
- In Central Administration, on the navigation pane, click Operations.
- On the Operations page, in the Topology and Services section, click Outgoing e-mail settings.
- On the Outgoing E-Mail Settings page, under Mail Settings, enter the correct SMTP Server in the Outgoing SMTP Server box.
Note: More information is available in the diagnostic logs on the Configure Diagnostic Settings page in SharePoint Portal Server Central Administration.
This situation is supported by MSPS 2003.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'SharePoint Portal Alert Service' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 151
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_Connection_To_SP_DB
Unable to connect SharePoint database.
Problem Description:
Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010) could not connect to the SharePoint database.
Possible Cause:
- The computer running SQL Server was turned off.
- The SQL Server service was paused.
- Network connectivity problems.
- The service account used to initialize the connection lacks permissions on the SharePoint database.
Advice: - Start the computer running SQL Server, if it is turned off.
- Start the SQL Server service.
- Check if there is any network connectivity problem
- Check if service account has enough permission for connecting to SharePoint database.
Note: Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010) uses SQL Server to store most of the content for the website as well as configuration settings. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server.
The default configuration has the following SQL syntax:
*IF (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Windows SharePoint Services 3' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 3355) *OR (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Microsoft-SharePoint Products-SharePoint Foundation' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 3355)
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_ECS_Active_Sessions
Sessions exceed 80 percent of maximum sessions per user value.
Problem Description:
Excel service will stop responding if number of sessions per user exceeds maximum sessions per user when anonymous access is enabled to a SharePoint site.
Possible cause:
Number of sessions per user exceeds the maximum number of sessions per user value.
Advice:
To resolve this issue, increase the maximum number of sessions per user.To do this, follow these steps:
- Login to SharePoint 3.0 Central Administration
- On the Central Administration page, click Application Management tab
- On the Application Management page, click Create or configure this farm's shared services
- Open Shared Services Admin Site
- On the Shared Services Administration page, click Edit Excel Services Settings
- On the Excel Services Settings page, type the
maximum number of sessions per user under Session Management, and then click OK
Change the situation formula Active Sessions > 80 percent of (maximum number of sessions per user) in TEP as per the new value of maximum number of sessions per user.
Note: By default, the maximum number of sessions per user is 25. This number is set at the shared services provider level. It is not based on individual trusted file locations. Therefore, only 25 sessions for anonymous users can be active at the same time on Excel Services. This is true even if the Excel workbooks are in different trusted file locations.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EXCEL_CALCULATION_SERVICES.Active_Sessions *GT 20
This situation is evaluated every 2 minutes.
This situation is available for distribution.
KQP_ECS_Session_Time_Out
Inactive session or workbook includes non supported features.
Problem Description:
- When the session time-out occurs, excel workbook data gets lost and also increases the value of Request with errors per second attribute of Excel Calculation Service by 1.
- Selected workbook cannot be loaded because it contains the features that are not supported by Excel Services and increases the value of Request with errors per second attribute of Excel Calculation Service by 1.
Possible cause(s):- Session Time Out exceeds the default limit.
- The workbook that is selected cannot be loaded because it contains the following features that are not supported by Excel Services:
Comments, ActiveX controls, Shapes, Text Boxes, Pictures, WordArt, Clip Art, Embedded OLE objects, Ink Annotations, Forms Toolbar controls, Control Toolbox controls, Charts that are part of a group, Signature Lines, or Camera objects.
Advice: - Change the session time-out as per the user requirement.
-
On the Central Administration page, click Application Management tab.
-
On the Application Management page, click Create or configure this farms shared services.
- Open Shared Services Admin Site.
- On the Shared Services Administration page, click Edit Trusted File Locations.
- On the Trusted File Locations Settings page, Click on Add Trusted file location and type the session time-out under Session Management, and then click OK.
- Use only the features supported by Excel Service.
Note: Session can remain active only for 300 seconds. This is a default value set at shared services provider level. A session time-out can occur even while interacting with Excel Services.
Once workbook gets opened in Excel Services, user can either view or interact with the workbook to see different results. For example, user can sort, filter, refresh data, or set parameters. These interactions occur within the session but do not change the workbook currently loaded into Excel Services. These interactions are also temporary, and so when a session time-out occurs, the interactions are not saved, and there are no changes made to the original workbook.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EXCEL_CALCULATION_SERVICES.Requests_with_Errors_Per_Sec *GE 1
This situation is evaluated every 5 minutes.
This situation is available for distribution.
Form actions exceeded Number of actions per postback value.
Problem Description:
When InfoPath Web form is loading and number of forms actions exceeded default value of 200, user session is terminated resulting in the loss of all form data entered during the session, and an error message is generated saying This session has exceeded the amount of allowable resources.
Possible Cause:
Form actions exceeded Number of actions per postback value.
Advice:
This value is configurable and can be changed by the administrator. To resolve this issue, increase the Number of actions per postback value. To do this, follow these steps:
-
Login to SharePoint 3.0 Central Administration.
-
Go to Configure InfoPath Forms Service in the InfoPath Forms Services section from Application Management tab.
- In the Number of actions per postback box, change the value to be above the number of form actions listed in message attribute of Event Log attribute group. The default value is 200.
Note: This value is configurable and can be changed by the administrator. To resolve this issue, increase the Number of actions per postback value. To do this, follow these steps: - Login to SharePoint 3.0 Central Administration.
- Go to Configure InfoPath Forms Service in the InfoPath Forms Services section from Application Management tab.
- In the Number of actions per postback box, change the value to be above the number of form actions listed in message attribute of Event Log attribute group. The default value is 200.
The default configuration has the following SQL syntax:
*IF (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5737 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Forms Services Runtime') *OR (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5736 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Forms Services Runtime')
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_InfoPath_Session_State
Session state size exceeded the Form session state value.
Problem Description:
Form-filling sessions that exceed default value of form session state will terminate, and an error message is generated saying This session has exceeded the amount of allowable resources will be generated, and all form data entered during the session will be lost. The default value is 4096 kilobytes.
Possible Cause:
Session state size of the InfoPath Web form, which is loaded, exceeded the value of Form session state.
Advice:
This value is configurable and can be changed by the administrator. To resolve this issue, increase the session state size value. To do this, follow these steps:
- Login to SharePoint 3.0 Central Administration.
- Go to Configure InfoPath Forms Service in the InfoPath Forms Services section from Application Management tab.
- In the Form Session State section, change the value of form session state above the number of Session state size listed in message attribute of Event Log attribute group. The default value is 4096 KB.
Note: Form session state stores data necessary to maintain a user session.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 7083 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Forms Services Runtime - Session State'
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_Insufficient_DB_Permission
Insufficient SQL Server database permissions.
Problem Description:
Service account specified in Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010) has insufficient privileges in SharePoint database.
Possible Cause:
- During deployment insufficient privileges are granted in the SharePoint database to the service account specified in Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010).
Advice: - Ensure that service account, which is used by Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010), has sufficient permissions in the SharePoint database.
Note: Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010) uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name and password (domain name and password) or a predefined system account, such as Local System or Network Service.
The default configuration has the following SQL syntax:
*IF (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Windows SharePoint Services 3' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5214) *OR (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Microsoft-SharePoint Products-SharePoint Foundation' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5214)
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_Last_Query_Server_Removed
The last query server is removed from rotation.
Problem Description:
The last query server is removed from the load-balanced rotation. You cannot perform search queries until this issue is resolved.
Possible Cause:
- The last query server is removed from rotation.
- The system cannot find the file that is specified on the query server.
Advice: - Click Start > Settings > Control Panel. Double-click Administrative Tools and double-click Component Services.
- Click Component Services. Expand Computers and then My Computer.
- Expand DCOM Config folder and right-click SPSearch and ISS WAMREG Admin components. Click Properties. Click Security tab and adjust the properties.
- Grant local activation permission to the network service (the account on which SPS site runs).
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 10040
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_MSPS_ActiveQueueLength
A large number of documents are waiting to be processed.
Problem Description:
A large value for Active Queue Length could indicate an unusually large amount of network traffic or a heavy load on the server, and that the server is not able to keep up with the load of requests presented.
Possible cause:
- Server is temporarily heavily utilized, and the processing is lagging behind schedule, if Active Queue Length attribute value is greater than zero
- Large amount of network traffic
Advice: - Restart the MSPS 2003 Search service
- Go to Start > Programs > Administrative Tools > Services tool
- Restart Microsoft SharePointPS Search service
Note: This attribute indicates the number of documents that are waiting for a robot thread to process them. Normally, this number should be zero. If this number is not zero, it means that the server is falling behind, although this may be a temporary condition caused by an especially busy period. If this number is anything other than zero, then all available threads should be filtering.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SEARCH_GATHERER.Active_Queue_Length *GT 100
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_MSPS_RBT_SystemIOTraffic
Crawling has been paused because of high System IO traffic.
Problem Description:
Document crawling has been paused because of insufficient system resources.
Possible cause(s):
- Overloading of internal tasks such as crawling
- Overloading from end users
Advice: - Some of the crawling threads that are running in parallel can be scheduled to run later. To change the crawling schedules,
- Login to the portal site on which crawling activity is going on.
- Click on the Site settings option.
- Clink on Configure Search and Indexing link
- Click Manage content sources link
- Select the name of content source for which schedule should be changed
- Select Specify full update schedule on content source page
-
Edit the crawling Schedule
- Upgrade the system's resources.
Note: System IO traffic rate:
System IO traffic rate attribute detects the System I/O traffic using back-off logic.
High traffic rate means the server is overloaded with tasks either from the end users, or because of internal tasks like crawling, indexing. Crawling activity can take up a lot of system resources and may deprive the gatherer (crawling), thus causing it to halt.
The threshold of System I/O traffic that may send the gatherer service into a back-off also depends on the Search Gatherer/Performance level attribute. If the attribute is set to 1 or 2, the gatherer (crawling) may back off for lower levels of I/O traffic. This attribute can have a value between 1 and 5. The default value is 3. The following values of back-off attribute describe why the gatherer service went into back off state:
0 - up and running
1 - High system IO traffic
2 - High notifications rate
3 - Delayed recovery in progress (not implemented)
4 - Back off due to user activity
5 - Battery Low
6 - Memory Low
99 - Back off for some internal reason (forced by Search itself)
While backing off, no indexing is performed.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SEARCH_GATHERER.Reason_to_Back_Off *EQ 1
This situation is evaluated every 5 minutes.
This situation is available for distribution.
KQP_MSPS_Retries_Rate
The rate at which the document access has been retried is high.
Problem Description:
The rate at which the document access has been retried per second is high. The gatherer is attempting to access a document numerous times and is not successful.
Possible cause:
- The document extension is incorrect.
- The iFilter for the document type is not installed.
Advice: - Check the gatherer logs and identify the document.
- Check if the document extension is correct.
- Check if the correct iFilter is installed for the document type.
To check which iFilters are installed on the system, click Start > Settings > Control Panel. Double-click Add or Remove Programs. Check if the required iFilter is installed.
For example, if the gatherer logs show that the document ABC.pdf has a problem, then ensure that the PDF iFilter is properly installed on the crawling system.
Note: This situation is supported by MSPS 2003.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SEARCH_GATHERER_PROJECTS.Retries_Rate *GT 5
This situation is evaluated every 40 minutes.
This situation is available for distribution.
KQP_MSPS_Search_DocDelayRetry
SharePoint is unable to crawl the SharePoint contents.
Problem Description:
If Documents Delayed Retry attribute is greater than zero, it means that the local SharePoint server it is crawling is shut down.
Possible Cause:
MSPS 2003 fails to access the documents because the server, on which it is crawling the contents, is shut down.
Advice:
- To know the server which is shut down check the crawl logs
- Login to the portal site.
- Go to the Site setting.
- Under Search Settings and Indexed Content section, go to the Configure search and indexing.
- Under General Content Settings and Indexing Status section, go to View errors and warnings on row.
- Now check log files for crawling portal content and for non portal content to check which server is shut down.
- Check if the server is actually inaccessible, if yes then start the server
- If server is accessible, then check for network/authentication problem which is creating accessibility problems for the crawler.
Note: Normally, the value of Documents Delayed Retry should be zero.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SEARCH_GATHERER.Documents_Delayed_Retry *GT 0
This situation is evaluated every 10 minutes.
This situation is available for distribution.
KQP_MSPS_Search_Service_Down
Microsoft SharePointPS Search service is not running.
Problem Description:
The Microsoft SharePointPS Search service is not running.
Possible cause:
- Problem in Gatherer service
Advice: - Stop and Start the Microsoft SharePointPS Search service. Take Action Start SharePoint Portal Search service
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SharePointPSSearch *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_MS_SSO_Service_Down
The Microsoft Single Sign-on service is not running.
Problem Description:
The Microsoft Single Sign-on service is not running.
Possible cause:
- The Microsoft Single Sign-on service is not running.
Advice: - Start the Microsoft Single Sign-on service. Take Action. Start the Microsoft Single Sign-on service.
Note: This situation is supported by MSPS 2003 and MOSS 2007.
The default configuration has the following SQL syntax:
*IF (*SCAN KQP_AVAILABILITY.Name *EQ ssosrv *OR *SCAN KQP_AVAILABILITY.Name *EQ SSOSrv) *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 30 minutes.
This situation is available for distribution.
KQP_Membership_Import_Failed
The membership information cannot be imported.
Problem Description:
The membership information cannot be imported from the directory service.
Possible Cause:
- There are network connectivity issues between the directory server and the Microsoft Office SharePoint Server 2007 server farm.
- There are SQL Server computer connectivity issues between the directory server and the Microsoft Office SharePoint Server 2007 server farm.
- The directory server is not responding.
- The distribution list or membership information that was requested during the import was not found on the directory server.
Advice: - Verify the network connectivity between the directory server and the Microsoft Office SharePoint Server 2007 server farm.
- Verify the connectivity among the SQL Server, the directory server, and the Microsoft Office SharePoint Server 2007 server farm.
- Verify that the directory server is available and is accessible from the Microsoft Office SharePoint Server 2007 server farm.
- Attempt the membership import again at a later time.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5708
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_My_Site_Creation_Failure
My Site cannot be created.
Problem Description:
My Site cannot be created for the user that is specified in the exception message.
Possible Cause:
- The URL that is required to create the user's My Site is already being used by a different site.
- The user does not exist.
- There is a conflict with an existing user name.
- The user does not have adequate permissions to create My Site. There was a failure in applying the My Site Web template or the features associated with the template.
Advice:
Read the exception message in the Windows NT Event log and verify the following: - An existing My Site for the affected user does not exist. If a My Site for the affected user does exist and is not used, then delete the site. You can also navigate to the Personal Sites management page in the Shared Services Provider (SSP) administration site and change the site naming format to eliminate name conflicts.
- The user name exists in the directory server.
- A site does not already exist at the specified URL.
- The user has adequate permissions to create the My Site.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5187
This situation evaluates data as it becomes available.
This situation is automatically distributed to instances of this agent.
KQP_Office_Active_Queue_Length
Active Queue Length is greater than 100.
Problem Description:
A large value for Active Queue Length could indicate an unusually large amount of network traffic or a heavy load on the server, and that the server is not able to keep up with the load of requests presented.
Possible cause(s):
- Server is temporarily heavily utilized, and the processing is lagging behind schedule, if Active Queue Length attribute value is greater than zero.
- Large amount of network traffic.
Advice: - Restart the MOSS 2007 Office SharePoint Server Search service
- Go to Start > Programs > Administrative Tools > Services tool
- Restart Office SharePoint Server Search service
Note: Active Queue Length:
This attribute shows the number of documents waiting for robot threads. If this number is not 0, all threads should be filtering. When requests are received by MOSS 2007, those requests are not immediately processed, but are rather placed into a queue for processing. Normally, this queue should contain no more than a couple of items at that most. If the server is experiencing a heavy workload and is having trouble keeping pace with the demand, then the queue can become backed up. If this situation occurs frequently, it means the systems current resources are not coping with the usage of the server. In that case, it is recommended to upgrade systems resources
The default configuration has the following SQL syntax:
*IF *VALUE KQP_OFFICE_SEARCH_GATHERER.Active_Queue_Length *GT 100
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_Office_Doc_Delayed_Retry
Problems in accessing the Web storage system.
Problem Description:
If Documents Delayed Retry attribute is greater than zero, it means that the local server it is crawling is shut down. Normally, the value of this attribute is zero, but a non-zero value means that MOSS 2007 is having problems accessing the Web storage system.
Possible cause:
- MOSS 2007 fails to access the documents because the server, on which it is crawling the contents, is shut down.
Advice: - To know the server which is shut down check the crawl logs
- Login to Central Administration
- Click the Application Management tab
- Click on Create or configure this farm's shared services link
- Click on Shared Service Provider SSPName
- On Shared Service Provider admin page, click Search Settings
- Click Crawl logs
- Check if the server is actually inaccessible, if yes then start the server
- If server is accessible, then check for network/authentication problem which is creating accessibility problems for the crawler
- Make sure the credentials with which the SSP is running has appropriate permissions to crawl the server
Note: If the number continues to steadily rise, then it indicates a Web storage system failure.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_OFFICE_SEARCH_GATHERER.Documents_Delayed_Retry *GT 0
This situation is evaluated every 10 minutes.
This situation is available for distribution.
KQP_Office_Protocol_Handler
Protocol handler is not loaded.
Problem Description:
During crawling, protocol handler is not loaded.
Possible Cause:
A registry entry for protocol handler is incorrect.
Advice:
- Check which protocol handler is unable to load by looking at the message attribute of event log attribute group.
- If protocol handler is provided by Microsoft, repair the installation of MOSS 2007 to make a registry entry correct.
- If it is third party protocol handler, reinstall it.
Note: MOSS 2007 uses protocol handlers for accessing different content sources during crawling.
The default configuration has the following SQL syntax:
*IF (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office Server Search' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 2484 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Gatherer') *OR (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office Server Search' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 2483 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Gatherer')
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_Office_RTB_SystemIOTraffic
Crawling has been paused because of high System IO traffic.
Problem Description:
Gatherer (crawling) has been paused because of high System IO traffic
Possible cause(s):
- Heavy internal tasks such as crawling
- Overloading from end users
Advice: - Some of the crawling threads that are running in parallel can be scheduled to run later. To change the crawling schedules,
- Login to Central Administration
- Click on Application Management tab
- Click on Create or configure this farm's shared services link
- Click on the Shared Service Provider
- On the Shared Services Provider administration page, select Search settings under the Search group
- Select the Content sources and crawl schedules link on the Configure Crawl settings page
- Edit (STOP/PAUSE crawls that might be causing load on server) the crawl schedules on the Manage content sources page
- Upgrade the system's resources
Note: System IO traffic rate:
System IO traffic rate attribute detects the System I/O traffic using back-off logic.
High traffic rate means the server is overloaded with tasks either from the end users, or because of internal tasks like crawling,indexing. Crawling activity can take up a lot of system resources and may deprive the Gatherer (crawling), thus causing it to halt.
The threshold of System I/O traffic that may send the gatherer (crawling) into a back-off also depends on the Office Server Search Gatherer/Performance level attribute. If the attribute is 1 or 2, the gatherer service may back off for lower levels of I/O traffic. This attribute can have a value between 1 and 5. The default value is 3.
The following values of back-off attribute describe why the gatherer (crawling) went into back off state:
0 - up and running
1 - High system IO traffic
2 - High notifications rate
3 - Delayed recovery in progress (not implemented)
4 - Back off due to user activity
5 - Battery Low
6 - Memory Low
99 - Back off for some internal reason (forced by Search itself)
While backing off, no indexing is performed.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_OFFICE_SEARCH_GATHERER.Reason_to_Back_Off *EQ 1
This situation is evaluated every 5 minutes.
This situation is available for distribution.
KQP_Office_Retries_Rate
The rate at which the document access has been retried is high.
Problem Description:
The rate at which the document access has been retried per second is high. The gatherer is attempting to access a document numerous times and is not successful.
Possible cause:
- The document extension is incorrect.
- The iFilter for the document type is not installed.
Advice: - Check the gatherer logs and identify the document.
- Check if the document extension is correct.
- Check if the correct iFilter is installed for the document type.
To check which iFilters are installed on the system, click Start > Settings > Control Panel. Double-click Add or Remove Programs. Check if the required iFilter is installed.
For example, If the Gatherer logs show that the document ABC.pdf has problems, then ensure that the PDF iFilter is properly installed on the crawling system.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_OFFICE_SEARCH_GATHERER_PROJECTS.Retries_Rate *GT 5
This situation is evaluated every 40 minutes.
This situation is available for distribution.
KQP_Office_Search_Index_Size
The current size of index is increasing.
Problem Description:
The current size of index is increasing.
Possible cause:
- Indexing process is carrying out rapidly and more contents like SharePoint sites, Microsoft Exchange Server content, file shares, Lotus notes, and custom content are getting indexed
Advice: - If the SharePoint query or index server is running out of disk space, either increases the size of the hard drive volume or move the content index to another hard drive volume that has adequate space. How to move index to another drive of query server
- Run the command prompt
- Navigate to c:\program files\common files\Microsoft shared\Web server extensions\12\bin directory
- Type the following:
stsadm.exe -o osearch -propagationlocation directory
Where directory is the new location for the content index.
How to move index to another drive of Index server - Run the command prompt
- Navigate to c:\program files\common files\Microsoft shared\Web server extensions\12\bin directory
- Type the following:
stsadm.exe -o osearch -defaultindexlocation directory
Where directory is the new location for the content index.
Note: Use this attribute to predict how quickly the server may run out of hard disk space. The threshold value is machine specific and should be set accordingly for the machine space requirements.A smaller index increases Index Server performance.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_OFFICE_SEARCH_INDEXER_CATALOGS.Index_Size *GT 200
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_Office_Search_Service_Down
Office SharePoint Server Search service is not running.
Problem Description:
The Office SharePoint Server Search service is not running.
Possible cause:
- Missing configuration details of the Office Search Service Help Search service
Advice: - Start the Office SharePoint Server Search service. Take Action Start Office SharePoint Server Search Service
- Check the configuration of the Search service
- Login to Central Administration
- Click on Operations tab
- Click on Services on Server link
- Click on Office SharePoint Server Search service link
- Make sure the settings and credentials are valid for the Search service
- Start the Office SharePoint Server Search service as mentioned in point 1
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ OSearch *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_Profile_Import_Failed
An error was encountered while importing user profiles.
Problem Description:
An error was encountered while importing user profiles from the directory service.
Possible Cause:
- There is a network connectivity issue between the directory server and the Microsoft Office SharePoint Server 2007 server farm.
- There is a network connectivity issue among the SQL Server computer, the directory server, and the Microsoft Office SharePoint Server 2007 server farm.
- The directory server is not responding.
- The user profile that was requested during the import was not found on the directory server.
Advice: - Verify the network connectivity among the SQL Server, the directory server, and the Microsoft Office SharePoint Server 2007 server farm.
- Verify the connectivity among the SQL Server, the directory server, and the Microsoft Office SharePoint Server 2007 server farm.
- Verify that the directory server is available and is accessible from the Microsoft Office SharePoint Server 2007 server farm.
- Attempt to import the user profile again at a later time.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5707
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_SP2010_Admin_Service_Down
SharePoint 2010 Administration service is not running.
Problem Description:
The SharePoint 2010 Administration service is not running.
Advice:
Take Action Start SharePoint 2010 Administration service
Note:
- The SharePoint 2010 Administration service maintains the configuration of each server in a SharePoint 2010 deployment.
- The service runs on each server in the farm and is responsible for checking the configuration database to ensure that the local server is performing roles that are assigned to it.
- It can stop and start services that SharePoint 2010 needs, including Search. It can also add or delete catalogs and search applications.
- This service account should be a member of the Power Users group on all machines running SharePoint 2010.
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SPAdminV4 *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SP2010_Timer_Service_Down
SharePoint 2010 Timer service is not running.
Problem Description:
The SharePoint 2010 Timer Service is not running.
Advice:
Take Action Start SharePoint 2010 Timer Service
Note:
- The SharePoint 2010 Timer service sends notifications and performs scheduled tasks for SharePoint Foundation.
- The service account should be a member of the Power Users group on all machines that run SharePoint 2010.
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SPTimerV4 *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SPP_Admin_Service_Down
SPP Administration service is not running.
Problem Description:
The SharePoint Portal Administration Service is not running.
Advice:
Take Action Start SharePoint Portal Administration Service
Note:
- It maintains the configuration of each server in a SharePoint Portal Server deployment.
- It runs on each server in the farm and is responsible for checking the configuration database to ensure that the local server is performing its assigned roles.
- It can stop and start services that SharePoint Portal Server needs, including SPSSearch. It can also add or delete catalogs and can add or delete search applications as needed.
- This service account should be a member of the Power Users group on all machines running Portal Server.
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SPSAdmin *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SPP_Alert_Service_Down
SharePoint Portal Server Alert service is not running.
Problem Description:
The SharePoint Portal Alert Service is not running .
Advice:
Take Action Start SharePoint Portal Alert Service
Note:
- The purpose of the SharePoint Portal Alert service is to notify a user, when the user requests it, that there is a change to a designated item, document, list, or document library on the website. Alerts are managed by the job server.
- This service account should be a member of the Power Users group on all machines running Portal Server.
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ spsalert *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SPP_Timer_Service_Down
SharePoint Timer service is not running.
Problem Description:
The SharePoint Timer Service is not running.
Advice:
Take Action Start SharePoint Timer Service
Note:
- The SharePoint Timer sends notifications and performs scheduled tasks for Windows SharePoint Services.
- This service account should be a member of the Power Users group on all machines running Portal Server.
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SPTimer *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SP_Active_Queue_Length
A large number of documents are waiting to be processed.
Problem Description:
A large value for Active Queue Length could indicate an unusually large amount of network traffic or a heavy load on the server, and that the server is not able to keep up with the load of requests presented.
Possible cause(s):
- Server is temporarily heavily utilized, and the processing is lagging behind schedule, if Active Queue Length attribute value is greater than zero.
- Large amount of network traffic.
Advice: - Restart the MOSS 2007 Windows SharePoint Services Help Search service
- Go to Start > Programs > Administrative Tools > Services tool
- Restart Windows SharePoint Services Help Search service
Note: This attribute indicates the number of documents that are waiting for a robot thread to process them. Normally, this number should be zero. If this number is not zero, it means that the server is falling behind, although this may be a temporary condition caused by an especially busy period. If this number is anything other than zero, then all available threads should be filtering.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SP_SEARCH_GATHERER.Active_Queue_Length *GT 100
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SP_DB_Login_Failed
SharePoint database login failed.
Problem Description:
Login to SharePoint database failed.
Possible Cause(s):
- The user name or password for the service account was invalid before the session or became invalid during the session.
- The password for the service account changes.
- If the user name was changed in Internet Information Services (IIS) Manager or Service Control Manager after being configured for Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010).
Advice: - Use the Service Accounts page in Central Administration or the stadm.exe utility to verify that the correct user name and password are configured for the service account.
Note: The administrator configures specific user name and password or a predefined system account, such as Local System or Network Service, when Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010)is installed. Windows SharePoint Services (or SharePoint Foundation for SharePoint Server 2010) uses that account for communicating with the database. This is referred to as the service account that SharePoint runs as.
The default configuration has the following SQL syntax:
*IF (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Windows SharePoint Services 3' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 3351) *OR (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Microsoft-SharePoint Products-SharePoint Foundation' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 3351)
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_SP_Doc_Delayed_Retry
SharePoint is unable to crawl SharePoint contents.
Problem Description:
If Documents Delayed Retry attribute is greater than zero, it means that the local SharePoint server it is crawling is shut down.
Possible cause:
- MOSS 2007 fails to access the documents because the server, on which it is crawling the contents, is shut down.
Advice: - To know the server which is shut down check the crawl logs
- Login to Central Administration
- Click the Application Management tab.
- Click on Create or configure this farm's shared services link.
- Click on Shared Service Provider SSPName
- On Shared Service Provider admin page, click Search Settings.
- Click Crawl logs.
- Check if the server is actually inaccessible, if yes then start the server.
- If server is accessible, then check for network/authentication problem which is creating accessibility problems for the crawler.
- Make sure the credentials with which the SSP is running has appropriate permissions to crawl the server.
Note: Normally, the value of Documents Delayed Retry should be zero.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SP_SEARCH_GATHERER.Documents_Delayed_Retry *GT 0
This situation is evaluated every 10 minutes.
This situation is available for distribution.
KQP_SP_Publish_CacheHitRatio
Low value of Cache Hit Ratio leads to slow response to end user.
Problem Description:
Throughput and user response time degrades if publishing cache hit ratio is low.
Possible cause(s):
- The cache profile is same for the SharePoint site or SharePoint site collection or different pages of SharePoint site
- SharePoint website contents are frequently modified
Advice:- Apply different caching profiles to SharePoint site or SharePoint site collection or different pages of SharePoint site to optimize the caching behavior
Note: - Microsoft Office SharePoint Server 2007 ships with advanced caching capabilities to maximize the performance of the SharePoint Site. If used properly, it can improve the throughput and user response time significantly. Hit ratio over 90% and a low object discard rate indicates that the cache size is big enough.
- Different caching profiles can apply to each level to optimize the caching behavior. For example, the home page of a site may be accessed most often, and one can use a unique page layout for the home page so that it is possible to apply a special cache profile to that unique page layout and override the caching behavior of the entire site collection. The cache profile of the page layout may be configured with longer cache duration. This allows to trade off timeliness of data against performance only for the home page where it is possible to afford this trade-off. For the other pages in the system, use a different cache profile with a shorter cached duration.
-
Tune Object cache if size is too big, there is wastage of valuable memory for the other caches, such as the ASP.NET output cache, if used. Certain Web parts, such as the Content by Query Web part, store their XSLT style sheet in output cache. If the object cache size is set too big, ASP.NET may flush output cache memory to make room for it. CPU usage may increase after the flushing. This is particularly important for a system running on 32-bits OS because each worker process is limited to 2GB application memory space. If the object cache size limit is set too big, the IIS worker process (w3wp) may actually run out of memory.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SP_PUBLISHING_CACHE.Publishing_Cache_Hit_Ratio *GT 0 *AND *VALUE KQP_SP_PUBLISHING_CACHE.Publishing_Cache_Hit_Ratio *LT 80
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SP_RTB_SystemIOTraffic
Crawling has been paused because of high System IO traffic.
Problem Description:
Document crawling has been paused because of insufficient system resources.
Possible cause(s):
- Overloading of internal tasks such as crawling
- Overloading from end users
Advice: - Some of the crawling threads that are running in parallel can be scheduled to run later. To change the crawling schedules,
- Login to Central Administration
- Click on Application Management tab
- Click on Create or configure this farms shared services link
- Click on the Shared Service Provider
- On the Shared Services Provider administration page, select Search settings under the Search group
- Select the Content sources and crawl schedules link on the Configure Crawl settings page
- Edit (STOP/PAUSE crawls that might be causing load on server) the crawl schedules on the Manage content sources page
- Upgrade the system's resources
Note: System IO traffic rate:
System IO traffic rate attribute detects the System I/O traffic using back-off logic.
High traffic rate means the server is overloaded with tasks either from the end users, or because of internal tasks like crawling, indexing. Crawling activity can take up a lot of system resources and may deprive the gatherer (crawling), thus causing it to halt.
The threshold of System I/O traffic that may send the gatherer (crawling) into a back-off also depends on the SharePoint Search Gatherer/Performance level attribute. If the attribute is 1 or 2, the gatherer service may back off for lower levels of I/O traffic. This attribute can have a value between 1 and 5. The default value is 3.
The following values of back-off attribute describe why the gatherer service went into back off state:
0 - up and running
1 - High system IO traffic
2 - High notifications rate
3 - Delayed recovery in progress (not implemented)
4 - Back off due to user activity
5 - Battery Low
6 - Memory Low
99 - Back off for some internal reason (forced by Search itself)
While backing off, no indexing is performed.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SP_SEARCH_GATHERER.Reason_to_Back_Off *EQ 1
This situation is evaluated every 5 minutes.
This situation is available for distribution.
KQP_SP_Search_Index_Size
The current size of index is increasing.
Problem Description:
The current size of index is increasing.
Possible cause:
- Indexing process is carrying out rapidly and more contents are getting uploaded on SharePoint sites and getting indexed
Advice: - If the server (query or index) is running out of disk space, either increases the size of the hard drive volume or moves the content index to another hard drive volume that has adequate space. How to move index to another drive of query server.
- Run the command prompt
- Navigate to c:\program files\common files\Microsoft shared\Web server extensions\12\bin directory
- Type the following:
stsadm.exe -o osearch -propagationlocation directory
Where directory is the new location for the content index.
How to move index to another drive of Index server - Run the command prompt.
- Navigate to c:\program files\common files\Microsoft shared\Web server extensions\12\bin directory
- Type the following:
stsadm.exe -o osearch -defaultindexlocation directory
Where 'directory' is the new location for the content index.
Note: Use this attribute to predict how quickly the server may run out of hard disk space. The threshold value is machine specific and should be set accordingly for the machine space requirements.A smaller index increases Index Server performance
The default configuration has the following SQL syntax:
*IF *VALUE KQP_SP_SEARCH_INDEXER_CATALOGS.Index_Size *GT 200
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SP_Search_Service_Down
Windows SharePoint Services Help Search service is not running.
Problem Description:
The Windows SharePoint Services Help Search service is not running.
Possible cause:
- Missing configuration details of the Windows SharePoint Services Help Search service
Advice: - Start the Windows SharePoint Services Help Search service. Take Action Start Windows SharePoint Services Search Service
- Check the configuration of the Search service
- Login to Central Administration
- Click on Operations tab
- Click on Services on Server link
- Click on Windows SharePoint Services Help Search service link
- Make sure the settings and credentials are valid for the Search service
- Start the Windows SharePoint Services Help Search service as mentioned in point 1
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SPSearch *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 15 minutes.
This situation is available for distribution.
KQP_SSP_Admin_Site_Unavailable
The SSP administration site is not available.
Problem Description:
The administration site of the Shared Services Provider (SSP) is not available.
Possible Cause:
- The SSP was created, but creating the administration site for SSP failed.
- The SSP was restored, but restoring the administration site might have failed.
- A user has deleted the administration site, the content database, or the Web application for that site.
- The SQL Server computer that contains the SSP databases is unavailable.
Advice: - If you have a backup of the administration site for the SSP, then restore it.
- If you do not have a backup of the administration site or you do not want to restore it, then you can use the stsadm.exe command line tool to create a new SSP administration site and attach the new site to the SSP.
- Ensure that the SQL Server that contains the databases for the SSP is available.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5290
This situation evaluates data as it becomes available.
This situation is automatically distributed to instances of this agent.
KQP_SSP_DB_Sync_Failed
The SSP synchronization with the configuration database failed.
Problem Description:
The Shared Services Provider (SSP) failed to synchronize the information with the configuration database.
Possible Cause:
- The service accounts that are used to access the computer on which the SQL Server is running have changed since the server farm was deployed. Because of this, the SSP service cannot write to the configuration database.
- There are network connectivity issues between the computer on which the SQL Server is running and the other servers in the farm.
- An individual service within the SSP cannot synchronize its properties with the configuration database.
Advice: - Verify that the Windows SharePoint Services Timer (SPTimerV3) service is running.
- Verify the network connectivity between the computer on which the SQL Server is running and the other servers in the farm.
- Ensure that the computer on which the SQL server is running is started.
- Verify that the service accounts that access the databases are correct.
- If the problem persists, then check the exception in the Windows NT Event log for details about the error and resolve the problem accordingly.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5783
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_SSP_Provisioning_Failed
The Shared Services Provider (SSP) creation failed.
Problem Description:
The Shared Services Provider (SSP) creation failed.
Possible Cause:
- There are network connectivity issues between the computer on which the SQL Server is running and the other servers in the farm.
- An individual service within the SSP failed to start.
Advice: - Verify that the computer on which the SQL Server is running is configured correctly and is accessible from the servers in the farm.
- Verify that the Windows SharePoint Services Timer (SPTimerV3) service is running on the servers in the farm.
- If the problem persists, then see the exception in the Windows NT Event log for details about the error and resolve the problem accordingly.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5162
This situation evaluates data as it becomes available.
This situation is automatically distributed to instances of this agent.
KQP_Sync_Job_Scheduler_Failed
The synchronization job scheduler failed.
Problem Description:
A failure occurred while an administrator was creating and scheduling a profile synchronization timer job for sweep sync and site sync of the Web applications.
Possible Cause:
- There is a network failure between the computer on which the SQL Server is running and the other servers in the farm.
- The profile synchronization timer job has insufficient permissions to access the content database.
- A timeout occurred while the profile synchronization timer job was communicating with the SQL Server.
Advice:
See the Windows NT Event log for details about the cause of occurrence of the error and then perform the following steps: - Verify that the service account for the profile synchronization timer job has adequate permissions to access the content database that is specified in the event log.
- Verify the network connectivity between the computer on which the SQL Server is running and the other servers in the farm.
- Resolve any issues that might cause the SQL Server to timeout.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5556
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_User_Profile_Commit_Failed
A user profile is not saved to the SSP database.
Problem Description:
A user profile is not saved to the Shared Services Provider (SSP) database.
Possible Cause:
- There is an SQL Server failure, such as a timeout or connection failure.
- There is a concurrency failure, such as two users are trying to create the same profile at the same time.
Advice: - Verify the connectivity between the computer on which the SQL Server is running and the other servers in the farm.
- If this is a recurring error, then contact the Microsoft technical support.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5188
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_User_Profile_Sync_Failed
The user profile synchronization failed.
Problem Description:
The user profile synchronization failed for new active users on the content database.
Possible Cause:
- There is a network failure between the computer on which the SQL Server is running and the other servers in the farm.
- The profile synchronization timer job that is used for synchronization, has insufficient permissions to access the content database.
- A timeout occurred while the timer job was communicating with the SQL Server.
Advice:
See the Windows NT Event log for details about the cause of occurrence of this error and then perform the following steps: - Verify that the service account for the profile synchronization timer job has adequate permissions to access the content database that is specified in the Windows NT Event log.
- Verify the network connectivity between the computer on which the SQL Server is running and the other servers in the farm.
- Resolve any issues that might cause the SQL Server to timeout.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *VALUE KQP_EVENT_LOG.Event_Source *EQ 'Office SharePoint Server' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 5554
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_WSS_Protocol_Handler
Protocol handler is not loaded.
Problem Description:
During crawling, protocol handler is not loaded.
Possible Cause:
A registry entry for protocol handler is incorrect.
Advice:
- Check which protocol handler is unable to load by looking at the message attribute of event log attribute group.
- If protocol handler is provided by Microsoft, repair the installation of MOSS 2007 to make a registry entry correct.
- If it is third party protocol handler, reinstall it.
Note: MOSS 2007 uses protocol handlers for accessing different content sources during crawling.
The default configuration has the following SQL syntax:
*IF (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Windows SharePoint Services 3 Search' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 2483 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Gatherer') *OR (*VALUE KQP_EVENT_LOG.Event_Source *EQ 'Windows SharePoint Services 3 Search' *AND *VALUE KQP_EVENT_LOG.Event_ID *EQ 2484 *AND *VALUE KQP_EVENT_LOG.Event_Category *EQ 'Gatherer')
This situation evaluates data as it becomes available.
This situation is available for distribution.
KQP_WSS_Tracing_Service_Down
The Windows SharePoint Services Tracing service is not running.
Problem Description:
The Windows SharePoint Services Tracing service is not running.
Possible cause:
- The Windows SharePoint Services Tracing service is not running.
Advice: - Start the Windows SharePoint Services Tracing service. Take Action. Start the Windows SharePoint Services Tracing service.
Note: This situation is supported by MOSS 2007.
The default configuration has the following SQL syntax:
*IF *SCAN KQP_AVAILABILITY.Name *EQ SPTrace *AND *VALUE KQP_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 30 minutes.
This situation is available for distribution.
Related topics:
Organization of the predefined workspaces