SQL Server 2008

  1. SQL Server Analysis Services and SQL Server must be in the same state in order to be upgraded. Both must be either stand-alone ...
  2. SQL Server Assertion: File: , line = %2!s! %3!s!. This error may be timing-related. If the error persists after rerunning ...
  3. SQL Server Assertion: File: , line = %2!s! Failed Assertion = '%3!s!' %4!s!. This error may be timing-related. If the error ...
  4. SQL Server Assertion: File: , line=%2!s! Failed Assertion = '%3!s!'. This error may be timing-related. If the error persists ...
  5. SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the ...
  6. SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to ...
  7. SQL Server Audit failed to create the audit file '%1!s!'. Make sure that the disk is not full and that the SQL service account ...
  8. SQL Server Audit failed to start, and the server is being shut down. To troubleshoot this issue, use the -m flag (Single ...
  9. SQL Server blocked access to %1!s! '%2!s!' of component '%3!s!' because this component is turned off as part of the security ...
  10. SQL Server Browser configuration failed to retrieve the feature name from action data dictionary: the key '{0}' is not present. ...
  11. SQL Server Browser configuration for feature '{0}' was cancelled by user after a previous installation failure. The last ...
  12. SQL Server cannot load database '%1!s!' because Change Data Capture is enabled. The currently installed edition of SQL Server ...
  13. SQL Server cannot load database '%1!s!' because change tracking is enabled. The currently installed edition of SQL Server ...
  14. SQL Server cannot save the Distributor password. The password will be blank until it is set using the Configure Distributor ...
  15. SQL Server cannot start because the license agreement for this '%1!s!' version of SQL Server is invalid. The server is exiting. ...
  16. SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server ...
  17. SQL Server cannot use the NO_BUFFERING option during I/O on this file, because the sector size for file '%1!s!', %2!s!, is ...
  18. SQL Server Compact Edition Subscribers cannot sync to publications that have native sync mode. Create the publication with ...
  19. SQL Server Configuration Manager provides basic configuration management for SQL Server services, server protocols, client ...
  20. SQL Server could not change the password used by this Publisher to connect to the Distributor. Do you want to continue saving ...
  21. SQL Server could not change the properties of article '{0}' based on object '{1}'. Do you want to continue saving other changes ...
  22. SQL Server could not connect to the Distributor, '{0}'. Do you want to disable publishing on '{1}' without removing entries ...
  23. SQL Server could not create article '{0}' based on object '{1}'. Do you want to continue saving other changes to the publication? ...
  24. SQL Server could not retrieve information about '{0}' and could not display the Disable Publishing and Distribution Wizard. ...
  25. SQL Server could not save the list of filtered columns in article '{0}' on table '{1}'. Do you want to continue saving changes ...
  26. SQL Server could not save the row filter for article '{0}' on table '{1}'. Do you want to continue saving changes to the ...
  27. SQL Server could not send the differential information for database file '%1!s!' of database '%2!s!\%3!s!' to the backup ...
  28. SQL Server could not spawn %1!s! thread. Check the SQL Server error log and the Windows event logs for information about ...
  29. SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears ...
  30. SQL Server could not use the NO_BUFFERING option during I/O, because the master file sector size, %1!s!, is incorrect. Move ...
  31. SQL Server detected a logical consistency-based I/O error: %1!s!. It occurred during a %2!s! of page %3!s! in database ID ...
  32. SQL Server encountered error 1!s! while communicating with full-text filter daemon host (FDHost) process. Make sure that ...
  33. SQL Server encountered one or more errors while retrieving the list of databases on '{0}'. The list of databases may not ...
  34. SQL Server encountered one or more errors while retrieving the list of Publishers using Distributor {0} and their publications. ...
  35. SQL Server encountered one or more errors while saving the properties for this Publisher. Open the property dialog box again ...
  36. SQL Server encountered one or more errors while saving the properties for this Subscriber. Open the property dialog box again ...
  37. SQL Server Enterprise Manager could not be located on this computer. Re-run Setup and make sure it is installed properly ...
  38. SQL Server error %1 has been listed as being non-alertable. Consequently alert '%2' - which would have fired - was not fired. ...
  39. SQL Server Error and Usage Reporting has encountered inconsistent configuration information or has failed on a COM interface. ...
  40. SQL Server Express does not install SQL Server Books Online. To install these Help files, download SQL Server Books Online ...
  41. SQL Server failed to communicate with filter daemon launch service (Windows error: %1!s!). Full-Text filter daemon process ...
  42. SQL Server failed to create named pipe '%1!s!' to communicate with the full-text filter daemon (Windows error: %2!s!). Either ...
  43. SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing ...
  44. SQL Server failed with error code 1!s! to spawn a thread to process a new login or connection. Check the SQL Server error ...
  45. SQL Server has encountered %1!s! occurrence(s) of cachestore flush for the '%2!s!' cachestore (part of plan cache) due to ...
  46. SQL Server has encountered %1!s! occurrence(s) of cachestore flush for the '%2!s!' cachestore (part of plan cache) due to ...
  47. SQL Server has encountered %1!s! occurrence(s) of I/O requests taking longer than %2!s! seconds to complete on file %3!s! ...
  48. SQL Server has insufficient memory to run the extended stored procedure '%1!s!'. Release server memory resources by closing ...
  49. SQL Server improves manageability and security by giving administrators more control over the surface area of local and remote ...
  50. SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, ...
  51. SQL Server installation media on a network share or in a custom folder can cause installation failure if the total length ...
  52. SQL Server is allowing new connections in response to 'continue' request from Service Control Manager. This is an informational ...
  53. SQL Server is not allowing new connections because the Service Control Manager requested a pause. To resume the service, ...
  54. SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the ...
  55. SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the ...
  56. SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. ...
  57. SQL Server is terminating because of fatal exception %1!s!. This error may be caused by an unhandled Win32 or C++ exception, ...
  58. SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message ...
  59. SQL Server is waiting for %1!s! remaining sessions and connections to close. If these sessions are not closed within a reasonable ...
  60. SQL Server Management Studio cannot display the list of article resolvers in the Article Properties dialog box because the ...
  61. SQL Server Management Studio could not be located on this computer. Re-run Setup, and make sure Workbench is installed properly ...
  62. SQL Server Management Studio encountered errors while cleaning up snapshots. Click the message link below to see the full ...
  63. SQL Server Management Studio encountered errors while generating snapshots. Click the message link below to see the full ...
  64. SQL Server Management Studio encountered errors while saving publication properties. Click the message link below to see ...
  65. SQL Server must enable your login or account for Publisher '{0}' before you can view or modify the publication properties. ...
  66. SQL Server must shut down in order to recover a database (database ID %1!s!). The database is either a user database that ...
  67. SQL Server native HTTP support is not available. Could not find function entry point '%1!s!' in %2!s!. Error 3!s!. Native ...
  68. SQL Server native SOAP support is now deprecated and will be removed in a future version of SQL Server. Avoid using this ...
  69. SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is ...
  70. SQL Server Network Interfaces failed to initialize listeners on node %1!s! of a multi-node (NUMA) server configuration with ...
  71. SQL Server Network Interfaces initialized listeners on node %1!s! of a multi-node (NUMA) server configuration with node affinity ...
  72. SQL Server Profiler cannot perform Replay on database servers earlier than the server used to generate the original trace ...
  73. SQL Server Profiler cannot perform this action on database servers earlier than SQL Server 2000. Please use SQL Server 2000 ...
  74. SQL Server Profiler cannot perform this action using trace data generated on database servers earlier than SQL Server 2000. ...
  75. SQL Server Profiler cannot perform this action using trace data generated on database servers earlier than SQL Server 2005. ...