SQL Server 2008

  1. The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs ...
  2. The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request ...
  3. The request has timed out. This error can occur when the timeout specified was too short, or a connection to the server or ...
  4. The request that was sent to the IIS server was greater than 4 GB, which is not supported. Try using a smaller value for ...
  5. 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! . ...
  6. The requested control code cannot be sent to the service because the state of the service (Win32_BaseService:State) is equal ...
  7. The requested list could not be retrieved because the query is not valid or a connection could not be made to the data source. ...
  8. The requested operation cannot be performed. Another operation, such as deployment or processing, may be in progress. Verify ...
  9. The requested operation could not be performed because OLE DB provider "%1!s!" for linked server "%2!s!" does not support ...
  10. The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication ...
  11. The requested protection level does not match the instance's required data protection level for administrative operations. ...
  12. The requested type of validation is not supported when replicating between '%1' %2 and '%3' %4. Change to a supported type ...
  13. The reservation for the HTTP namespace (%1!s!) has been deleted. If there are any endpoints associated with this namespace, ...
  14. The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%1!s!' resolver. ...
  15. The resolver information was specified without specifying the resolver to be used for article '%1!s!'. The default resolver ...
  16. The resource database has been detected in two different locations. Attaching the resource database in the same directory ...
  17. The resource database version is %1!s! and this server supports version %2!s!. Restore the correct version or reinstall SQL ...
  18. The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %1!s! including ...
  19. The response '{0}' returned from the chainer retry notification channel is invalid. Valid values are 'Cancel' and 'Retry'. ...
  20. The restart-checkpoint file '%1!s!' could not be opened. Operating system error '%2!s!'. Correct the problem, or reissue ...
  21. The restart-checkpoint file '%1!s!' is from a previous interrupted RESTORE operation and is inconsistent with the current ...
  22. The restart-checkpoint file '%1!s!' was corrupted and is being ignored. The RESTORE command will continue from the beginning ...
  23. The restart-checkpoint file '%1!s!' was not found. The RESTORE command will continue from the beginning as if RESTART had ...
  24. The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup ...
  25. The result of a binary operation was too big for the maximum size for numeric types. The operand types could not be implicitly ...
  26. The result of a unary minus (negation) operation overflowed the maximum size for result data type. The magnitude of the result ...
  27. The result of the assignment expression "%1!s!" cannot be converted to a type that is compatible with the variable that it ...
  28. The result of the binary operation "%1!s!" exceeds the maximum size for result data type "%2!s!". The magnitude of the result ...
  29. The result of the binary operation "%1!s!" on data types %2!s! and %3!s! exceeds the maximum size for numeric types. The ...
  30. The result of the column expression for column "%1!s!" is not compatible with the requested type "XML". The result must be ...
  31. The result of the expression "%1!s!" on property "%2!s!" cannot be written to the property. The expression was evaluated, ...
  32. 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 ...
  33. The result of the unary minus (negation) operation "%1!s!" exceeds the maximum size for result data type "%2!s!". The magnitude ...
  34. The result string for expression "%1!s!" may be truncated if it exceeds the maximum length of %2!d! characters. The expression ...
  35. The result, %{resultid/}, cannot be found for this session. Either the result has not been created by the KeepResult header, ...
  36. The results of the current statement cannot be stored on the server because the associated session is either unspecified ...
  37. The results of the current statement cannot be stored on the server because the current session already has a stored result. ...
  38. The ResumeService method attempts to place the service in the resumed state. It returns an integer value of 0 if the ResumeService ...
  39. The retention period for change tracking information. Change information will be retained for at least the time period that ...
  40. The retention period for the distribution database must be greater than the retention period of any existing non-merge publications. ...
  41. The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to ...
  42. The return table column "%1!s!" is not the same type as the type it was created with. Drop and recreate the module using ...
  43. The return type is determined by the type of the evaluated result of expression. If the expression result is integer, decimal, ...
  44. The return value uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier. ...
  45. The returned rows appear in the Results pane and the database server continues to retain the result set in its local memory, ...
  46. The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE FROM DATABASE_SNAPSHOT ...
  47. The ring index n ({0}) passed to STInteriorRingN is less than 1. The number must be greater than or equal to 1 and should ...
  48. The ROLAP database cannot create an index on the view for the '%{schema/}' schema, '%{table/}' table. Verify that the requirements ...
  49. The role assignment cannot be deleted. This error occurs when you attempt to delete a role assignment that has already been ...
  50. The role assignment on the root folder cannot be deleted. At least one role assignment must be defined for the root folder ...
  51. The roll forward start point is now at log sequence number (LSN) %1!s!. Additional roll forward past LSN %2!s! is required ...
  52. The root component associated with '{0}' ('{1}') does not match the original root component ('{2}'). Check to make sure that ...
  53. The root node name of the query trace retrieval operation has the value '%{nodename/}', which does not correspond to any ...
  54. The row filter for the table, '%{table/}', of the mining model , '%{model/}' , is invalid. The specified filter expression ...
  55. The rowset does not contain any column with offset %1!s!. Back up the publication database and contact Customer Support Services. ...
  56. The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last ...
  57. The rule '{0}' has no ExpressionXml defined, and the ExpressionGeneratorType is not defined. The ExpressionGeneratorType ...
  58. The rule '{0}' has no ExpressionXml defined, but the element is optional only for Comparison type rules. For all other rules ...
  59. The rule '{0}' is defined as a cluster comparison, but the ExpressionXml element was specified. This element is not allowed ...
  60. The rule cannot determine whether Windows Firewall is enabled. Any access from a remote computer will be blocked if a firewall ...
  61. The rule cannot verify Internet access on this version of Windows. There might be delays in starting a .NET application like ...
  62. The runtime connection manager with the ID "%1!s!" cannot be found. Verify that the connection manager collection has a connection ...
  63. The runtime connection manager with the ID %1!s! cannot be found. Verify that the connection manager collection has a connection ...
  64. The runtime object cannot be loaded from the specified XML node. This happens when trying to load a package or other object ...
  65. The same column(s) of the same row was updated at both '%1' and '%2'. The resolver chose the update from '%3' as the winner. ...
  66. The SaveToSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
  67. The scalar values property for the {2} of the {0} {1}' is set to true. Scalar cannot be true if the axis has more than one ...
  68. The scalar values property for the {2} of the {0} {1}' is set to true. Scalar cannot be true if the dynamic grouping has ...
  69. The scalar values property for the {2} of the {0} {1}' is set to true. Therefore the specified label expression will be ignored. ...
  70. The scale %1!u! exceeded the maximum limit of 7 for time/datetime2/datetimeoffset column %2!Iu!. InMemory Rowset creation ...
  71. The schedule '{0}' already exists and cannot be created or renamed. This error occurs when the schedule name is not unique. ...
  72. The schedule '{0}' at the Share Point site '{1}' already exists and cannot be created or renamed. This error occurs when ...
  73. The schedule '{0}' cannot be found. The schedule identifier that is provided to an operation cannot be located in the report ...
  74. The schedule was not attached to the specified job. The schedule owner and the job owner must be the same or the operation ...
  75. The schema at the Publisher (version: %2!d! and guid: '%1') does not match the schema at the Subscriber (version: %4!d! and ...