SharePoint Server 2016

  1. The setting makes this service application available for use by default for web applications in this farm. Do not check this ...
  2. The setup path is from Windows SharePoint Services version 2.0 or 3.0 and was not upgraded to Microsoft SharePoint Foundation ...
  3. The SharePoint Central Administration Web Application authentication provider is a global setting to the server farm. When ...
  4. The SharePoint Central Administration Web Application content files will not be installed because a Central Administration ...
  5. The SharePoint Central Administration Web Application port is a global setting to the server farm. When changing the port, ...
  6. The SharePoint Foundation service is not configured with a Directory Management Service that supports distribution groups. ...
  7. The SharePoint groups were created successfully, but an error occurred while creating the distribution group for the member ...
  8. The SharePoint Incoming E-Mail Service was unable to configure the SMTP security policy on |0, because of the following error: ...
  9. The SharePoint metadata manager can import a term set from a UTF-8 CSV format file. Use the sample file as a template for ...
  10. The SharePoint Products Configuration Wizard help file could not be found. Repair this product by selecting it from the Add/Remove ...
  11. The SharePoint server %1 returned an error when retrieving the change denoted by %2. Some changes may have been missed because ...
  12. The SharePoint Server 2001 category hierarchy will be imported under the parent area specified in Location . Click Change ...
  13. The SharePoint Server Enterprise feature is not activated on this site. Activate the feature to use Business Data columns. ...
  14. The SharePoint Server Enterprise feature is not activated on this site. Activate the feature to use External Data Columns. ...
  15. The SharePoint SiteSubscriptionSettings service must be started and an application must be provisioned to set the eDiscovery ...
  16. The SharePoint URL is a valid site but PerformancePoint Services features have not been configured. Please contact your site ...
  17. The SharingCapability set for this SPOSite will not take effect until the '{0}' SharingCapability is also enabled on the ...
  18. The sign-in name or password that was sent to the Microsoft account STS was not correct. There is an existing "e-mail as ...
  19. The single sign-on application associated with this IView is not found. Contact your administrator to correct this problem. ...
  20. The single sign-on application associated with this portlet is not found. Contact your administrator to correct this problem. ...
  21. The site %1 is approaching its storage quota limit. The following administrators can access the central administration site ...
  22. The site collection could not be restored. If this problem persists, please make sure the content databases are available ...
  23. The site collection feature "Cross-Site Collection Publishing" is required for this operation. Activate the feature and try ...
  24. The site collection has already been upgraded, but some additional work may be required. You should validate that the site ...
  25. The Site Collection Heath Checks have never run for this version of the site collection. Click Start checks to run the heath ...
  26. The site collection is experiencing some problems. If you are the Microsoft Online Services administrator, open a service ...
  27. The site collection is experiencing some problems. If you are the Microsoft Online Services administrator, open a service ...
  28. The site collection level fields, content types and webparts required for discussion lists, reputation, categories and membership ...
  29. The site column '^1' might not be supported by earlier versions of client programs. Adding this column might block those ...
  30. The site column ^1 is configured to append changes to existing text. You must first turn on versioning in this list before ...
  31. The site definition with Id |0 is referenced in the database |1], but is not installed on the current farm for sites with ...
  32. The site definitions with Id |0 is referenced in the database |1], but is not installed on the current farm. The missing ...
  33. The site located at |0 in the database |1 is using SharePoint 2007 UI which is no longer supported and may cause visual errors ...
  34. The Site Mailbox app helps you keep email and documents close together by connecting your site to an Exchange mailbox. You ...
  35. The site master page will be used by all publishing pages - the pages that visitors to your website will see. You can have ...
  36. The site master page will be used by all publishing pages. Select the first option to inherit the site master page of the ...
  37. The site name is not specified or is invalid. Specify a site name that does not contain the following characters: /\@#| or ...
  38. The site named |0 and with id |1 in content database |2 in the database server |3 was unable to be deleted from the configuration ...
  39. The site named |0 and with id |1 was found in the content database |2 in the database server |3. However, the following error ...
  40. The site specified by the MySiteHostLocation parameter is not configured to use the proxy specified by the ProfileServiceApplicationProxy ...
  41. The site specified by the MySiteHostLocation parameter is not configured to use the site subscription specified by the Identity ...
  42. The site specified by the MySiteHostLocation parameter must either use the "SPSMSITEHOST#0" template or have no template ...
  43. The site subscription specified by the Identity parameter already exists in the proxy specified by the ProfileServiceApplicationProxy ...
  44. The site subscription specified by the Identity parameter does not exist in the proxy specified by the ProfileServiceApplicationProxy ...
  45. The site template was not provisioned successfully. Delete this site collection in Central Administration, and then create ...
  46. The site URL is not valid. The site URL should refer to a site in the current site collection and should be specified as ...
  47. The site URL is not valid. The site URL should refer to a site in the current site collection and should be specified as ...
  48. The Site Welcome Page is set to VariationsRoot but there are no Variation Sites. Site Administrator can reset the Site Welcome ...
  49. The site |0 cannot be added to the site subscription because it may contain apps. Use the |1 powershell cmdlet to create ...
  50. The site |0 has user |1 which is a |2 autentication user which is inconsitent with the web application which is in |3 authentication ...
  51. The SiteMapProvider was configured to inherit settings from the parent SPWeb, but this is not allowed for the root SPWeb. ...
  52. The Sites Directory is a catalog of sites that can be grouped into categories. To submit a site to the Sites Directory go ...
  53. The Sites Directory is a catalog of sites that can be grouped into categories. To submit a site to the Sites Directory, please ...
  54. The size of files uploaded has exceeded, or may exceed, the limit set for the folder "%1!-.200s!". Remove some files from ...
  55. The size of the input given to a bulk MethodInstance exceeds the maximum value specified in its 'Bulk Input Limit' property. ...
  56. The size of the SOAP response that the data source returns to the data retrieval service can be limited with this setting. ...
  57. The SMTP service is not installed. For information about the SMTP service requirement see Microsoft SharePoint Foundation ...
  58. The solution "{0}" is installing assemblies into the bin directory. The bin directory is deprecated and assemblies installed ...
  59. The solution "{0}" needs to install assemblies in the Global Assembly Cache (GAC). If you fully trust this solution, use ...
  60. The solution "|0" is installing assemblies into the bin directory. The bin directory is deprecated and assemblies installed ...
  61. The solution "|0" needs to install assemblies in the Global Assembly Cache (GAC). If you fully trust this solution, use the ...
  62. The solution cannot be deployed. Directory "|0" associated with feature '|1' in the solution is used by feature '|2' installed ...
  63. The solution cannot be deployed. The feature '|0' uses the directory "|1" in the solution. However, it is currently installed ...
  64. The solution contains no Web application scoped resource, and therefore cannot be deployed to a particular Web application. ...
  65. The solution contains no Web application scoped resource, and therefore cannot be retracted from a particular web application. ...
  66. The solution contains Web application scoped resources and should be deployed to specific Web applications. Please choose ...
  67. The solution contains Web application scoped resources and should be retracted from specific Web applications. Please choose ...
  68. The Solution Deployment operation for |0 failed. A FirstMatch CodeGroup could not be found in the current Code Access Security ...
  69. The Solution Deployment operation for |0 failed. The Code Access Security portion of the solution failed to deploy because ...
  70. The solution initialization failed. Restarting (!idspnOutlook_Short) may fix the problem. If the problem persists, you need ...
  71. The solution is not valid. Directory "|0" associated with feature '|1' is already used by feature '|2' in the solution. All ...
  72. The solution is not valid. The feature ID '|0' in the feature manifest file "|1" is associated with another feature in "|2" ...
  73. The solution is not valid. The feature ID '|0' in the feature manifest file "|1" matches the solution ID in the solution ...
  74. The solution package generation failed because a required OIR.config.deploy file was not found in the source document library ...
  75. The solution upgrade file is missing. You can run the upgradesolution command without an upgrade file only if the solution ...