SharePoint Search 2013

  1. The Search service database is missing. Please go to the Shared Service Provider administration page and enter the Search ...
  2. The search service is not able to connect to the machine that hosts the administration component. Verify that the administration ...
  3. The search service is running as a local System service. To access Exchange documents, check that the search service is running ...
  4. The search service will access all content using this account. The account will be added to the Full Read policy, giving ...
  5. The search service will run using this account. The search service account must not be a built-in account in order to access ...
  6. The security descriptor for this item only contained built-in access control entries. The built-in ACEs have to be removed ...
  7. The security validation for this page is invalid and might be corrupted. Please use your web browser's Back button to try ...
  8. The selected content index definition did not initialize and cannot be used. Check server status, content index configuration, ...
  9. The selected refinement target is no longer valid. To enable this Web Part, open it for editing and select a valid refinement ...
  10. The service cannot access the Exchange 5.5 server. The configured Microsoft Exchange 5.5 server name may be invalid, the ...
  11. The service cannot access the Exchange 5.5 service. The account used by the search service may not be an Exchange administrator, ...
  12. The SetStatus operation cannot be completed, because another SetStatus operation is already in progress. Try again after ...
  13. The SharePoint server being crawled did not respond to the crawler because crawls may have had an impact on its end-user ...
  14. The SharePoint Server Indexing Service that was enabled on this server will be uninstalled and all index files will be deleted ...
  15. The site name cannot be empty, contain spaces or the characters \/#@], or be longer than 254 characters or begin with the ...
  16. The site name is not specified or is invalid. Specify a site name that does not contain the following characters: /\@#| or ...
  17. The specified account information is incorrect or not valid. Check that the correct account and password are being used. ...
  18. The specified account name cannot be used because it contains invalid characters, such as '\'. Use a valid account name. ...
  19. The specified address was excluded from the index. The site hops or page depth restrictions may have to be modified to include ...
  20. The specified content index was not found. Check to see if it was deleted, or if there are errors in your application code. ...
  21. The specified database instance does not exist in the configuration database. Please choose a different database instance. ...
  22. The specified file name is invalid. This error is obsolete and should no longer be reported. Call Microsoft Product Support. ...
  23. The specified gatherer application could not be found. Use the name of an existing application, or reinstall the application. ...
  24. The specified name for this object exceeds the maximum length, which is usually 2047 characters. Use a shorter name for the ...
  25. The specified page could not be displayed because the application ID is missing or invalid. You can attempt to browse to ...
  26. The specified Pluggable Security Trimmer Implementation Type could not be loaded or it does not implement ISecurityTrimmerPost, ...
  27. The specified Pluggable Security Trimmer Implementation Type does not implement ISecurityTrimmerPost, ISecurityTrimmerPre ...
  28. The specified Pluggable Security Trimmer initialization property name or value has a '~' in it, which is a reserved character. ...
  29. The specified scope does not exist in the database. The information in the service does not agree with that in the database. ...
  30. The specified search server already exists. This error is obsolete and should no longer be reported. Call Microsoft Product ...
  31. The specified URL mapping is invalid. The "from" mapping is empty, or the "from" mapping is the same as the "to" mapping. ...
  32. The SQL Express database is near the 4GB limit. All running crawls have been stopped and scheduled crawls will not run. You ...
  33. The stack for a thread in this process is corrupted due to a programming bug. This may be a security threat and indicate ...
  34. The start address {0} cannot be added when crawling the entire web application. Either select to crawl only the SharePoint ...
  35. The string ID ({2}) could not be found for locale ({0}) or the site's default language ({1}). Please make sure you include ...
  36. The supplied URL cannot contain wildcard characters '{0}'. The string '{1}' supplied in parameter 'urlQueryString' contains ...
  37. The system attempted to load a filter marked as apartment from an embedded component in a multi-threaded filter daemon. The ...
  38. The system attempted to load a filter marked as apartment in a multi-threaded filter daemon. The document will be retried ...
  39. The system attempted to load an apartment threading model filter marked in a multi-threaded filter daemon. The document will ...
  40. The system cannot write to the configuration file, because it was modified since it was last read. Stop and restart the search ...
  41. The system was not able to retrieve all the crawl log information within the standard UI timeout. Try to restrict your query ...
  42. The thesaurus file %2 for lcid %3 has invalid format. Please edit the file and correct it. Use retail tracing for detailed ...
  43. The Topic Assistant requires sample documents from at least two categories. Try again when sample documents for more categories ...
  44. The total number of client polls since the start of the component. Each time a client refreshes the session to check for ...
  45. The total number of documents skipped in the submission service before being delivered to the content processing component. ...
  46. The total number of flow instances that have been aborted due to full queues. This will occur when there has not been a successful ...
  47. The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. ...
  48. The URL that was provided is shown below. Complete the form and log on to access a page that requires credentials. If the ...
  49. The URL was already processed during this update. If you received this message while processing alerts, then the alerts are ...
  50. The urn:schemas-microsoft-com:publishing:ShortcutTarget property must be type LPWSTR. Change the type for the property to ...
  51. The user account name cannot be resolved within the Directory Server. You would need to verify whether the user is a real ...
  52. The user agent string was not specified or contains invalid characters. Specify a user agent which is not empty and does ...
  53. The user name mapping cannot be read. Check that the database, view, and column names are correct, that the Lotus Notes database ...
  54. The user name mapping cannot be read. Check that the database, view, and column names are correct, that the Notes database ...
  55. The value cannot be set, because the object was already deleted or was not initialized properly. Check that the object reference ...
  56. The value cannot be set, because the object was already deleted or was not initialized properly. Make sure the object reference ...
  57. The was a problem configuring your Search Alerts. It looks like you don't have a valid user profile. To verify that your ...
  58. The was a problem upgrading your Search Alerts. It looks like you don't have a valid user profile. To verify that your profile ...
  59. There are no Analytics Reporting Databases created for the Search Service Application. Search topology cannot be initialized. ...
  60. There is a mismatch in the major version number. Check that the same versions of search are used on both the content index ...
  61. There is a mismatch in the property store version numbers. Ensure that the same versions of search are used on both the content ...
  62. There is a mismatch in the protocol between the search service and the client. Install the correct version of the client. ...
  63. There is already an Exchange results source registered. Only the Exchange source which comes first alphabetically will be ...
  64. There is insufficient privilege to access the Microsoft Exchange 5.5 server. Check that the Microsoft Exchange 5.5 configuration ...
  65. There is insufficient privilege to access the Microsoft Exchange 5.5 Server. Verify that the Microsoft Exchange 5.5 configuration ...
  66. There is no backup content index. This error is obsolete and should no longer be reported. Call Microsoft Product Support. ...
  67. There is no server in this farm capable of running Search. Search Server requires at least one server with an install type ...
  68. There is no update in progress. This error is obsolete and should no longer be reported. Call Microsoft Product Support. ...
  69. There is not enough available physical or virtual memory for chunk buffers. Chunk buffers are needed to index data. Please ...
  70. There is not enough occurrence buffer memory available. Possible causes include too many processors, too many filter threads, ...
  71. There shouldn't be a Search Application in SPF farm or MOSS Standalone before starting the restore. Delete existing Search ...
  72. There was an error writing to the temporary noise word file. This error is obsolete and should no longer be reported. Call ...
  73. There was an exception in the Database. Please retry your operation and if the problem presists, contact an administrator. ...
  74. There were not enough keywords in the sample documents to train the Topic Assistant. Try again when more sample documents ...
  75. There were not enough sample documents to train the Topic Assistant. Try again when more sample documents are available. ...