SQL Server 2012

  1. The REporting Services WMI provider is loaded. Please close all running application on any machine that connect to the WMI ...
  2. The republisher does not have a range of identity values from the root Publisher '%1!s!' that it can assign to its Subscribers. ...
  3. The republisher does not have a range of identity values from the root Publisher that it can assign to its Subscribers. Run ...
  4. The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range. ...
  5. The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range. ...
  6. The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs ...
  7. The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request ...
  8. The request has timed out. This error can occur when the timeout specified was too short, or a connection to the server or ...
  9. The request ID (or logical connection ID). A value of 0 indicates the default batch in a non-MARS (multiple active result ...
  10. The request that was sent to the IIS server was greater than 4 GB, which is not supported. Try using a smaller value for ...
  11. The requested %1!s! index on column '%2!s!' of table '%3!s!' could not be created because the column type is not %4!s! . ...
  12. The requested change to the login's membership in the Utility Reader role has failed. See exception details for more information. ...
  13. The requested changes for policy evaluation settings of volatile resources have failed. See exception details for more information. ...
  14. The requested control code cannot be sent to the service because the state of the service (Win32_BaseService:State) is equal ...
  15. The requested list could not be retrieved because the query is not valid or a connection could not be made to the data source. ...
  16. The requested OLE DB provider %2!s! is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode. ...
  17. The requested OLE DB provider %2!s! is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. ...
  18. The requested operation cannot be performed. Another operation, such as deployment or processing, may be in progress. Verify ...
  19. The requested operation cannot proceed because the database {0} contains these unsupported objects or missing dependencies: ...
  20. The requested operation could not be performed because OLE DB provider "%1!s!" for linked server "%2!s!" does not support ...
  21. The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication ...
  22. The requested protection level does not match the instance's required data protection level for administrative operations. ...
  23. The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%1!s! ...
  24. The requested type of validation is not supported when replicating between '%1' %2 and '%3' %4. Change to a supported type ...
  25. The required .svc handler mappings are not installed in IIS. For more information, see http://go.microsoft.com/fwlink/?LinkId=226284. ...
  26. The required components for the 32-bit edition of Integration Services cannot be found. Run SQL Server Setup to add the required ...
  27. The required components for the 64-bit edition of Integration Services cannot be found. Run SQL Server Setup to install the ...
  28. The required IACCEPTLICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you acknowledge that ...
  29. The required IACCEPTSQLLOCALDBLICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you acknowledge ...
  30. The required IACCEPTSQLNCLILICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you acknowledge ...
  31. The required version of .the NET Framework is not installed. The client library and maintainer require .NET Framework 2.0. ...
  32. The reservation for the HTTP namespace (%1!s!) has been deleted. If there are any endpoints associated with this namespace, ...
  33. The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%1!s!' resolver. ...
  34. The resolver information was specified without specifying the resolver to be used for article '%1!s!'. The default resolver ...
  35. The resource database has been detected in two different locations. Attaching the resource database in the same directory ...
  36. The resource database version is %1!s! and this server supports version %2!s!. Restore the correct version or reinstall SQL ...
  37. The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %1!s! including ...
  38. The response '{0}' returned from the chainer retry notification channel is invalid. Valid values are 'Cancel' and 'Retry'. ...
  39. The restart-checkpoint file '%1!s!' could not be opened. Operating system error '%2!s!'. Correct the problem, or reissue ...
  40. The restart-checkpoint file '%1!s!' could not be opened. Operating system error '%2!s!'. Make the file available and retry ...
  41. The restart-checkpoint file '%1!s!' is from a previous interrupted RESTORE operation and is inconsistent with the current ...
  42. The restart-checkpoint file '%1!s!' was corrupted and is being ignored. The RESTORE command will continue from the beginning ...
  43. The restart-checkpoint file '%1!s!' was corrupted. The restored database can not be recovered. Restart the RESTORE sequence. ...
  44. The restart-checkpoint file '%1!s!' was not found. The RESTORE command will continue from the beginning as if RESTART had ...
  45. The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup ...
  46. The restore operation for database '{0}' did not complete because of an operating system error. This error can occur because ...
  47. The result of a binary operation was too big for the maximum size for numeric types. The operand types could not be implicitly ...
  48. The result of a unary minus (negation) operation overflowed the maximum size for result data type. The magnitude of the result ...
  49. The result of the assignment expression "%1!s!" cannot be converted to a type that is compatible with the variable that it ...
  50. The result of the binary operation "%1!s!" exceeds the maximum size for result data type "%2!s!". The magnitude of the result ...
  51. The result of the binary operation "%1!s!" on data types %2!s! and %3!s! exceeds the maximum size for numeric types. The ...
  52. The result of the column expression for column "%1!s!" is not compatible with the requested type "XML". The result must be ...
  53. The result of the expression "%1!s!" on property "%2!s!" cannot be written to the property. The expression was evaluated, ...
  54. The result of the function call "%1!s!" is too large to fit in type "%2!s!". The magnitude of the result of the function ...
  55. The result of the unary minus (negation) operation "%1!s!" exceeds the maximum size for result data type "%2!s!". The magnitude ...
  56. The result string for expression "%1!s!" may be truncated if it exceeds the maximum length of %2!d! characters. The expression ...
  57. The result, %{resultid/}, cannot be found for this session. Either the result has not been created by the KeepResult header, ...
  58. The results of the current statement cannot be stored on the server because the associated session is either unspecified ...
  59. The results of the current statement cannot be stored on the server because the current session already has a stored result. ...
  60. The ResumeService method attempts to place the service in the resumed state. It returns an integer value of 0 if the ResumeService ...
  61. The retention period for change tracking information. Change information will be retained for at least the time period that ...
  62. The retention period for the distribution database must be greater than the retention period of any existing non-merge publications. ...
  63. The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to ...
  64. The return table column "%1!s!" is not the same type as the type it was created with. Drop and recreate the module using ...
  65. The return type is determined by the type of the evaluated result of expression. If the expression result is integer, decimal, ...
  66. The return value uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier. ...
  67. The returned rows appear in the Results pane and the database server continues to retain the result set in its local memory, ...
  68. The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE FROM DATABASE_SNAPSHOT ...
  69. The ring index n ({0}) passed to STInteriorRingN is less than 1. The number must be greater than or equal to 1 and should ...
  70. The ROLAP database cannot create an index on the view for the '%{schema/}' schema, '%{table/}' table. Verify that the requirements ...
  71. The role 'DatabaseMailUserRole' does not exist in the current database. This role is required for database notifications. ...
  72. The role assignment cannot be deleted. This error occurs when you attempt to delete a role assignment that has already been ...
  73. The role assignment on the root folder cannot be deleted. At least one role assignment must be defined for the root folder ...
  74. The role for the replica '{0}' has already changed before failover. Verify the replica role, and re-run the Failover Wizard ...
  75. The Role, '%{role/}', for the RelationshipEnd is not valid because this name is a reserved word, contains one or more invalid ...