SQL Server 2012

  1. The object is in a zombie state. An object may enter a zombie state when either ITransaction::Commit or ITransaction::Abort ...
  2. The object model cannot be used since there is no available session context. This typically occurs because the AdomdServer ...
  3. The object model does not accept the calls from non-server threads. This typically occurs because the AdomdServer object ...
  4. The object name '{0}' is not unique. You must use a fully-qualified name, in the format '[module_guid].package_name.object_name'. ...
  5. The object name '{0}' is not valid. The name cannot start or end with whitespace and it cannot contain any of the following ...
  6. The object name cannot be changed from "%1!s!" to "%2!s!" because another object in the collection already uses that name. ...
  7. The object referenced as '%1!s!' resolves differently in the target metadata collation '%2!s!' than in the current metadata ...
  8. The object type for parameter {0} is not valid. Valid object type values are 20 (project), 30 (package), or 50 (execution). ...
  9. The object with ID "{0}" referred by to a ForEachPropertyMapping is not a ForEach Loop container. The offending ForEachPropertyMapping ...
  10. The object with ID of '%{id/}', Name of '%{name/}' is of type '%{typename/}' which does not support the requested operation. ...
  11. The object {0} is not found in Dependency Services catalog. Please contact the Dependency Services admin and confirm that ...
  12. The ObjectData element is missing in the XML block of a hosted object. This occurs when the XML parser attempts to locate ...
  13. The objects "%1!s!" and "%2!s!" in the FROM clause have the same exposed names. Use correlation names to distinguish them. ...
  14. The OLAP binding of the '%{column/}' nested table should reference the same cube as the binding of the '%{struct/}' mining ...
  15. The OLAP Cube-based mining structure or model, %{name/}, cannot be processed with out-of-line bindings (e.g. the INSERT INTO ...
  16. The OLE Automation extended stored procedures (XPs) allow Transact-SQL batches, stored procedures, and triggers to reference ...
  17. The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact ...
  18. The OLE DB provider "%1!s!" for linked server "%2!s!" could not set the range for table "%3!s!" because of column "%4!s!". ...
  19. The OLE DB provider "%1!s!" for linked server "%2!s!" could not set the range for table "%3!s!". %4!s!. For possible cause ...
  20. The OLE DB provider "%1!s!" for linked server "%2!s!" does not contain the table "%3!s!". The table either does not exist ...
  21. The OLE DB provider "%1!s!" for linked server "%2!s!" reported a change in schema version between compile time ("%3!s!") ...
  22. The OLE DB provider "%1!s!" for linked server "%2!s!" reported different metadata at run time for table "%3!s!", column "%4!s!". ...
  23. The OLE DB provider "%1!s!" for linked server "%2!s!" returned a "%3!s!" index "%4!s!" with the incorrect bookmark ordinal ...
  24. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata for a column. The column "%3!s!" (compile-time ...
  25. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata for a column. The name was changed at ...
  26. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata. An extra column was supplied during ...
  27. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata. The object "%3!s!" was missing the ...
  28. The OLE DB provider "%1!s!" for linked server "%2!s!" supports column level collation, but failed to provide collation data ...
  29. The OLE DB provider "%1!s!" for linked server "%2!s!" supports column level collation, but failed to provide the metadata ...
  30. The OLE DB provider '%1!s!' for linked server '%2!s!' provided invalid collation. LCID = %3!s!, Compflags = %4!s!, SortOrder ...
  31. The OLE DB provider used by the OLE DB adapter does not support IConvertType. Set the adapter's ValidateColumnMetaData property ...
  32. The OLE DB Provider {0} is not installed or is not valid. Do you want to reset the connection string? If you click OK, the ...
  33. The ON clause at line %d{Line/}, column %d{Column/}, is not valid. Columns specified in the ON clause must be scalar, and ...
  34. The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online. ...
  35. The online restore to database '%1!s!' failed. It may be appropriate to perform an offline restore instead. An offline restore ...
  36. The online restore to database '%1!s!' failed. It may be appropriate to perform an offline restore instead. To force an offline ...
  37. The only configurable property for a cached HOLAP object is Silence Interval, which must be specified as zero or greater. ...
  38. The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. ...
  39. The OPENROWSET and OPENDATASOURCE functions support ad hoc connections to remote data sources without linked or remote servers. ...
  40. The OPENROWSET and OPENDATASOURCE functions support ad hoc connections to remote data sources without linked or remote servers. ...
  41. The operating system does not support Channel Bindings, but the server is configured to require Extended Protection. Update ...
  42. The operating system does not support Service Bindings, but the server is configured to require Extended Protection. Update ...
  43. The operating system on this computer does not meet the minimum requirements for SQL Server 2012. For Windows Vista or Windows ...
  44. The operating system returned error %1!s! to SQL Server during a %2!s! at offset %3!s! in file '%4!s!'. Additional messages ...
  45. The operating system returned error 5 (ACCESS_DENIED) while creating an ETW tracing session. ErrorFormat: Ensure that the ...
  46. The operation cannot be completed because the current user does not have sufficient permissions on the SQL Azure logical ...
  47. The operation cannot be completed because the file extension is either missing or it is not valid. Valid file extensions ...
  48. The operation cannot be completed because the memory quota estimate (%d{Request/}MB) exceeds the available system memory ...
  49. The operation cannot be executed since the database folder '%{dir_name/}' for the database with the name of '%{db_name/}', ...
  50. The operation cannot be executed since the database with the name of '%{db_name/}', ID of '%{db_id/}' already exists in the ...
  51. The operation cannot be performed because another operation is in progress. Please wait for the other operation to complete ...
  52. The operation cannot be performed on database "%1!s!" because it is involved in a database mirroring session or an availability ...
  53. The operation cannot be started because the user is not a member of the database role, '%1!s!', or the server role, '%2!s!'. ...
  54. The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that ...
  55. The operation cannot continue because the application name in the package file does not match the application name of the ...
  56. The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin ...
  57. The operation caused a FileTable check constraint error. A directory entry cannot have a data stream associated with the ...
  58. The operation caused a FileTable check constraint error. A file entry cannot have a NULL value for the data stream associated ...
  59. The operation could not be completed. The specified '%1!s!' value, %2!s!, causes the sum of minimums on all resource pools ...
  60. The operation could not be completed. The specified '%1!s!' value, %2!s!, causes the sum of minimums on all workload groups ...
  61. The operation could not be performed because OLE DB provider "%1!s!" for linked server "%2!s!" was unable to begin a distributed ...
  62. The operation factory '{1}' defined for the operation type '{0}' does not match the operation factory type '{2}' found in ...
  63. The operation failed because of another operation in progress. Please wait for other operations to complete and try again. ...
  64. The operation failed because the source database does not exist, the source table does not exist, or because you do not have ...
  65. The operation failed because the source does not contain the requested column. You can fix this problem by updating the column ...
  66. The operation failed because the Windows SharePoint Services object model is not installed on the report server. Install ...
  67. The operation failed because the Windows SharePoint Services object model is not installed on the report server. Install ...
  68. The operation has been cancelled because there is not enough memory available for the application. If using a 32-bit version ...
  69. The operation is not valid because of the current state of the object. You can use the FetchAllProperties method to retrieve ...
  70. The operation of synchronizing changed dependencies of the extraction point "{0}", failed with the following message: "{1}". ...
  71. The operation on '%{name/}' %{typename/} cannot be completed since it creates ambiguous relationship between reference dimensions ...
  72. The operation on '%{name/}' %{typename/} cannot be completed since it creates ambiguous relationship between reference tables ...
  73. The operation on FileTable system defined object '%1!s!' was allowed because of traceflag settings. To prevent this informational ...
  74. The operation on object '%1!s!' is blocked. The object is a FileTable system defined object and user modifications are not ...
  75. The operation, ID {0}, has started. For information about package executions and validations, open the Integration Services ...