SQL Server 2016

  1. The password to use in conjunction with the logon name the report server uses to impersonate when running reports unattended. ...
  2. The passwords you typed do not match. Please ensure value provided for 'Password' field matches the value provided for 'Confirm ...
  3. The patch installer has failed to update the following instance:{0}. To determine the reason for failure, review the log ...
  4. The path '%1!s!' cannot be used for FILESTREAM files. For information about supported paths, see SQL Server Books Online. ...
  5. The path '%1!s!' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable ...
  6. The path '{0}' resolved to multiple locations. Specify a path that identifies a single provider location. This error might ...
  7. The path and file name of the workload file to use as input for tuning. Accepted formats: *.trc - SQL Server Profiler trace ...
  8. The path for item '{0}' exceeds the maximum length of {1}. The path includes the name of the item itself, plus the names ...
  9. The path for non-materialized reference dimension '%{refdimname/}' between '%{startname/}' and '%{endname/}' must exist in ...
  10. The PATH function cannot work with values such as '%{incompatvalue/}' that contain a vertical pipe ('|') because that character ...
  11. The PATH function has found the following loop '%{loop/}' in columns '%{table1/}'[%{column1/} and '%{table2/}'[%{column2/}]. ...
  12. The path name '{0}' is not valid. The path may not exist, you may not have permissions to access that folder, or the disk ...
  13. The path name for the specified SQL Server directory {0} might be on an administrative share, which is not recommended. Use ...
  14. The path of the item '{0}' is not valid. The full path must be less than {1} characters long; other restrictions apply. If ...
  15. The path of the virtual directory should be specified as a local path (for example c:\Program Files), even if the computer ...
  16. The path or file name '{0}' is not valid. The path may not exist, you may not have permissions to create a file in that folder, ...
  17. The path specified by '%1!s!' cannot be used for a FILESTREAM container since it is contained in another FILESTREAM container. ...
  18. The path to the catalog backup file could not be determined. Integration Services might not be installed on this server, ...
  19. The path,'{0}', does not exist or is not valid for report server at '{1}'. Verify that the path is valid on the report server ...
  20. The PathName property contains the fully qualified path to the service binary file that implements the service. Example: ...
  21. The paths must refer to disks that are local to the Distributor and begin with a local drive letter and colon (for example, ...
  22. The paths to the data and log folders must refer to drives that are local to the secondary server. The paths must begin with ...
  23. The paths to the distribution database folder and transaction log folder must refer to drives that are local to '{0}'. The ...
  24. The PauseService method attempts to place the service in the paused state. It returns an integer value of 0 if the PauseService ...
  25. The peer-to-peer topology has conflict detection enabled. To add a new node into the topology, the version must be SQL Server ...
  26. The percentage of 1 MB regions of pages that have high logical fragmentation. This will be '0.00 %' for index type 'Heap.' ...
  27. The percentage of identity values to use before assigning a new range. The value must be greater than or equal to 1 and less ...
  28. The performance counter registry hive is corrupted. To continue, you must repair the performance counter registry hive. For ...
  29. The PERIODICITY_HINT parameter for the mining model, '%{modelname/}', is not valid. PERIODICITY_HINT should be {n1, n2, n3.}, ...
  30. The permission '%1!s!' is not supported in this version of SQL Server. Alternatively, use the %2!s! level '%3!s!' permission. ...
  31. The plug-in assembly '%{plugin/}' raised the following exception when processing '%{event/}' event. %1[%{exception/}%]%[;%{exceptioninner/}%] ...
  32. The PMM log for database '%1!s!' is not valid. This error may indicate data corruption. Restore from backup if the problem ...
  33. The PMML-based '%{name/}' mining structure can only be altered for adding bindings to data. No other options for altering ...
  34. The point around which the needle rotates. The coordinates are in percent of the Gauge's width or height, whichever is smaller. ...
  35. The point index n ({0}) passed to STPointN is less than 1. This number must be greater than or equal to 1 and less than or ...
  36. The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements only. Omit the clause ...
  37. The policy '{0}' will not be evaluated because it references a condition whose evaluation includes executing T-SQL or WQL ...
  38. The policy for '{0}' user or group is not valid. The role assignment is either empty, specifies a user or group name that ...
  39. The PollBegin request succeeded after %1!d! retries: 'Snapshot too old' errors encountered = %2!d!; 'Cannot Serialize Transaction' ...
  40. The PollBegin request was unable to determine a consistent set of changes and the retry maximum has been exceeded: Total ...
  41. The PolyBase feature must be installed on the server instance {0}' before you can create a PolyBase group on this instance. ...
  42. The Polygon input is not valid because the exterior ring does not have enough points. Each ring of a polygon must contain ...
  43. The Polygon input is not valid because the interior ring number {0} does not have enough points. Each ring of a polygon must ...
  44. The Polygon input is not valid because the ring number {0} does not have enough points. Each ring of a polygon must contain ...
  45. 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 ...
  46. The Polygon input is not valid because the start and end points of the interior ring number {0} are not the same. Each ring ...
  47. 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 ...
  48. The Pools table does not exist in FILESTREAM blob store . The data is corrupted. Restore from backup or reinstall the blob ...
  49. The port number, %1!s!, that is specified is invalid. Valid port numbers range from 1 to 65535, inclusive. Select a port ...
  50. The port specified in the connection string is not valid. The ConnectionString format is ServerName:Port. Port should be ...
  51. The posList element provided has {0} coordinates. The number of coordinates in a posList element must be an even number. ...
  52. The Power View field name is not valid. To create a Power View report, use data that is organized as a list with labeled ...
  53. The PowerPivot Configuration Tool uses default values for an initial configuration. The server farm account is used to provision ...
  54. The PowerPivot field list cannot be loaded. The PowerPivot field list customization has been corrupted or is missing. Try ...
  55. The PowerPivot Management Data.xlsx file is not being updated. This workbook stores internal data used by the PowerPivot ...
  56. The PowerPivot service application failed to write query request information to the PowerPivot service application database. ...
  57. The PowerPivot service application identity must have Analysis Services system administrator permissions on the local SQL ...
  58. The PowerPivot service application identity must have Analysis Services system administrator permissions on the local SQL ...
  59. The PowerPivot workbook could not be imported. The service account for the workspace database server does not have permission ...
  60. The precision %1!u! specified for column %2!Iu! is out of the valid range of 1 to %3!d!. InMemory Rowset creation failed. ...
  61. The predicate was not added to the security policy '%1!s!' because there are no available predicate IDs. Drop and recreate ...
  62. The predictable column has not been mapped. Open the column mapping editor and connect a column in the input table to the ...
  63. The PredictAdjustedProbability function returns the adjusted probability value for either the most likely or specified value. ...
  64. The PredictHistogram function returns a table that contains the statistics for all states of a predictable column. The table ...
  65. The PredictHistogram function returns a table that contains the statistics for cluster membership of the input case. The ...
  66. The prediction calculator is generated in a new spreadsheet, together with accuracy diagrams and a suggested score threshold. ...
  67. The prediction calculator is generated in a stand-alone spreadsheet, ready to be printed. The layout favors operating the ...
  68. The prediction flags, REPLACE_MODEL_CASES and EXTEND_MODEL_CASES, cannot be used to query against the '%{Name/}' model because ...
  69. The PREDICTION JOIN query against the '%{Name/}' model is not supported because there are references to both aggregates and ...
  70. The PredictSequence function returns a sequence of events that is n steps long (one if not specified) based on the input ...
  71. The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the ...
  72. The prepared statement handle %1!s! is not valid in this context. Please verify that current database, user default schema, ...
  73. The Preview Page could be not loaded. If you contact Microsoft support about this error, provide the following message: {0} ...
  74. The preview sample contains embedded text qualifiers ({0}). The flat file parser does not support embedding text qualifiers ...
  75. The preview shows the source file divided into the specified columns. Initial data rows that are skipped when the file is ...