SQL Server 2012

  1. The policy '{0}' will not be evaluated because it references a condition whose evaluation includes executing T-SQL or WQL ...
  2. The policy for '{0}' user or group is not valid. The role assignment is either empty, specifies a user or group name that ...
  3. The PollBegin request succeeded after %1!d! retries: 'Snapshot too old' errors encountered = %2!d!; 'Cannot Serialize Transaction' ...
  4. The PollBegin request was unable to determine a consistent set of changes and the retry maximum has been exceeded: Total ...
  5. The Polygon input is not valid because the exterior ring does not have enough points. Each ring of a polygon must contain ...
  6. The Polygon input is not valid because the interior ring number {0} does not have enough points. Each ring of a polygon must ...
  7. The Polygon input is not valid because the ring number {0} does not have enough points. Each ring of a polygon must contain ...
  8. The Polygon input is not valid because the start and end points of the exterior ring are not the same. Each ring of a polygon ...
  9. The Polygon input is not valid because the start and end points of the interior ring number {0} are not the same. Each ring ...
  10. The Polygon input is not valid because the start and end points of the ring number {0} are not the same. Each ring of a polygon ...
  11. The Pools table does not exist in FILESTREAM blob store . The data is corrupted. Restore from backup or reinstall the blob ...
  12. The port number, %1!s!, that is specified is invalid. Valid port numbers range from 1 to 65535, inclusive. Select a port ...
  13. The port specified in the connection string is not valid. The ConnectionString format is ServerName:Port. Port should be ...
  14. The posList element provided has {0} coordinates. The number of coordinates in a posList element must be an even number. ...
  15. The PowerPivot Configuration Tool uses default values for an initial configuration if they are available. The server farm ...
  16. The PowerPivot field list cannot be loaded. The PowerPivot field list customization has been corrupted or is missing. Try ...
  17. The PowerPivot Management Data.xlsx file is not being updated. This workbook stores internal data used by the PowerPivot ...
  18. The PowerPivot service application failed to write query request information to the PowerPivot service application database. ...
  19. The PowerPivot service application identity must have Analysis Services system administrator permissions on the local SQL ...
  20. The precision %1!u! specified for column %2!Iu! is out of the valid range of 1 to %3!d!. InMemory Rowset creation failed. ...
  21. The predictable column has not been mapped. Open the column mapping editor and connect a column in the input table to the ...
  22. The PredictAdjustedProbability function returns the adjusted probability value for either the most likely or specified value. ...
  23. The PredictHistogram function returns a table that contains the statistics for all states of a predictable column. The table ...
  24. The PredictHistogram function returns a table that contains the statistics for cluster membership of the input case. The ...
  25. The prediction calculator is generated in a new spreadsheet, together with accuracy diagrams and a suggested score threshold. ...
  26. The prediction calculator is generated in a stand-alone spreadsheet, ready to be printed. The layout favors operating the ...
  27. The prediction flags, REPLACE_MODEL_CASES and EXTEND_MODEL_CASES, cannot be used to query against the '%{Name/}' model because ...
  28. The PREDICTION JOIN query against the '%{Name/}' model is not supported because there are references to both aggregates and ...
  29. The PredictSequence function returns a sequence of events that is n steps long (one if not specified) based on the input ...
  30. The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the ...
  31. The prepared statement handle %1!s! is not valid in this context. Please verify that current database, user default schema, ...
  32. The Preview Page could be not loaded. If you contact Microsoft support about this error, provide the following message: {0} ...
  33. The preview sample contains embedded text qualifiers ({0}). The flat file parser does not support embedding text qualifiers ...
  34. The preview shows the source file divided into the specified columns. Initial data rows that are skipped when the file is ...
  35. The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider ...
  36. The primary key constraint '%1!s!' on table '%2!s!' cannot be dropped because change tracking is enabled on the table. Change ...
  37. The primary key for '%1!s!.%2!s!' has %3!s! columns. SQL Server supports a maximum of %4!s! columns. Redefine the primary ...
  38. The primary key for source table "%1!s!" includes the timestamp column "%2!s!". Cannot create the article for the specified ...
  39. The primary key or unique constraint cannot be changed until its existing relationships are deleted. Do you want to delete ...
  40. The primary key or unique constraint cannot be changed while relationships to the existing primary key or unique constraint ...
  41. The primary/foreign key combination doesn't match for relationship object '%{relid/}' and preferred path between '%{FKTable/}' ...
  42. The PrimeOutput method on "%1!s!" returned success, but did not report an end of the rowset. There is an error in the component. ...
  43. The principal and mirror server instances cannot be the same instance of SQL Server. Select another instance as the mirror ...
  44. The principal and witness server instances cannot be the same instance of SQL Server. Select another instance as the witness ...
  45. The principal cannot be updated because the principal identifier is not valid. The identifier must have an existing GUID, ...
  46. The principal copy of the '%1!s!' database encountered error %2!s!, status %3!s!, severity %4!s! while sending page %5!s! ...
  47. The private key for the security certificate bound to the database principal (ID %1!s!) is password protected. Password protected ...
  48. The proactive caching object of the '%{dimension/}' MOLAP dimension does not have a finite duration for the silence interval, ...
  49. The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the ...
  50. The process could not load the Merge Replication Provider for '%1'. Check to see if the component is registered correctly. ...
  51. The process failed to complete last batch in multi-streaming mode, it has been reset to single connection mode and is retrying ...
  52. The process has successfully completed retrying failed multi-streaming operation in single connection mode, %2!d! transaction(s) ...
  53. The process may take some time depending on the amount of data. If target table already contains any data, it will be lost ...
  54. The Process operation cannot be performed. If you are currently deploying or building your project, please wait until the ...
  55. The process operation ended because the number of errors encountered during processing reached the defined limit of allowable ...
  56. The ProcessAdd specified for the %{name/} %{typename/} is not valid for IMDI dimensions if that dimension is associated with ...
  57. The processing of {2} for the {0} {1}' cannot be performed. Cannot compare data of types {3} and {4}. Please check the data ...
  58. The processing of {2} for the {0} {1}' cannot be performed. The comparison failed. Please check the data type returned by ...
  59. The ProductFeatureScenarioCondition element cannot be the root element of a document, it can only be used as the child of ...
  60. The profile request "{0}" has invalid property "{1}". Correct it or remove the request to proceed. The detailed error is: ...
  61. The profiling configuration has been changed by another user, Your changes cannot be saved. The new settings are about to ...
  62. The project cannot be debugged because no starting model is specified. In the Project Menu, select Properties and enter a ...
  63. The project cannot be debugged because no starting report is specified. In the Project Menu, select Properties and enter ...
  64. The project cannot be deployed because it is missing a required value. For a report server that runs in SharePoint integrated ...
  65. The project cannot be deployed because no target server is specified. Provide a value for the TargetServerURL property in ...
  66. The project cannot be saved because it does not pass consistency check. Use the Events object to get more detailed errors ...
  67. The Project Connection Manager "%1" is not accessible inside this package because a connection manager declared in the package ...
  68. The project contains unpublished data learned in the last correction execution. Changing the data source mapping will cause ...
  69. The project contains unpublished data learned in the last matching execution. Changing the data source mapping will cause ...
  70. The project contains unsaved correction data from the last data correction activity. Running data correction will cause all ...
  71. The project could not be deployed due to missing parameters. Please make sure all values have been specified on the command ...
  72. The project could not be deployed to the '{1}' server because of the following connectivity problems : {0} To verify or update ...
  73. The project deployment failed with the following message: {0}. Please see the server log for further details. Operation ID: ...
  74. The project file consists of option settings and a meta-database of source and target databases. Saving the meta-database ...
  75. The project has been to converted to the project deployment model, but the changes will not be saved until the project is ...