SQL Server 2008 R2

  1. The credentials you provided for the Reporting Services service are invalid. To continue, provide a valid account and password ...
  2. The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password ...
  3. The cryptographic signature of the package failed verification due to error 1!8.8X! "%2!s!". This occurs when the signature ...
  4. The cube already contains a Key Performance Indicator (KPI) with the specified name. Provide a different name for the KPI. ...
  5. The cube attribute with ID '%{propertyid/}' and Name '%{propertyname/}' referenced by the cube dimension '%{cubedimension/}' ...
  6. The cube cannot be browsed. Either structural changes have been made to the cube that require it to be reprocessed, or the ...
  7. The cube contains a large number of measure groups. To improve performance, consider consolidating them into fewer measure ...
  8. The cube contains a semiadditive measure '%{name/}'. The time dimension in the relevant measure group contains more than ...
  9. The cube dimension '{0}' is not included as a fact dimension in the measure group '{1}'. All fact dimensions in a measure ...
  10. The cube dimensions, '{0}' and '{1}', do not have distinct hierarchy and attribute hierarchy names. The HierarchyUniqueNameStyle ...
  11. The cube does not have a source. The Currency Conversion Wizard can only be run if a source is present in the data source ...
  12. The cube has been reprocessed on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this message, ...
  13. The cube has been updated on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this message, ...
  14. The cube will not be migrated because it contains the '{0}' dimension that is either linked or depends on linked objects. ...
  15. The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 ...
  16. The cumulative lengths of the columns specified in the exact match joins exceeds the 900 byte limit for index keys. Fuzzy ...
  17. The current action cannot be completed. The user data source credentials do not meet the requirements to run this report ...
  18. The current action cannot be completed. The user data source credentials do not meet the requirements to run this report ...
  19. The current affinity setting specifies the use of more that 64 processors. Before you use sp_configure to change affinity ...
  20. The current amount of time, in milliseconds, elapsed from when transactions are applied at the Publisher to when they are ...
  21. The current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they ...
  22. The current Analysis Services connection does not point to a valid catalog. Click the 'Connection' button on the Analyze ...
  23. The current connection does not support the cross-validation task. A connection to an Enterprise Edition instance of Analysis ...
  24. The current edition of SQL Server cannot be upgraded because some of the specified features are not supported in the SQL ...
  25. The current event was not reported to the Windows Events log. Operating system error = %1!s!. You may need to clear the Windows ...
  26. The current instance of SQL Server cannot be upgraded because it is running on a domain contoller and the service account ...
  27. The current instance of SQL Server cannot be upgraded because there are databases attached with FILESTREAM filegroups and ...
  28. The current instance of the SQL Server Analysis Services service cannot be upgraded because the Analysis Services service ...
  29. The current log shipping configuration is not functional because the required backup job cannot be found. You must drop the ...
  30. The current login '%1!s!' is not in the publication access list (PAL) of any publication at Publisher '%2!s!'. Use a login ...
  31. The current login does not have permissions to set the database owner to '{0}' The database was created successfully however. ...
  32. The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session ...
  33. The current monitor is not functional because the required alert job cannot be found. You can recreate the alert job by running ...
  34. The current node {0} is at patch level {1}], which is lower than that of active node {2}: patch level {3}]. After completing ...
  35. The current notification method is set to SQL Server, but the data source is not a SQL Server. This method is only valid ...
  36. The current notification method is set to SQL Server, but the data source is not a SQL Server. This method is only valid ...
  37. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  38. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  39. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  40. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  41. The current number of message fragments received in transport receive I/O operations that have not been enqueued (or rejected) ...
  42. The current number of message fragments that are being marshalled, or marshalled and ready to be sent via the transport layer. ...
  43. The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being ...
  44. The current package settings are not supported. Please change the SaveCheckpoints property or the TransactionOption property. ...
  45. The current restore sequence was previously interrupted during the transition to the online state. RESTORE DATABASE WITH ...
  46. The current security context cannot be reverted using this statement. A cookie may or may not be needed with 'Revert' statement ...
  47. The current security context cannot be reverted. Please switch to the original database where '%1!s!' was called and try ...
  48. The current selection contains more than one row. To run this task, please make sure that your selection contains only one ...
  49. The current selection is not valid for cross-validation. All the selected models have Key Time or Key Sequence columns. Select ...
  50. The current task requires a predictable attribute. The specified attribute, '%{Attribute/}', of the '%{Model/}' mining model ...
  51. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. ...
  52. The current tuning session has already been scheduled to run at {0}. If you choose another option, previous schedule will ...
  53. The current user %1!s! does not have SELECT permission on the table %2!s!. The user must have SELECT permission to retrieve ...
  54. The current user '%1!s!' does not have a valid linked server login mapping for non-SQL Server Publisher %2!s!]. Replication ...
  55. The current user ('%1!s!') either does not have permission to access the database specified in the parameter @execute_query_database ...
  56. The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use G ...
  57. The current user does not have sufficient permissions on the instance of SQL Server to delete the data-tier application. ...
  58. The current user does not have sufficient permissions on the instance of SQL Server to upgrade the data-tier application. ...
  59. The CurrentCube property on the Context object cannot be used since there is no available cube context. This typically occurs ...
  60. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  61. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  62. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  63. The currently selected partitions have different error configurations. Any changes made will be applied to all selected partitions. ...
  64. The currently selected partitions have different proactive cache configurations. Any changes made will be applied to all ...
  65. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  66. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  67. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  68. The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction ...
  69. The custom command name %1!s! specified for parameter %2!s! will be ignored. A system generated name will be used instead. ...
  70. The custom component shape with the Prog ID '{0}' could not be created. The designer will attempt to use the generic shape ...
  71. The custom event "%1!s!" is already declared with a different parameter list. A task is trying to declare a custom event, ...
  72. The custom property "%1!s!" cannot be specified for the aggregation type selected for this column. The comparison flags custom ...
  73. The custom stored procedure calling the format for the %1!s! command specified in the article definition does not match the ...
  74. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a CustomReportItem must have the ...
  75. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must ...