SQL Server 2008 R2

  1. The replication agent job '%1!s!' was not removed because it has a non-standard name; manually remove the job when it is ...
  2. The replication agent process failed to obtain license information from one of the servers in the replication topology. Ensure ...
  3. The replication agent responded to a shutdown/cancel request and has been stopped. See the previous job step history message ...
  4. The Replication Conflict Viewer is not registered on '%1', or %9 could not retrieve information about the Viewer from the ...
  5. The replication Merge Agent failed to change metadata on one or more database objects at the Subscriber when applying the ...
  6. The replication Merge Agent failed to propagate a Publisher schema change to the Subscriber. When troubleshooting, restart ...
  7. The replication Merge Agent failed to retrieve subscription partitioning information from the Publisher. When troubleshooting, ...
  8. The replication settings on SQL Server version 6.0 cannot be upgraded directly to SQL Server 2000. You must first upgrade ...
  9. The replication upgrade task was not able to completely transfer your existing replication configuration settings to SQL ...
  10. The report '{0}' cannot be opened because no data source is associated with it. Associate a model data source with this report ...
  11. The report '{0}' cannot be opened because the data source '{1}' associated with it is not a report model. This report was ...
  12. The report '{0}' cannot be opened because you do not have permission to access the data source: '{0}'. Contact your administrator. ...
  13. The report '{0}' contains a reference to a data source that is not valid. Verify that the shared data sources and models ...
  14. The report '{0}' contains a reference to a dataset that is not valid. Verify that the shared datasets that are required for ...
  15. The report '{0}' is in an earlier report format and must be automatically upgraded before opening it in Report Builder 3.0. ...
  16. The Report Builder launch URL is not valid. It can be an absolute or relative URL and must include the .application file ...
  17. The report cannot be rendered. A filter is required to prevent too much data from being returned. Add a filter to your report. ...
  18. The report contains an embedded image with an invalid name {1}'. Embedded image names must be CLS-Compliant identifiers. ...
  19. The report contains an invalid data source with the name {1}'. Data source names must be greater than 0 and less than or ...
  20. The report contains an invalid embedded image name, {1}'. Embedded image names must be greater than 0 and less than or equal ...
  21. The report contains more than one report section, which is not supported in SQL Server 2008 Reporting Services. Either reduce ...
  22. The report contains more than one report section, which is not supported in SQL Server 2008 Reporting Services. The {0} extra ...
  23. The report contains references to one or more assemblies and RDLSandboxing has been enabled for local preview. Remove the ...
  24. The report data source '{0}' refers to shared data source '{1}' that was not found or a connection could not be established. ...
  25. The report data source object must be of the type System.Data.DataTable, System.Collections.IEnumerable, or System.Web.UI.IDataSource. ...
  26. The report data source object must be of the type System.Data.DataTable, System.Collections.IEnumerable, System.Windows.Forms.BindingSource, ...
  27. The Report Definition Customization Extension (RDCE) name that is specified in the report does not match the RDCE name that ...
  28. The Report Definition Customization Extension (RDCE) returned a different RDL version than it was originally passed. The ...
  29. The Report Definition Customization Extension (RDCE) returned a null or invalid RDL. Make sure that the RDL contains valid ...
  30. The report definition element '{0}' is empty at line {2}, position {3}. It is missing a mandatory child element of type '{1}'. ...
  31. The report definition is not valid or supported by this version of Reporting Services. This could be the result of publishing ...
  32. The report definition is not valid. Please verify that the report definition uses the current report definition {2} (i.e. ...
  33. The report had been updated in SharePoint site and has not synced to Report Server. Please sync it first from SharePoint ...
  34. The Report Manager virtual directory name is not configured. To configure the directory, enter a name or use the default ...
  35. The report parameter {1}' has a DefaultValue or a ValidValue that depends on the report parameter "{3}". Forward dependencies ...
  36. The report parameter {1}' has a DefaultValue that has a Values collection containing more than one value. For single-value ...
  37. The report parameter {1}' has a DefaultValue that has both or neither of the following: Values and DataSetReference. DefaultValue ...
  38. The report parameter {1}' has a ValidValues that has both or neither of the following: ParameterValues and DataSetReference. ...
  39. The report part '{0}' ComponentId='{1}' will not be deployed because it no longer exists in the report. To refresh the list ...
  40. The report part to be updated is in the page header or page footer, and the report part definition from the report server ...
  41. The report preview failed because the report could not be built. Read the errors, warnings, and messages in the Error List ...
  42. The report query processor stopped the query to free system resources. Run the query again to see more rows in the result ...
  43. The report server at '{0}' is an earlier version than the one specified in the TargetServerVersion property. The RDL files ...
  44. The report server at '{0}' is running SQL Server version {1}.{2}, which is incompatible with SQL Server 2008 R2 Business ...
  45. The report server at {0}' is not compatible with this version of Report Builder. Specify a URL to a SQL Server 2008 R2 report ...
  46. The report server cannot access settings in the SharePoint configuration database. Most likely, the Windows SharePoint Services ...
  47. The report server cannot access the private key for the service account. This key is used to decrypt the symmetric key that ...
  48. The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server ...
  49. The report server cannot decrypt the symmetric key. Most likely, the service account or password has changed. To continue, ...
  50. The report server cannot open a connection to the report server database. A connection to the database is required for all ...
  51. The report server cannot process the report or shared dataset. The shared data source '{0}' for the report server or SharePoint ...
  52. The report server cannot start. One or more configuration files are not valid. Check the log files for more information. ...
  53. The report server cannot start. One or more configuration files are not valid. Check the log files for more information. ...
  54. The report server configuration file specifies localhost for the Web server name. The report server requires that the computer ...
  55. The report server could not transmit the file because the file {0} is not installed or you do not have the correct permissions ...
  56. The report server database is hosted on a supported version of the Database Engine. The database can be upgraded to the format ...
  57. The report server database is hosted on a version of the Database Engine that is not supported by a SQL Server 2008 Reporting ...
  58. The report server has detected a possible denial of service attack. The report server is dropping requests for service from ...
  59. The report server has not been configured for SharePoint integrated mode. Use Reporting Services Configuration Manager to ...
  60. The report server has RDLSandboxing enabled and the array returned by the {2} expression or an expression parameter for the ...
  61. The report server has RDLSandboxing enabled and the class instance '{1}' contains a type '{2}' that is not allowed or the ...
  62. The report server has RDLSandboxing enabled and the report contains a reference to assembly '{3}' that cannot be loaded. ...
  63. The report server has RDLSandboxing enabled and the report contains custom code. Remove the Code element from the report ...
  64. The report server has RDLSandboxing enabled and the resource specified by the {2} expression for the {0} '{1}' exceeds the ...
  65. The report server has RDLSandboxing enabled and the string returned by the {2} expression or an expression parameter for ...
  66. The report server has RDLSandboxing enabled and the {2} expression for the {0} '{1}' contains a reference to a type, namespace, ...
  67. The report server has RDLSandboxing enabled and the {2} expression for the {0} '{1}' contains a syntax error. Change the ...
  68. The report server has RDLSandboxing enabled and the {2} expression for the {0} '{1}' contains the New operator for the type ...
  69. The report server has RDLSandboxing enabled and the {2} expression for the {0} '{1}' exceeds the maximum character limit ...
  70. The report server instance is not configured correctly. Please use the Reporting Services Configuration tool to create a ...
  71. The report server instance supports SharePoint integration, but it currently runs in native mode. If you want to integrate ...
  72. The report server is configured to use one or more extensions that were deprecated in a previous release. Upgrade can continue, ...
  73. The report server is running under the built-in {0} account, which is not supported by a SharePoint farm installation. Please ...
  74. The report server is unable to create the list of valid values for one or more report parameters. If the values list is retrieved ...
  75. The report server to which you are connecting has returned an SSL certificate that is not valid. The server might not be ...