SQL Server 2008

  1. The RemoveFromSQLServer method encountered OLE DB error code 1!8.8X! (%2!s!) The SQL statement that was issued has failed. ...
  2. The Reorganize Index task defragments and compacts clustered and non-clustered indexes on tables and views. This will improve ...
  3. The Reorganize Index task defragments and compacts clustered and nonclustered indexes on tables and views. This will improve ...
  4. The replication administrative user for Oracle Publisher "%1!s!" has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql ...
  5. The replication agent completed successfully. See the previous job step history message or Replication Monitor for more information. ...
  6. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. ...
  7. The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job ...
  8. The Replication agent had detected inconsistent data in replication system table. It is possible that an article was added ...
  9. The replication agent had encounter an unexpected null '{0}' value from the database back end. Contact Technical Support. ...
  10. The replication agent had encountered an exception. Source: {0} Exception Type: {1} Exception Message: {2} Message Code: ...
  11. The replication agent had encountered an unexpected exception, a memory dump containing information about the exception has ...
  12. The replication agent had encountered at least one unhandled exception during execution. Extended error information can be ...
  13. The replication agent has not logged a progress message in %1!s! minutes. This might indicate an unresponsive agent or high ...
  14. The replication agent is being shut down because execution time for status callback handlers has exceeded the system limit ...
  15. The replication agent job '%1!s!' was not removed because it has a non-standard name; manually remove the job when it is ...
  16. The replication agent process failed to obtain license information from one of the servers in the replication topology. Ensure ...
  17. The replication agent responded to a shutdown/cancel request and has been stopped. See the previous job step history message ...
  18. The Replication Conflict Viewer is not registered on '%1', or %9 could not retrieve information about the Viewer from the ...
  19. The replication Merge Agent failed to change metadata on one or more database objects at the Subscriber when applying the ...
  20. The replication Merge Agent failed to propagate a Publisher schema change to the Subscriber. When troubleshooting, restart ...
  21. The replication Merge Agent failed to retrieve subscription partitioning information from the Publisher. When troubleshooting, ...
  22. The replication settings on SQL Server version 6.0 cannot be upgraded directly to SQL Server 2000. You must first upgrade ...
  23. The replication upgrade task was not able to completely transfer your existing replication configuration settings to SQL ...
  24. The report '{0}' cannot be opened because no data source is associated with it. Associate a model data source with this report ...
  25. The report '{0}' cannot be opened because the data source '{1}' associated with it is not a report model. This report was ...
  26. The report '{0}' cannot be opened because you do not have permission to access the data source: '{0}'. Contact your administrator. ...
  27. The report '{0}' contains a reference to a data source that is not valid. Verify that the shared data sources and models ...
  28. The Report Builder launch URL is not valid. It can be an absolute or relative URL and must include the .application file ...
  29. The Report Builder Launch URL property allows you to specify the launch URL for the Report Builder ships with SQL Server ...
  30. The report cannot be rendered. A filter is required to prevent too much data from being returned. Add a filter to your report. ...
  31. The report contains an embedded image with an invalid name {1}'. Embedded image names must be CLS-Compliant identifiers. ...
  32. The report contains an invalid data source with the name {1}'. Data source names must be greater than 0 and less than or ...
  33. The report contains an invalid embedded image name, {1}'. Embedded image names must be greater than 0 and less than or equal ...
  34. The Report Definition Customization Extension (RDCE) name that is specified in the report does not match the RDCE name that ...
  35. The Report Definition Customization Extension (RDCE) returned a different RDL version than it was originally passed. The ...
  36. The Report Definition Customization Extension (RDCE) returned a null or invalid RDL. Make sure that the RDL contains valid ...
  37. The report definition element '{0}' is empty at line {2}, position {3}. It is missing a mandatory child element of type '{1}'. ...
  38. The report definition is not valid. Please verify that the report definition uses the current report definition {2} (i.e. ...
  39. The report had been updated in SharePoint site and has not synced to Report Server. Please sync it first from SharePoint ...
  40. The Report Manager virtual directory name is not configured. To configure the directory, enter a name or use the default ...
  41. The report parameter {1}' has a DefaultValue or a ValidValue that depends on the report parameter "{3}". Forward dependencies ...
  42. The report parameter {1}' has a DefaultValue that has a Values collection containing more than one value. For single-value ...
  43. The report parameter {1}' has a DefaultValue that has both or neither of the following: Values and DataSetReference. DefaultValue ...
  44. The report parameter {1}' has a ValidValues that has both or neither of the following: ParameterValues and DataSetReference. ...
  45. The report processing log keeps a record of when every report is processed as well as information about when it was run and ...
  46. The report query processor stopped the query to free system resources. Run the query again to see more rows in the result ...
  47. The report server cannot access settings in the SharePoint configuration database. Most likely, the Windows SharePoint Services ...
  48. The report server cannot access the private key for the service account. This key is used to decrypt the symmetric key that ...
  49. The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server ...
  50. The report server cannot decrypt the symmetric key. Most likely, the service account or password has changed. To continue, ...
  51. The report server cannot open a connection to the report server database. A connection to the database is required for all ...
  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 configuration file specifies localhost for the Web server name. The report server requires that the computer ...
  54. The report server could not transmit the file because the file {0} is not installed or you do not have the correct permissions ...
  55. The report server database is hosted on a supported version of the Database Engine. The database can be upgraded to the format ...
  56. The report server database is hosted on a version of the Database Engine that is not supported by a SQL Server 2008 Reporting ...
  57. The report server has detected a possible denial of service attack. The report server is dropping requests for service from ...
  58. The report server instance is not configured correctly. Please use the Reporting Services Configuration tool to create a ...
  59. The report server instance supports SharePoint integration, but it currently runs in native mode. If you want to integrate ...
  60. The report server is configured to use one or more extensions that were deprecated in a previous release. Upgrade can continue, ...
  61. The report server is running under the built-in LocalService account and cannot connect to a remote SharePoint database. ...
  62. The report server is unable to create the list of valid values for one or more report parameters. If the values list is retrieved ...
  63. The report server to which you are connecting has returned an SSL certificate that is not valid. The server might not be ...
  64. The Report Server Web service can receive Simple Object Access Protocol (SOAP) requests and URL access requests. Enable Web ...
  65. The Report Server Web service group that is associated with this SQL Server instance will be deleted during the upgrade process. ...
  66. The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount ...
  67. The Report Server WMI provider cannot create the virtual directory. This error occurs when you call SetVirtualDirectory and ...
  68. The report snapshot '{1}' cannot be found for report '{0}'. The snapshot identifier cannot be located in the report server ...
  69. The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add {0} to the {1} ...
  70. The report was saved successfully but could not be bound to the data source. Try saving the report to the same site or server ...
  71. The Reporting Services rights were not applied properly. The user may still not have appropriate access to Reporting Services ...
  72. The republisher does not have a range of identity values from the root Publisher '%1!s!' that it can assign to its Subscribers. ...
  73. The republisher does not have a range of identity values from the root Publisher that it can assign to its Subscribers. Run ...
  74. The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range. ...
  75. The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range. ...