在 SharePoint 伺服器知識庫文章中搜尋Search in SharePoint Server knowledge articles

了解如何解決 Systems Center Operations Manager (SCOM) 的 SharePoint Server 2016 和 SharePoint 2013 管理組件中關於搜尋索引、內容處理、查詢處理和其他搜尋問題的警示。Learn how to resolve alerts about the search index, content processing, query processing, and other search issues in the SharePoint Server 2016 and SharePoint 2013 management pack for Systems Center Operations Manager (SCOM).

本節中的文章為 SharePoint Server 中搜尋服務的相關知識庫文章。通常您在 Operations Manager 主控台中按一下警示內的連結時,就會顯示這些文章。這些文章可用於協助您針對搜尋進行疑難排解並解決問題。請下載並安裝適用於 SharePoint Server 2016 的 System Center 監視組件適用於 SharePoint Server 的 System Center 監視組件,或適用於 SharePoint Foundation 的 System Center 監視組件The articles in this section are knowledge articles for search services in SharePoint Server. Typically, these articles appear when you click a link in an alert in the Operations Manager console. You can use these articles to help you troubleshoot and resolve problems in search. Download and install System Center Monitoring Pack for SharePoint Server 2016, System Center Monitoring Pack for SharePoint Server, or System Center Monitoring Pack for SharePoint Foundation.

分析:無法啟動 - 搜尋分析Analytics analysis: failed to start - search analytics

警示名稱: 分析:無法啟動 - 搜尋分析Alert Name: Analytics analysis: failed to start - search analytics

摘要: 計時器工作會在預先設定的時間間隔 (每 24 小時一次) 嘗試啟動執行搜尋分析。當計時器工作無法啟動分析時,就會觸發此警示。Summary: At a preconfigured time interval (once every 24 hours) the timer job will try to start a run of the search analytics analysis. This alert is triggered when the timer job fails to start the analysis.

有數個問題均會阻止分析啟動。若計時器工作無法啟動分析,則計時器工作會停止並稍後再重試 (10 分鐘內)。Multiple problems can prevent the analysis from being started. If the timer job fails to start the analysis, the timer job will stop and retry later (in 10 minutes).

原因Cause

  • 無法使用分析處理元件。Analytics processing component is not available.

  • 網路中斷。Network outage.

  • 伺服器問題。Server issues.

  • 無法使用分析設定資料庫。Analysis configuration database not available.

解決方案Resolution

請確保下列區域可正常運作:Make sure these areas are functioning:

  • 分析處理元件可正常運作。The analytics processing component is functioning properly.

  • 沒有網路問題。There are no networking issues.

  • 沒有伺服器問題。There are no server issues.

  • 可以使用分析報表資料庫。The analysis reporting database is available.

分析:無法啟動警告 - 搜尋分析Analytics analysis: failed to start warning - search analytics

警示名稱: 分析:無法啟動警告 - 搜尋分析Alert Name: Analytics analysis: failed to start warning - search analytics

摘要: 當搜尋分析還在執行時,如果計時器工作嘗試對相同分析啟動新的執行,此新的啟動就必須延遲。一旦計時器工作偵測到執行的分析已經停止,系統便會嘗試重新啟動該搜尋分析。Summary: If a search analytics analysis is still running when the timer job is trying to start a new run of the same analysis, this new start has to be postponed. The system with try to restart the search analytics analysis as soon as the timer job detects that the running analysis has stopped.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 尚未完成上一個分析執行。Previous analysis run has not completed.

  • 伺服器或網路負載過重導致較長的分析執行時間。Heavy load on servers or network leads to longer analysis run time.

解決方案Resolution

請確保下列區域可正常運作:Make sure these areas are functioning:

  • 目前執行的分析已有進度。若沒有,請調查為何沒有進度。可能是網路或伺服器問題。請加以解決。確保可使用所有資料庫 (連結資料庫、分析報表資料庫等)。Current running analysis does have progress. If not, investigate why there is no progress. There might be a networking or server issue. Resolve these. Do make sure that all databases are available (Link database, analytics reporting database, etc.).

  • 若執行沒有任何進度,您可能必須執行手動停止分析。You might have to perform a manual stop of the analysis if it is running without any progress.

內容處理:未載入遞補文字分隔Content Processing: Fallback word breaker did not load

警示名稱: 內容處理:未載入遞補文字分隔Alert Name: Content Processing: Fallback word breaker did not load

摘要: 文字分隔服務無法為所指定的文字分隔語言載入遞補文字分隔。Summary: The word breaker service could not load the fallback word breaker for the indicated word breaker language.

原因Cause

安裝錯誤或其他暫時性錯誤,可透過重新啟動內容處理元件或伺服器重新開機來解決。在內部部署設定中,可能也代表因為變更文字分隔設定所造成的錯誤。Installation error or another transient error that might be resolved by a content processing component restart or rebooting the server In an on-premises setting, it could also indicate an error caused by changing the word breaker configuration.

解決方案Resolution

重新啟動內容處理元件或重新啟動伺服器。若曾嘗試斷詞工具自訂,記錄檔可能會啟發更多資訊以指出原因和解決方案。Restart the content processing component or restart the server. component. If a word breaker customization was tried, the logs could suggest more information to indicate a cause and resolution.

內容處理:查詢分類字典超過大小限制Content Processing: Query classification dictionary exceeds size limit

警示名稱: 內容處理:查詢分類字典超過大小限制Alert Name: Content Processing: Query classification dictionary exceeds size limit

摘要: 字典太大,超出了大小限制。在字典再次成功編譯之前,仍會使用目前的字典,而不會進行任何字典更新。系統將重新嘗試直到字典再次編譯。但可能需要從字詞庫減少資料。Summary: The dictionary has grown too large and is exceeding the size limit. The current dictionary will still be used and no dictionary updates will occur until dictionary compilation succeeds again. The system will retry until the dictionary compiles again. But a reduction in data from the Term Store may be required.

原因Cause

查詢分類規則使用的字典增加過大,且已超過大小限制。The dictionary used for query classification rules has grown too large and is now exceeding the size limit.

解決方案Resolution

檢查查詢分類規則使用的字詞組。可能需要減少項目以使字典再次編譯。重複重新嘗試可能會在內容處理元件上造成額外的高負載。Check the term sets used for query classification rules. Entries may need reducing to make the dictionary compile again. The recurring retries may otherwise create a high load on the content processing component.

內容處理:拼字字典超過大小限制Content Processing: Spelling dictionary exceeds size limit

警示名稱: 內容處理:拼字字典超過大小限制Alert Name: Content Processing: Spelling dictionary exceeds size limit

摘要: 查詢拼字校正字典太大,超出了大小限制。在字典再次成功編譯之前,仍會使用目前的字典,而不會進行任何字典更新。系統將重新嘗試直到字典再次編譯。但可能需要減少搜尋索引中的資料,或重新設定查詢拼字元件。Summary: The query spelling correction dictionary has grown too large and is now exceeding the size limit. The current dictionary will still be used and no dictionary updates will occur until dictionary compilation succeeds again. The system will retry until the dictionary compiles again. But a reduction in data in the search index or a reconfiguration of the query spelling components may be required.

原因Cause

動態查詢拼字校正字典太大,超出了大小限制。The dynamic query spelling correction dictionary has grown too large and is exceeding the size limit.

解決方案Resolution

檢查索引大小。此錯誤指出索引太大,可能很快就需要分割。此外,請考慮使用 Set-SPEnterpriseSearchQuerySpellingCorrection Cmdlet 降低每個組織允許的字典字詞數。重複重新嘗試可能會在內容處理元件上造成額外的高負載。Check the size of the index. This error indicates that the index is very large and might need splitting soon. Also, consider lowering the number of dictionary terms allowed per organization by using the cmdlet Set-SPEnterpriseSearchQuerySpellingCorrection. The recurring retries may otherwise create a high load on the content processing component.

內容處理:搜尋自訂字典更新Content Processing: Search Custom Dictionaries Update

警示名稱: 內容處理:搜尋自訂字典更新Alert Name: Content Processing: Search Custom Dictionaries Update

摘要: 計時器工作「搜尋自訂字典更新」失敗。Summary: The timer job "Search Custom Dictionaries Update" fails.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • Search Service 應用程式或字詞庫已暫停或無法使用。The Search service application or the term store is paused or not available.

  • 部署自訂實體擷取字典或建立連線時發生錯誤。An error occurred during the deployment of the custom entity extraction dictionary or while establishing a connection.

解決方案Resolution

  • 檢查 Search Service 應用程式及字詞庫的狀態,並視需要重新啟動。Check the status of the Search service application and the term store, restart if it is necessary.

  • 檢查是否部署自訂實體擷取字典,並確認連線未中斷。Check whether the custom entity extraction dictionary is deployed, and make sure that connection is present.

  • 視需要重新啟動計時器工作。Restart timer job if necessary.

內容處理:拼字字典更新Content Processing: Spelling Dictionary Update

警示名稱; 內容處理:拼字字典更新Alert Name: Content Processing: Spelling Dictionary Update

摘要: 計時器工作「拼字字典更新」失敗。Summary: The timer job "Spelling Dictionary Update" fails.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • Search Service 應用程式或字詞庫已暫停或無法使用。The Search service application or the term store is paused or not available.

  • 部署或建立連線期間發生錯誤。An error occurs during deployment or connection establishment.

解決方案Resolution

  • 檢查 Search Service 應用程式及字詞庫的狀態,並視需要重新啟動。Check the status of the Search service application and the term store, restart if it is necessary.

  • 確認連線未中斷。Make sure that connection is present.

  • 視需要重新啟動計時器工作。Restart timer job if it is necessary.

內容處理:收集程式內容處理連接器Content Processing: Gatherer Content Processing connector

警示名稱: 內容處理:收集程式內容處理連接器Alert Name: Content Processing: Gatherer Content Processing connector

摘要: 編目程式無法連線至內容處理。Summary: The crawler could not connect to content processing.

原因Cause

這可能是因為間歇網路連線中斷所造成,或是無法使用內容處理元件。This may be caused by intermittent loss of network connectivity, or the content processing component is not available.

解決方案Resolution

如果問題仍然存在,請檢查編目程式和內容處理之間的網路連線。此外,也請檢查內容處理元件,並視需要重新啟動。If the problem persists, check network connectivity between the crawler and content Processing. Also, check the content processing component, and restart if it is necessary.

內容處理:無法啟動流程Content Processing: flow failed to start

警示名稱: 內容處理:無法啟動流程Alert Name: Content Processing: flow failed to start

摘要: 沒有如預期啟動指定的處理流程。Summary: The indicated processing flow is not started as expected.

原因Cause

所需的服務不存在,或搜尋索引可能無法使用。The required services are not present, or the search index may be unavailable.

解決方案Resolution

檢查所需的搜尋元件和資料庫是否執行,並視需要重新啟動。Check that the required search components and databases are running and restart these if necessary.

內容處理:查詢分類字典接近大小限制Content Processing: Query classification dictionary close to size limit

警示名稱: 內容處理:查詢分類字典接近大小限制Alert Name: Content Processing: Query classification dictionary close to size limit

摘要: 字典已增加至接近其大小限制 (位於或超過其大小限制的 80%)Summary: The dictionary has grown close to its size limit (at or beyond 80 percent of its size limit).

原因Cause

對應字典中針對跨所有組織的查詢分類規則,所使用的字詞數已增加至接近限制。The number of terms in the corresponding dictionary used for query classification rules across all organizations is growing towards the limit.

解決方案Resolution

檢查查詢分類使用的字詞組。Check the term sets used for query classification.

內容處理:拼字字典接近大小限制Content Processing: Spelling dictionary close to size limit

警示名稱: 內容處理:拼字字典接近大小限制Alert Name: Content Processing: Spelling dictionary close to size limit

摘要: 查詢拼字校正字典已增加至接近其大小限制 (剛好或超過其大小限制的 80%)。Summary: The query spelling correction dictionary has grown close to its size limit (at or beyond 80 percent of its size limit).

原因Cause

與跨所有組織的動態查詢拼字校正字典相關的字詞數已增加至接近限制。The number of terms relevant for the dynamic query spelling correction dictionary across all organizations is growing towards the limit.

解決方案Resolution

檢查索引文件數。若索引文件數接近系統的限制,就可以忽略此警告。Check the number of indexed documents. If the number of indexed documents is close to the system's limit, this warning can be discarded.

編目程式:無法使用搜尋收集程式主機Crawler: Search Gatherer Host Unavailable

警示名稱: 編目程式:無法使用搜尋收集程式主機Alert Name: Crawler: Search Gatherer Host Unavailable

摘要: 為了進行搜尋編目,包含編目元件的伺服器會與內容伺服器通訊,以擷取編目的項目。編目伺服器與內容伺服器之間的網路通訊問題會阻擋此編目。當 SharePoint 從特定內容伺服器編目內容時,若網路通訊問題存在,SharePoint 就可能會顯示下列徵狀:Summary: As part of a search crawl, the servers that contain the crawl components communicate with content servers to retrieve the items for the crawl. Network communication problems between crawl server and content server will block this crawl. When SharePoint is crawling content from a specific content server and network communication problems exist, SharePoint might display the following symptoms:

  • 特定內容伺服器的編目不繼續進行,且似乎停滯不前。The crawl of the specific content server does not progress and seems to stall.

  • 編目記錄檔不會顯示特定內容伺服器的任何新編目文件。The crawl logs show no new crawled documents for the specific content server.

原因Cause

網路問題可能會導致無法通訊。請檢查內容伺服器是否在線上,且可連線至主控編目元件的伺服器。Network issues might be preventing the communication. Check that the content server is online and can connect to the server that hosts the crawl component.

解決方案Resolution

檢查內容伺服器的狀態。若內容伺服器在線上且提供內容給編目帳戶,則請檢查網路連線。Check the status of the content server. If the content server is online and serves content to the crawl account, check for network connection issues.

DocParsing:沒有更多剖析器伺服器工作者DocParsing: No More Parser Server Workers

警示名稱: DocParsing:沒有更多剖析器伺服器工作者Alert Name: DocParsing: No More Parser Server Workers

摘要: 無法重新啟動所有剖析伺服器工作者。因此集區沒有更多可供使用的工作者。此時僅有未設定為在沙箱中執行的格式處理常式可以運行。Summary: All parser server workers cannot restart. Therefore the pool has no more workers available. At this point, only format handlers that are not configured to run in a sandbox can run.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 剖析器伺服器與內容處理元件之間的管道中斷。Broken pipe between the parser server and the content processing component.

  • 過多的資源使用量導致取得資源逾時。Excessive resource usage causing a time-out to obtain resources.

  • 任何所需目錄的使用權限失敗。Permission failure to any of the required directories.

  • 剖析器處理或要寫入之暫存目錄的目錄權限外部變更。External change in directory permission of either the parser process or the temporary directory that it writes to.

  • 找不到設定檔或設定檔毀損。Misplaced or corrupted configuration file.

解決方案Resolution

  • 檢查 CPU 及內容處理元件的記憶體使用量。Check CPU and memory usage of the content processing component.

  • 檢查 parserserver.exe 的適當權限及相關資料夾。Check appropriate permissions to parserserver.exe and the related directories.

  • 檢查設定檔案。Check the configuration file.

DocParsing:無法重新啟動剖析器伺服器工作者DocParsing: Parser Server Worker Failed to Restart

警示名稱: DocParsing:無法重新啟動剖析器伺服器工作者Alert Name: DocParsing: Parser Server Worker Failed to Restart

摘要: 無法重新啟動剖析器伺服器工作者。因此會將其從集區移除。集區仍然有指定的可用工作者數。無法重新啟動剖析器伺服器集區裡的工作者時便會發生此情況。此時集區中的可用工作者數會減少,使輸送量降低。Summary: A parser server worker cannot restart. Therefore it is being removed from the pool. The pool still has the indicated number of workers available. This occurs when a worker inside the parser server pool could not restart. When this happens, the number of available workers in the pool is decreased, which reduces throughput.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 剖析器伺服器與內容處理元件之間的管道中斷Broken pipe between the parser server and the content processing component

  • 過多的資源使用量導致取得資源逾時。Excessive resource usage causing a time-out to obtain resources.

  • 任何所需目錄的使用權限失敗;Permission failure to any of the required directories;

  • 剖析器處理或要寫入之暫存目錄的目錄權限外部變更。External change in directory permission of either the parser process or the temporary directory that it writes to.

  • 找不到設定檔或設定檔毀損。Misplaced or corrupted configuration file.

解決方案Resolution

  • 檢查 CPU 及內容處理元件的記憶體使用量。Check CPU and memory usage of the content processing component.

  • 檢查 parserserver.exe 的適當權限及相關資料夾。Check appropriate permissions to parserserver.exe and the related directories.

  • 檢查設定檔案。Check the configuration file.

索引:遺失索引產生Index: Lost Generations

警示名稱: 索引:遺失索引產生Alert Name: Index: Lost Generations

摘要: 認可為已編製索引的資料已永久遺失。指定的索引系統上與指定的索引產生之間已永久遺失文件。Summary: Data acknowledged as indexed is permanently lost. Potentially lost documents on the index system indicated, between the given generations.

原因Cause

這可能是因為失敗數超過容錯量。This may be caused by the amount failures exceeding the fault-tolerance.

解決方案Resolution

可能需要完整重新編目。A full re-crawl may be required.

索引:遺失分割區Index: Missing partition

警示名稱: 索引:遺失分割區Alert Name: Index: Missing partition

摘要: 由於指定的索引系統上有一或多個遺失的分割區導致不完整的結果集。若仍然無法使用相關搜尋元件,就可能需要重新傳送資訊。換言之即為持續失敗無法使用。Summary: Incomplete result set because of one or more missing partitions on the indicated index system. This may require resending of information if the related search components remain unavailable. That is, it continues to fail.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 在查詢處理元件上遺失索引元件的插入。Missing injection from index component on the query processing component.

  • 網路連線中斷。Lost network connectivity.

  • 索引元件失敗。Index component fails.

解決方案Resolution

  • 將自動重新啟動查閱服務。Lookup Service will restart automatically.

  • 檢查索引元件。Check index component.

  • 檢查通訊問題。Check communication issues.

索引:索引封鎖Index: Indexing Blocked

警示名稱: 索引:索引封鎖Alert Name: Index: Indexing Blocked

摘要: 資訊流程從內容處理器到索引遭到封鎖;等待檢查點中 (指定的時間)。此為限制的索引速度;索引查詢已滿且持續超過預期時間。Summary: Information flow from content processor to index is blocked; waiting for a checkpoint (time indicated). This is limiting index speed; indexing queues remain full for longer than expected.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 索引器沒有收到足夠的資源。Indexer not receiving enough resources.

  • 資訊傳入過快。Information coming in too quickly.

解決方案Resolution

調查索引元件上的資源使用狀況,並盡可能調整搜尋拓撲以降低饋送率。Investigate resource usage on the index component, and possibly adjust the search topology to lower the feeding rate.

索引:日誌 IO 例外狀況讀取Index: Journal IO Exception Read

警示名稱: 索引:日誌 IO 例外狀況讀取Alert Name: Index: Journal IO Exception Read

摘要: 無法讀取日誌檔案。這表示有潛在問題存在於復原或複寫中。索引編製停止。Summary: Unable to read Journal file. This indicates a potential problem with recovery or replication. Indexing is stopped.

原因Cause

日誌檔案儲存在磁碟上,索引器的外部原因可能為:Journal file is stored on disk, external cause to indexer may be:

  • 鎖定檔案。Lock on file.

  • 檔案變更。Changes to file.

  • 實體磁碟問題。Physical disk problem.

解決方案Resolution

  • 釋放鎖定檔案。Release lock on file.

  • 恢復變更。Revert changes.

  • 修復磁碟。Fix disk.

此問題可能需要刪除日誌,然後重新饋送。This issue may require deleting the Journal and refeeding.

索引:日誌 IO 例外狀況寫入Index: Journal IO Exception Write

警示名稱: 索引:日誌 IO 例外狀況寫入Alert Name: Index: Journal IO Exception Write

摘要: 無法寫入日誌檔案。這表示有潛在問題存在於復原或複寫中。索引編製停止。Summary: Unable to write to Journal file. This indicates a potential problem with recovery or replication. Indexing is stopped.

原因Cause

日誌檔案儲存在磁碟上。索引器的外部原因可能為:Journal file is stored on disk. External cause to indexer may be:

  • 鎖定檔案。Lock on file.

  • 檔案變更。Changes to file.

  • 實體磁碟問題。Physical disk problems.

解決方案Resolution

  • 釋放鎖定檔案。Release lock on file.

  • 恢復變更。Revert changes.

  • 修復磁碟。Fix disk.

此問題可能需要刪除日誌,然後重新饋送。This issue may require deleting the Journal and refeeding.

索引查閱:結構描述服務可用性查詢處理Index Lookup: Schema service availability query processing

警示名稱: 索引查閱:結構描述服務可用性查詢處理Alert Name: Index Lookup: Schema service availability query processing

摘要: 因為無法使用結構描述服務,所以索引查閱無法運作。Summary: Index lookup could not work because the schema service was not available.

原因Cause

索引或資料庫無法使用,或是兩者皆無法使用。The indexer or the database, or both are unavailable.

解決方案Resolution

檢查結構描述服務或 OM,並視需要重新啟動。Check, and restart, the Schema service or OM, if it is necessary.

索引查閱:遺失分割區Index Lookup: Missing partition

警示名稱: 索引查閱:遺失分割區Alert Name: Index Lookup: Missing partition

摘要: 指定的索引系統上遺失一或多個分割區。這表示至少有一個內容處理元件沒有與一個主要索引元件連線。因此系統無法為此特定的連線進行饋送。Summary: One or more partitions are missing on the index system indicated. This means that at least one content processing component has no connection to one primary index component. Therefore the system cannot feed for that particular connection.

原因Cause

可能的原因如下:Possible causes include the following:

  • 索引元件沒有運作。Index component down.

  • 在內容處理元件上遺失索引元件的插入。Missing injection from index component on the content processing component.

  • 網路連線中斷。Lost network connectivity.

解決方案Resolution

服務將自動重新啟動;檢查索引元件;檢查通訊問題,視需要重新啟動。The service will restart automatically; check index component; check communication issues, restart if it is necessary.

查詢處理:查詢分類字典更新Query Processing: Query classification dictionary update

警示名稱: 查詢處理:查詢分類字典更新Alert Name: Query Processing: Query classification dictionary update

摘要: 計時器工作查詢分類字典失敗。Summary: The timer job Query Classification Dictionary fails.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • Search Service 應用程式已暫停或無法使用。The Search service application is paused or not available.

  • 部署或建立連線期間發生錯誤。An error occurred during deployment or connection establishment.

解決方案Resolution

  • 檢查 Search Service 應用程式的狀態,並視需要重新啟動。Check the status of the Search service application, and restart if it is necessary.

  • 確認連線未中斷。Make sure that connection is present.

  • 視需要重新啟動計時器工作。Restart timer job if it is necessary.

查詢處理:Search Service 應用程式可用性Query Processing: Search Service Application Availability

警示名稱: 查詢處理:Search Service 應用程式可用性Alert Name: Query Processing: Search Service Application Availability

摘要: 因為無法使用具有指定 ID 的 Search Service 應用程式,所以查詢剖析無法運作。Search Service 應用程式已關閉。所以服務中斷。Summary: Query parsing could not work because the Search service application with the indicated ID is not available. The Search service application is down. Therefore service is interrupted.

原因Cause

無法使用 Search Service 應用程式。The Search service application is not available.

解決方案Resolution

檢查 Search Service 應用程式並視需要重新啟動。Check, and restart, the Search service application if it is necessary.

查詢處理:元件可用性 - 查詢處理Query Processing: Component Availability - Query Processing

警示名稱: 查詢處理:元件可用性 - 查詢處理Alert Name: Query Processing: Component Availability - Query Processing

摘要: 查詢處理元件已停止且無法使用。Summary: The query processing component is stopped and is unavailable.

原因Cause

查詢處理元件在預期或意外的情況下停止。The query processing component is stopped under either expected or unexpected conditions.

解決方案Resolution

如果問題仍然存在,表示此為系統問題。請檢查查詢處理元件並視需要重新啟動。If the issue persists, this indicates system issues. Check and restart the query processing component, if it is necessary.

查詢處理:無法啟動流程Query processing: flow failed to start

警示名稱: 查詢處理:無法啟動流程Alert Name: Query processing: flow failed to start

摘要: 沒有如預期啟動指定的處理流程。Summary: The indicated processing flow is not started as expected.

原因Cause

所需的服務不存在,或索引可能無法使用。The required services are not present, or the index may be unavailable.

解決方案Resolution

檢查所需的搜尋元件和資料庫是否執行,並視需要重新啟動。Check that the required search components and databases are running and restart these if necessary.

查詢處理:未載入遞補文字分隔Query Processing: Fallback word breaker did not load

警示名稱: 查詢處理:未載入遞補文字分隔Alert Name: Query Processing: Fallback word breaker did not load

摘要: 文字分隔服務無法為所指定的文字分隔語言載入遞補文字分隔。Summary: The word breaker service could not load the fallback word breaker, for the indicated word breaker language.

原因Cause

安裝錯誤或其他暫時性錯誤,可透過重新啟動元件或伺服器重新開機來解決。在內部部署設定中,可能也代表因為變更文字分隔設定所造成的錯誤。Installation error or another transient error that might be resolved by a component restart or rebooting the server. In an on-premises setting, it could also indicate an error caused by changing the word breaker configuration.

解決方案Resolution

重新啟動查詢處理元件或伺服器。若曾嘗試斷詞工具自訂,記錄檔可能會啟發更多資訊以指出原因和解決方案。Restart the query processing component or restart the server. If a word breaker customization was tried, the logs could suggest more information to indicate a cause and resolution.

查詢處理:查詢元件取得設定Query Processing: Query Component Get Configuration

警示名稱: 查詢處理:查詢元件取得設定Alert Name: Query Processing: Query Component Get Configuration

摘要: 無法取得查詢處理元件的設定。所以無法啟動查詢服務,目前也沒有運作。Summary: Unable to get the configuration for query processing component. So, the query service cannot start and is currently not working.

原因Cause

設定毀損或遺失。Corrupt or missing configuration.

解決方案Resolution

檢查查詢處理元件的設定。Check settings for the query processing component.

查詢處理:查詢正規化結構描述服務可用性Query Processing: Query Normalization Schema Service Availability

警示名稱: 查詢處理:查詢正規化結構描述服務可用性Alert Name: Query Processing: Query Normalization Schema Service Availability

摘要: 因為無法使用結構描述服務,所以無法運作特定查詢的查詢正規化。特定查詢的查詢處理失敗。Summary: Query normalization could not work for the particular query because the schema service was not available. Query processing fails for particular queries.

原因Cause

無法使用索引器,或搜尋管理資料庫關閉,或兩者皆是。The indexer is unavailable, or the search administration database is down, or both.

解決方案Resolution

檢查結構描述服務或 OM 並重新啟動。Check and restart the schema service or OM.

查詢處理:查詢剖析結構描述服務可用性Query Processing: Query Parsing Schema Service Availability

警示名稱: 查詢處理:查詢剖析結構描述服務可用性Alert Name: Query Processing: Query Parsing Schema Service Availability

摘要: 因為無法使用與指定 Search Service 應用程式相關的結構描述服務,所以特定查詢的查詢剖析無法運作。特定查詢的查詢剖析失敗。Summary: Query parsing could not work for the particular query because the schema service related to the indicated Search service application was not available. Query parsing fails for particular queries.

原因Cause

無法使用索引器,或搜尋管理資料庫關閉,或兩者皆是。The indexer is unavailable, or the search administration database is down, or both.

  1. 已重新啟動查詢處理元件,但無法存取任何索引元件。請檢查索引元件。The query processing component has restarted and cannot access any index component. Check index components.

  2. 可使用索引器,但無法提供結構描述給查詢處理。Indexers are available, but cannot provide the schema to query processing.

解決方案Resolution

檢查結構描述服務或 OM 並重新啟動。Check and restart the schema service or OM.

查詢處理:查詢剖析範圍快取可用性Query Processing: QueryParsing Scope Cache Availability

警示名稱: 查詢處理:查詢剖析範圍快取可用性Alert Name: Query Processing: QueryParsing Scope Cache Availability

摘要: 因為無法使用指定 Search Service 服務應用程式的查詢規則,所以特定查詢的查詢剖析無法運作。Summary: Query parsing could not work for the particular query because the query rules for the indicated Search Service service Aapplication was not available.

原因Cause

無法使用查詢規則。Query rules are not available.

解決方案Resolution

檢查查詢規則。Check the query rules.

查詢服務:服務可用性查詢處理Query Service: Service availability query processing

警示名稱: 查詢服務:服務可用性查詢處理Alert Name: Query Service: Service availability query processing

摘要: 具有指定服務 URI 的查詢服務已停止。Summary: The query service that has the indicated service URI has stopped.

原因Cause

查詢處理元件在預期或意外的情況下停止。導致其公開的 WCF 服務關閉。Query processing component is stopped under either expected or unexpected conditions. That leads to the shutdown of the WCF service it exposes.

解決方案Resolution

如果問題仍然存在,請檢查查詢處理元件並重新啟動。If the issue persists, check and restart the query processing component.

查詢服務:啟動服務可用性 - 查詢處理Query Service: Start Service Availability - Query Processing

警告名稱: 查詢服務:啟動服務可用性 - 查詢處理Alert Name: Query Service: Start Service Availability - Query Processing

摘要: 因為查詢服務沒有正確運作,所以無法啟動具有指定服務 URI 的查詢服務。Summary: Unable to start the query service that has the indicated service URI because the query service is not working correctly.

原因Cause

有潛在的網路通訊服務問題存在。例如,WCF 連接埠正在使用中。Potential network communication service issues. For example, the WCF port is in use.

解決方案Resolution

若 WCF 連接埠正在使用中且必須釋出,請重新啟動查詢處理元件、查詢服務或 WCF 服務。Restart the query processing component, the query service or WCF services if the WCF port is in use and has to be released.

查詢服務:無法停止查詢處理Query Service: Unable to stop query processing

警示名稱: 查詢服務:無法停止查詢處理Alert Name: Query Service: Unable to stop query processing

摘要: 無法停止具有指定服務 URI 的查詢服務。Summary: Unable to stop the query service that has the indicated service URI.

原因Cause

有潛在的網路通訊服務問題存在。例如,WCF 連接埠正在使用中。Potential network communication service issues. For example, the WCF port is in use.

解決方案Resolution

若 WCF 連接埠正在使用中且必須釋出,請重新啟動查詢處理元件、查詢服務或 WCF 服務。Restart the query processing component, the query Service or WCF services if the WCF port is in use and has to be released.

查詢 URL 對應:備用 URL 對應服務可用性 - 查詢處理Query URL Mapping: Alternate URL Mapping Service Availability - Query Processing

警示名稱: 查詢 URL 對應:備用 URL 對應服務可用性 - 查詢處理Alert Name: Query URL Mapping: Alternate URL Mapping Service Availability - Query Processing

摘要: 因為無法使用對應服務,所以無法使用備用 URL 對應。查詢或結果處理失敗。Summary: The alternate URL mapping did not work because the mapping service was not available. Query or results processing fails.

原因Cause

無法使用備用存取對應 OM。The Alternate Access Mapping OM is unavailable.

解決方案Resolution

檢查備用存取對應或 OM,並視需要重新啟動。Check, and restart, the Alternate Access Mapping service or OM if it is necessary.

結構描述讀取者:結構描述服務可用性 - 查詢處理Schema Reader: Schema Service Availability - Query Processing

警示名稱: 結構描述讀取者:結構描述服務可用性 - 查詢處理Alert Name: Schema Reader: Schema Service Availability - Query Processing

摘要: 因為無法使用結構描述服務,所以無法運作特定查詢的結構描述讀取者。特定查詢的查詢處理失敗。Summary: The schema reader cannot work for the particular query because the schema service is not available. Query processing fails for particular queries.

原因Cause

無法使用索引器,或搜尋管理資料庫關閉,或兩者皆是。The Indexer is unavailable, or the search administration database is down, or both.

解決方案Resolution

檢查結構描述服務或 OM,並視需要重新啟動。Check and restart the schema service or OM if it is necessary.

搜尋管理平台服務:存放庫初始化失敗Search Admin Platform Services: Repository Initialization Failed

警示名稱: 搜尋管理平台服務:存放庫初始化失敗Alert Name: Search Admin Platform Services: Repository Initialization Failed

摘要: 每個元件中的 PackageManager 服務在元件啟動時會讀取 Default-manifest.txt,以快速找出存放庫目前的狀態。執行時,每個元件中的 PackageManager 會從主機控制器取得安裝及解除安裝的更新。本情況為無法初始化存放庫。這表示在主機控制器啟動時,存放庫的初始化失敗。例如,在主要容錯移轉期間或在重設存放庫期間。Summary: The PackageManager service in each component will read the Default-manifest.txt on component startup to find the current status of the repository quickly. While running, the PackageManager in each component obtains updates about installs and uninstalls from the host controller. In this case, the repository could not be initialized. This means that there was a failure when the repository was initializing on host controller startup. For example, during a primary failover or during a repository reset.

原因Cause

原因可能是 ACL 問題或毀損的存放庫資訊清單檔案。若是存放庫毀損而資訊清單檔案完好,初始化會嘗試再次重建存放庫。但重建失敗時仍會傳送相同的事件。The cause could be an ACL issue or a corrupted repository manifest file. If it is a corrupted repository with a good manifest file, initialization will try to rebuild the repository again. However, the same event is also sent when rebuild fails.

解決方案Resolution

  1. 檢查潛在的 ACL 問題。Check for potential ACL issues.

  2. 遵循此程序以修復次要 (非主要) 主機上的存放庫:Follow this procedure for fixing the repository on secondary (not primary) hosts:

    • 停止主機控制器。Stop the host controller.

    • 刪除目錄 C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Repository。Delete the directory C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Repository.

    • 啟動主機控制器。這麼做會使主機控制器使用與主要存放庫不同的 GUID 建立空的存放庫。然後次要存放庫會立即啟動以複製主要存放庫的內容。Start the host controller. This will affect the host controller to create an empty repository with a GUID that does not match the primary. So, the secondary will immediately start to replicate the contents of the primary.

搜尋管理平台服務:存放庫安裝失敗Search Admin Platform Services: Repository Installation Failed

警示名稱: 搜尋管理平台服務:存放庫安裝失敗Alert Name: Search Admin Platform Services: Repository Installation Failed

摘要: 指定的檔案在存放庫安裝失敗。當主要存放庫的字典安裝失敗時,使用者應注意如查詢建議等語言功能可能會過期。Summary: Repository installation fails for the file indicated. When dictionary installation fails for the primary, users should be aware that linguistic features such as query suggestions might get outdated.

原因Cause

檔案已安裝在存放庫中,或是相關的計時器工作失敗。The file may already be installed in the repository, or the related timer job may have failed.

解決方案Resolution

檢查存放庫,確保事件發生之後,字典編譯計時器工作已成功完成。您可從管理中心手動觸發計時器工作或使用 Microsoft PowerShell 來解除安裝。Check the repository. Make sure that a dictionary compilation timer job has completed successfully after the event. You can manually trigger the timer job from Central Administration or by using Microsoft PowerShell in order to re-install.

搜尋管理平台服務:存放庫複寫Search Admin Platform Services: Repository Replication

警示名稱: 搜尋管理平台服務:存放庫複寫Alert Name: Search Admin Platform Services: Repository Replication

摘要: 此情況會發生在次要存放庫。本機主機控制器中的存放庫發現其具有比主要主機控制器更低的存放庫版本 (或是當主要主機關閉時,找到比次要主機控制器更低的版本)。發生此情況時,本機存放庫會根據被觸發的方式,嘗試從主要或次要主機取得最新的版本。這表示複寫期間發生錯誤。Summary: This situation occurs in secondary repositories. The repository in the local host controller has found that it has a lower repository version than the primary host controller (or lower version than other secondary host controllers if the primary is down). When this happens, the local repository attempts to obtain the latest version from the primary or a secondary based on how it is triggered. This indicates that something went wrong during the replication.

原因Cause

由於網路問題,或是由於複寫期間的的遠端存放庫 (主機控制器) 問題,可能已遺失對已複寫之遠端存放庫的連線。本機存放庫可能已毀損,或有 ACL 問題。Connection to the remote repository which is being replicated can be lost due to a network issue or due to a remote repository (host controller) issue during replication. The local repository can be corrupted or have an ACL issue.

解決方案Resolution

如果問題仍然存在,就可能需要手動介入以根據問題加以修正 (參見原因)。但不包含網路及 ACL 等等這些具有明顯解決方案的問題,因為可以重新啟動遠端主機控制器。若存放庫毀損,通常會自動重新建立。If persistent, a manual intervention might require to make it correct based on the problem (see cause). Except for the obvious resolutions on network and ACL and so on, remote host controller can be restarted. If the repository is corrupted, usually it is automatically rebuilt.

搜尋分析:分析執行狀態搜尋分析Search Analytics: analysis run state Search Analytics

警示名稱: 搜尋分析:分析執行狀態搜尋分析Alert Name: Search Analytics: analysis run state Search Analytics

摘要: 分析可能會遇到各種不同問題。所以無法保證系統會成功執行搜尋分析。在分析失敗模型後,計時器工作會嘗試重新排程新的分析執行,而不需等待觸發每日排程。Summary: An analysis can encounter different problems. Hence the system cannot guarantee a successful run of search analytics analysis. The timer job, following the analysis failure model, will try to re-schedule a new analysis run to prevent from waiting until daily schedule is triggered.

徵狀:當計時器工作偵測到成功的分析執行時,就會觸發監視器。Symptoms: Monitor is triggered when unsuccessful analysis run is detected by the timer job.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 無法使用分析處理元件或其他某些伺服器陣列元件。Analytics processing component(s) or some other farm components are not available.

  • 無法執行或使用資料庫 (連結資料庫、分析報表資料庫等)。Databases (Link database, analytics reporting database, etc.) are not running or reachable.

  • 網路中斷。Network outage.

  • 伺服器問題。Server issues.

解決方案Resolution

請確保下列區域可正常運作:Make sure these areas are functioning:

  • 分析處理元件及其他伺服器陣列元件正常運作。The analytics processing component(s) and other farm components are functioning correctly.

  • 沒有網路問題。There are no networking issues.

  • 沒有伺服器問題。There are no server issues.

  • 可使用分析資料庫,且使用者可讀取或寫入資料庫。The analytics databases are available and that the user can read or write to the databases.

搜尋分析:計時器工作無法解析分析處理引擎 (APE)Search analytics: Timer job cannot resolve Analytics Processing Engine (APE)

警示名稱: 搜尋分析:計時器工作無法解析分析處理引擎 (APE)Alert Name: Search analytics: Timer job cannot resolve Analytics Processing Engine (APE)

摘要: 計時器工作成功找到 Search Service 應用程式後,就會嘗試解析分析處理元件中的分析處理引擎。您需要此元件才能讀取或寫入分析設定,以及啟動、停止、暫停或恢復分析。徵狀:若系統找不到分析處理引擎或無法與其通訊,就無法啟動新的分析執行。Summary: After the timer job has successfully found the Search service application it will try to resolve the Analysis Processing Engine in the analytics processing component. This component is needed to be able to read or write the analysis configuration and to start, stop, suspend, or resume the analysis. Symptoms: If the system cannot locate or communicate with the Analysis Processing Engine, it will be unable to start a new run of the analysis.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 無法連線至 Search Service 應用程式。Unable to connect to Search service application.

  • 無法連線至搜尋管理元件。Unable to connect to the search administration component.

  • 無法連線至系統管理員。Unable to connect to System Manager.

  • 無法連接至分析處理引擎。Unable to connect to the Analysis Processing Engine.

解決方案Resolution

確認下列元件均已啟用且在運行中:Ensure that the following components are up and running:

  • Search Service 應用程式。Search service application.

  • 搜尋管理元件。Search administration component.

  • 系統管理員。System Manager.

  • 分析處理元件。Analysis Processing component.

警示名稱: 搜尋分析:計時器工作無法解析連結資料庫Alert Name: Search Analytics: Timer job cannot resolve Link database

摘要: 計時器工作會在嘗試啟動搜尋分析之前,先檢查所有可使用的連結資料庫分割區。徵狀:若無法使用連結資料庫分割區,則在啟動新的分析執行時,會中止此啟動嘗試。新連結資料庫檢查後,會在下一次計時器工作輪詢 (每 10 分鐘一次) 執行新的啟動嘗試。Summary: The timer job will check that all Link database partitions are available before it tries to start the search analytics analysis.Symptoms:If the Link database partitions are unavailable when it is time to start a new analysis run, the start try will be aborted. New Link database checks followed by a new start try will be performed in the next timer job polls (every 10 minutes).

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 無法解析 Search Service 應用程式。Unable to resolve the Search service application.

  • 連結資料庫連線逾時。Link database connection timed out.

  • 連結資料庫連線遭拒。Link database connection is refused.

  • 無法使用連結資料庫。Link database is not available.

解決方案Resolution

確認可使用連結資料庫。也請確認使用者具有對連結資料庫的讀取權。Verify that the Link database is available and reachable. Also verify that the user has access to read from the Link database.

搜尋分析:分析執行狀態搜尋分析Search Analytics: analysis run state search analytics

警示名稱: 搜尋分析:分析執行狀態搜尋分析Alert Name: Search Analytics: analysis run state search analytics

摘要: 搜尋分析會由其計時器工作啟動。分析會執行到所有工作完成為止,然後分析狀態會設為已停止。若某些工作無法完成,則分析執行會停止 (在重試數次後),然後狀態會設為失敗。完成前已停止表示分析已達到已停止狀態,但分析工作卻「尚未」全部完成。有些由分析完成的工作可能已傳送至索引,但為了確保沒有遺失任何項目,在下一次分析執行期間,會再次處理所有工作。Summary: The search analytics analysis is started by its timer job. The analysis will run until all its tasks are completed, and the analysis state will be set to Stopped. If some tasks cannot be completed, the analysis run will be stopped (after some retries) and the state set to Failed. Stopped before completion indicates that the analysis has reached the Stopped state, but all analysis tasks have NOT completed. Some of the work done by the analysis might have been sent to the index then, but to make sure nothing is lost and all of the work is processed again during next analysis run.

原因Cause

分析已因為下列原因停止:Analysis is stopped for the following reasons:

  • 已手動停止執行中的搜尋分析A manual stop on a running search analytics analysis was performed

  • 或者,系統維護工作需要停止執行中的搜尋分析。Or, system maintenance tasks require stopping a running search analytics analysis.

解決方案Resolution

檢查搜尋分析的狀態以及是否有任何作用中的系統維護工作。Check the state of the search analytics analysis and any active system maintenance tasks.

搜尋收集程式:磁碟完整編目程式Search Gatherer: Disk Full Crawler

警示名稱: 搜尋收集程式:磁碟完整編目程式Alert Name: Search Gatherer: Disk Full Crawler

摘要: 當編目程式進行編目內容時,會在暫存位置建立檔案。此暫存位置的大小會與日俱增,而讓暫存位置所在的磁碟耗盡空間。當此情況發生時,SharePoint 會出現下列徵狀:Summary: As the crawler crawls content, it creates files in a temporary location. This temporary location can grow over time. The disk where the temporary location is located is running out of space. SharePoint experiences the following symptoms when this happens:

  • 編目作業無法繼續執行,似乎停滯不前。The crawl does not progress and seems to stall.

  • 編目記錄未顯示任何新的編目文件。The crawl logs show no new crawled documents.

原因Cause

編目程式建立暫存檔的磁碟已耗盡空間。The disk on which the crawler creates temporary files is running out of space.

解決方案Resolution

  • 釋放編目程式建立暫存檔所在磁碟的空間。若要釋放磁碟空間:使用 [磁碟清理] 刪除儲存暫時索引檔案之磁碟機中的暫存檔。使用接下來的程序可判斷索引檔案的位置。Free up space on the disk on which the crawler creates the temporary files. To free up disk space: Use Disk Cleanup to delete temporary files on the drive where the temporary index files are stored. Use the procedure following this one to determine the location of the index files.

    注意

    若暫存檔位於其他磁碟機而不是作業系統磁碟機 (磁碟機 C),就必須在您刪除暫存檔之後,重新啟動搜尋服務以測試編目程式的效能。If the temporary files are located on a drive other than the operating system drive (drive C), you must restart the search service to test the performance of the crawler after you delete the temporary files.

  • 磁碟清理完成之後,測試編目程式的效能。After Disk Cleanup is complete, test the performance of the crawler.

  • 若編目程式未編目內容,請刪除選取磁碟機上不需要的檔案及資料夾。If the crawler is not crawling content, delete unnecessary files and folders on the selected drive.

  • 若您無法清除任何磁碟空間,請重新啟動搜尋服務。重新啟動搜尋服務會重新建立已編目檔案的暫存目錄。在命令提示字元視窗中,執行 net stop osearch15 命令可停止搜尋服務。執行 net start osearch15 命令可重新啟動搜尋服務。If you cannot clear any disk space, restart the search service. Restarting the search service recreates the Temp directory for crawled files. In a Command Prompt window, run the command net stop osearch15 to stop the search service. Run the command net start osearch15 to restart the search service.

搜尋流量分析:分析設定失敗Search Usage Analytics: Analysis configuration failed

警示名稱: 搜尋流量分析:分析設定失敗Alert Name: Search Usage Analytics: Analysis configuration failed

摘要:Summary:

  1. 若系統無法取得或設定分析設定,就不會排程新的分析執行。計時器工作會在稍後重試。If the system cannot get or set the analysis configuration, it will not schedule a new run of the analysis. The timer job will retry later.

  2. 使用錯誤的事件設定執行分析:Analysis run with wrong event configuration:

    • 錯誤的建議權數。Wrong recommendations weight.

    • 錯誤的事件發生率權數。Wrong event rate weight.

  3. 擷取到刪除範圍時,所有來自 API 的錯誤皆會產生事件。在沒有發生此狀況時分析仍可執行。但結果的品質或正確性會隨著時間每況愈下。When the deletion scopes are fetched, any errors from the API will result in an event. The analysis can still run without this. However, the quality or correctness of the result will deteriorate over time.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  1. 無法使用分析處理元件。Analytics processing component not available.

    • 網路問題。Network issues.

    • 來自 API 逾時。Time-out from API.

    • 分析處理元件擲回例外狀況。Analytics processing component throwing exceptions.

    • 分析報表資料庫關閉。Analytics reporting database down.

    • 網路功能問題。Networking issues.

    • 設定錯誤。Errors in configuration.

  2. 從 API 取得錯誤事件設定。Getting wrong event configuration from API.

    • 系統中沒有設定資料。No configuration data is present in the system.

    • 網路問題導致呼叫 API 失敗。Networking problems causing API calls to fail.

    • API 傳回逾時。API returning time-out.

  3. 當您使用 API 時,有網路問題導致失敗。Network issues causing failures when you are using the API.

    • API 傳回錯誤。The API returning errors.

解決方案Resolution

  1. 請確保下列區域可正常運作:Make sure these areas are functioning:

    • 系統中有 Search Service 應用程式。There is a Search service application in the system.

    • 分析處理元件可正確運作。The Analytics processingcomponent is functioning correctly.

    • 沒有網路問題。There are no networking issues.

  2. 檢查設定。Check configuration.

  3. 確認元件中的 API 是否已開啟且正在運作。Verify that the component where the API is running is up and functioning.

    • 檢查所有網路問題。Check for any network problems.
  4. 確認搜尋分析在過去 30 天有執行。Verify that search analytics has run the last 30 days.

搜尋流量分析:無法啟動分析Search Usage Analytics: Analysis failed to start

警示名稱: 搜尋流量分析:無法啟動分析Alert Name: Search Usage Analytics: Analysis failed to start

摘要: 無法啟動流量分析,或是流量分析執行期間失敗。Summary: Usage analytics analysis cannot start, or usage analytics analysis fails during execution.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  1. 這可能是由於外部相依性所造成,例如設定、分析處理元件或 Search Service 應用程式相依性或網路問題。This can be caused by external dependencies like configuration, analytics processing component or Search service application dependencies or networking issues.

  2. 若流量分析執行期間失敗,也會觸發監視器。This monitor can also be triggered if the usage analytics analysis fails during execution.

  3. 這可能是由於流量分析相依的元件失敗所造成,例如分析處理元件或或其他網路問題。This can be caused by failures in components usage analytics depend on, such as the analytics processing component or other networking issues.

  4. 還有可能是處理事件中的某些項目導致分析失敗。There can also be something in the events being processed causing the analysis to fail.

解決方案Resolution

確認其他 System Center Operations Manager 監視器並查看是否有顯示任何上層錯誤。Verify other System Center Operations Manager monitors and see whether any parent errors are present.

  • Search service 應用程式已開啟。The Search service application is up.

  • 分析處理資料庫和連結資料庫都在執行,且處於狀況良好狀態。The analytics processing database and link databases are running, and are in healthy state.

  • 分析處理元件沒有任何問題There is no problem with the analytics processing component

  • 磁碟空間沒有任何問題。There is no problem with disk space.

  • 沒有網路連線問題。There is no metwork connectivity issue.

  • 正在執行流量分析計時器工作。The usage analytics timer job is running.

  • 正在執行搜尋分析計時器工作。The search analytics timer job is running.

  • 確認搜尋分析的狀態。Verify the status of the search analytics analysis.

搜尋流量分析:饋送失敗Search Usage Analytics: Feeding failure

警示名稱: 搜尋流量分析:饋送失敗Alert Name: Search Usage Analytics: Feeding failure

摘要: 這表示流量分析提供的建議和統計資料將太舊或遺失。不會顯示任何最近的分析變更。Summary: This means the recommendations and statistics provided by usage analytics will be old or missing. Any recent analysis changes will not be visible.

徵狀:分析所需的流量分析饋送失敗。Symptom: usage analytics feeding required for the analysis was unsuccessful.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 索引器傳回錯誤。The indexer is returning errors.

  • 內容處理元件沒有運作。The content processing component is not working.

  • 元件上執行的索引器可能已經關閉。The component that the indexer is running on could be down.

解決方案Resolution

  • 確認索引系統是否有正確運作。Verify that the index system is functioning correctly.

  • 檢查網路錯誤。Check for network errors.

  • 確保分析處理元件沒有任何錯誤。Make sure there are no errors on the analytics processing component.

搜尋流量分析:報表 API 寫入失敗Search Usage Analytics: Reporting API write failure

警示名稱: 搜尋流量分析:報表 API 寫入失敗Alert Name: Search Usage Analytics: Reporting API write failure

摘要: 背景或徵狀:Summary: Background or symptoms:

  1. 若必須重建快取檔案,就會使用寫入報表 API 或資料庫的資訊。當流量分析無法寫入報表 API 時,就表示沒有更新建議和資料。所以顯示給使用者的計數就會過期,而下一次重建快取時也會顯示舊的或錯誤的資料。The information written to the reporting API or database is used if the cache files must be rebuilt. When usage analytics cannot write to the reporting API, this means that the recommendations and data is not updated. Counts presented to the user are therefore out of date, and old or wrong data will also be presented next time that the cache is rebuilt.

  2. 無法讀取報表 API,所以無法建立快取檔案,導致沒有執行任何分析。在此狀態中執行分析會造成複寫目前資料。The Reporting API could not be read so that no cache files could be created and the analysis will therefore not be run. Running the analysis in this state would in effect overwrite the current data.

影響:Impact:

  • 沒有執行任何流量分析。There will be no usage analytics analysis run.

  • 系統中將不會更新此項目的建議。Recommendations will not be updated for items in the system.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 報表 API 傳回錯誤說明資料庫已關閉。Reporting API is returning an error saying database is down.

  • 報表 API 回應已傳送錯誤資料 (沒有儲存任何資料)。Reporting API is responding that the wrong data is being sent (nothing is stored).

  • 無法使用報表 API (網路問題)。The reporting API cannot be reached (networking issues).

  • 報表 API 傳回錯誤說明資料庫已關閉Reporting API is returning an error saying database is down

  • 報表 API 傳回空白 (錯誤資料)。Reporting API is returning empty (wrong data).

  • 快取傾印工具發生問題。The cache dumper is malfunctioning.

解決方案Resolution

  1. 確認系統中沒有任何資料庫問題,並確保分析報表資料庫正在運作中。Verify that there are no database problems in the system, and make sure that the analytics reporting database is functioning.

  2. 確認分析處理元件正在運作中。這代表可執行分析。Verify that analytics processing component is functioning. This means that analyses can run.

  3. 檢查有無任何網路問題。Check for any networking issues.

搜尋流量分析:無法使用存放區Search Usage Analytics: Store not available

警示名稱: 搜尋流量分析:無法使用存放區Alert Name: Search Usage Analytics: Store not available

摘要: 背景或徵狀:Summary: Background or symptoms:

  1. 流量分析無法與事件存放區通訊。將不會啟動流量分析,且分析報表資料庫中的流量分析資料以及搜尋索引將會過期。Usage analytics cannot communicate with the event store. The usage analysis will not be started, and usage analytics data in the analytics reporting database and the search index will be stale.

  2. 流量分析的第一個步驟中,系統會從事件存放區擷取事件資料。這是對分析的原始輸入。其中包含針對系統中使用者所執行的動作。若沒有此資料,將無法執行分析。During the first step of the usage, the system fetches the event data from the event store. This is the raw input to the analysis. It contains the actions for the users in the system. Without this data, the analysis cannot be run.

原因Cause

可能原因包括下列一或多項:One or more of the following might be the cause:

  • 網路中斷、事件存放區處理序已關閉,或事件存放區對要求傳回錯誤反應。Network outage, Event Store process is down, or the event store is returning errors in response to request.

  • 事件存放區可能已關閉。由於註冊事件的元件沒有正確運作,導致事件存放區沒有傳回資料,或是有網路問題,造成無法使用事件存放區。The event store can be down. The event store is returning no data because the components registering events are not functioning correctly, or there are networking issues so that the event store cannot be reached.

解決方案Resolution

  • 確認事件存放區已啟動並執行。Ensure that the event store is up and running.

  • 確認事件存放區是否有正確運作。Verify that the event store is functioning correctly.

  • 檢查網路錯誤。Check for networking errors.

  • 確保系統中的資料庫正在運作。Make sure the databases in the system are running.

搜尋流量分析:無法使用流量分析 APESearch Usage Analytics: Usage analytics APE not available

警示名稱: 搜尋流量分析:無法使用流量分析 APEAlert Name: Search Usage Analytics: Usage analytics APE not available

摘要: 背景或徵狀:Summary: Background or symptoms:

  1. 無法擷取 Search Service 應用程式,這表示無法執行新的分析,且無法更新建議。Fails to retrieve Search service application, which means that no new analysis can be run, and recommendations cannot be updated.

  2. 無法擷取分析引擎服務,所以沒有可啟動的新分析。Fails to retrieve Analysis Engine Service so that no new analysis can be started.

原因Cause

無法連線至 Search Service 應用程式可能是由下列一或多個原因所造成:Inability to connect to the Search service application may be caused by one or more of the following:

  • 網路問題。Network issues.

  • 未建立 Search Service 應用程式。Search service application not created.

  • 使用者權限不符。User permissions mismatch.

無法連線至分析引擎服務可能是由下列一或多個原因所造成:Inability to connect to the Analysis Engine Service can be caused by one or more of the following:

  • 無法連線至 Search Service 應用程式。Unable to connect to Search service application.

  • 無法連線至搜尋管理元件。Unable to connect to the search administration component.

  • 無法連線至系統管理員。Unable to connect to System Manager.

  • 網路問題。Network problems.

  • 使用者權限或 WCF 錯誤。User rights or WCF errors.

  • 無法連線至分析處理元件。Unable to connect to the Analytics processing component.

解決方案Resolution

檢查下列區域:Check the following areas:

  1. 檢查下列區域:Check the following areas:

    • Search Service 應用程式不存在。A Search service application does not exist.

    • 網路問題。Network problems.

    • 使用者權限或 WCF 錯誤。User permissions or WCF errors.

  2. 確認下列元件均已啟用且在運行中:Ensure that the following components are up and running:

    • Search Service 應用程式。Search service application.

    • 搜尋管理元件。Search administration component.

    • 系統管理員。System Manager.

    • 分析處理元件Analysis processing component

    • 主機的網路連線正常。Networking is ok on host.

流量表超過最大位元組限制Usage table exceeded max bytes limit

警示名稱: 流量表超過最大位元組限制Alert Name: Usage table exceeded max bytes limit

摘要: 此項警示回報流量表超過其配額。流量資料儲存在各種表格中。且每個表格皆有其配額。一旦表格已滿,就無法插入新資料。Summary: This alert is to report that a usage table exceeds its quota. Usage data is stored in various tables. And each table has its quota. Once a table is full, new data cannot be inserted.

原因Cause

一天中產生過多流量資料。Too much usage data is generated in one day.

解決方案Resolution

有兩種方法可解決此問題:There are two ways to resolve this issue:

  1. 在「設定」表格中增加表格配額。Extend the table quota defined in "configurations" table.

  2. 停用流量供應者以停止產生資料。Disable the usage provider to stop generating data.

流量表超過最大位元組限制Usage table exceeded max bytes limit

警示名稱: 流量表超過最大位元組限制Alert Name: Usage table exceeded max bytes limit

摘要: 此項警示回報流量表超過其配額。流量資料儲存在各種表格中。且每個表格皆有其配額。一旦表格已滿,就無法插入新資料。Summary: This alert is to report that a usage table exceeds its quota. Usage data is stored in various tables. And each table has its quota. Once a table is full, new data cannot be inserted.

原因Cause

一天中產生過多流量資料。Too much usage data is generated in one day.

解決方案Resolution

有兩種方法可解決此問題:There are two ways to resolve this issue:

  1. 在「設定」表格中增加表格配額。Extend the table quota defined in the "configurations" table.

  2. 停用流量供應者以停止產生資料。Disable the usage provider to stop generating data.

服務主機控制器Services Host Controller

警示名稱: 服務主機控制器Alert Name: Services Host Controller

摘要: 目前無法使用主機控制器服務。Summary: The host controller service is currently unavailable.

原因Cause

這可能表示主機控制器有內部問題。This may indicate an issue internal to the host controller.

解決方案Resolution

如果問題仍然存在,或問題重複發生,請檢查主機控制器,並視需要重新啟動。If persistent or recurring, check the host controller and restart if it is necessary.

另請參閱See also

概念Concepts

監視 SharePoint Server 中的計劃Plan for monitoring in SharePoint Server

其他資源Other Resources

適用於 SharePoint Foundation 的 System Center 監視組件System Center Monitoring Pack for SharePoint Foundation

適用於 SharePoint Server 2013 的 System Center 監視組件System Center Monitoring Pack for SharePoint Server 2013

適用於 SharePoint Server 2016 的 System Center 監視組件System Center Monitoring Pack for SharePoint Server 2016