SQL Server 2012

  1. SQL Server must enable your login or account for Publisher '{0}' before you can view or modify the publication properties. ...
  2. SQL Server must shut down in order to recover a database (database ID %1!s!). The database is either a user database that ...
  3. SQL Server native HTTP support is not available. Could not find function entry point '%1!s!' in %2!s!. Error 3!s!. Native ...
  4. SQL Server native SOAP support is now deprecated and will be removed in a future version of SQL Server. Avoid using this ...
  5. SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is ...
  6. SQL Server Network Interfaces failed to initialize listeners on node %1!s! of a multi-node (NUMA) server configuration with ...
  7. SQL Server Network Interfaces initialized listeners on node %1!s! of a multi-node (NUMA) server configuration with node affinity ...
  8. SQL Server PowerPivot for SharePoint must be installed as a named instance using PowerPivot' as the instance name. This name ...
  9. SQL Server Profiler cannot perform Replay on database servers earlier than the server used to generate the original trace ...
  10. SQL Server Profiler cannot perform this action on database servers earlier than SQL Server 2005. Please use SQL Server 2005 ...
  11. SQL Server Profiler cannot perform this action using trace data generated on database servers earlier than SQL Server 2005. ...
  12. SQL Server redistributable and shared features are installed when needed: Error and Usage Reporting, SQL Server Native Client, ...
  13. SQL Server replication requires the actual server name to make a connection to the server. Specify the actual server name, ...
  14. SQL Server Reporting Services versions earlier than SQL Server 2008 Reporting Services are not supported. The detected version ...
  15. SQL Server requires that all articles in a publication allowing updatable subscriptions contain a timestamp column used for ...
  16. SQL Server requires that all objects referenced by published stored procedures, such as tables and user-defined functions, ...
  17. SQL Server requires that all tables referenced by published views and indexed views be available at the Subscriber. If the ...
  18. SQL Server service has been paused. No new connections will be allowed. To resume the service, use SQL Computer Manager or ...
  19. SQL Server setup account does not have the SeSecurityPrivilege privilege on the specified file server in the path {0}. This ...
  20. SQL Server Setup could not instantiate because another instance of SQL Server Setup is already running. The running instance ...
  21. SQL Server Setup could not search for updates through the Windows Update service. You can either check again or click Next ...
  22. SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the ...
  23. SQL Server setup detected that after the removal of the current node, all IP addresses for the SQL Server failover cluster ...
  24. SQL Server Setup detected that there are multiple subnets. Because of this, Setup sets the IP address resource dependency ...
  25. SQL Server Setup did not have the administrator permissions required to copy a file: 2]. To continue, verify that the file ...
  26. SQL Server Setup expects a valid security identifier (SID) stored on machine '{0}' in the registry key 'HKEY_LOCAL_MACHINE\{1}' ...
  27. SQL Server Setup failed after the uninstall process removed the files for the feature, and therefore, the uninstall process ...
  28. SQL Server Setup failed to create and clean up directory '{0}' for product updates. Verify that you have permissions to create ...
  29. SQL Server Setup failed to download product updates with result '{0}' and error code {2}. This may indicate that the Windows ...
  30. SQL Server setup failed to download product updates. This may indicate that the Windows Update service does not have online ...
  31. SQL Server Setup failed to modify security permissions on file 2 for user 3]. To proceed, verify that the account and domain ...
  32. SQL Server Setup failed to modify security permissions on registry key 2 for user 3]. To proceed, verify that the account ...
  33. SQL Server Setup failed to modify security permissions on service 2 for user 3]. To proceed, verify that the account and ...
  34. SQL Server Setup failed to register the Microsoft Update service. This may indicate that the Windows Update service does ...
  35. SQL Server Setup failed to search for product updates with result '{0}' and error code {2}. This may indicate that the Windows ...
  36. SQL Server setup failed to search for product updates. This may indicate that the Windows Update service does not have online ...
  37. SQL Server Setup has detected that that no instance ID was passed to the setup. Setup cannot continue pass a valid instance ...
  38. SQL Server Setup has encountered an error when running a Windows Installer file. Windows Installer error message: {0} Windows ...
  39. SQL Server setup patch '{0}' failed to install. Error code: {1}. Please check the log files or contact your administrator. ...
  40. SQL Server setup patch failed to install, do you want to continue the setup? Patch file: {0} Error code: {1} If you want ...
  41. SQL Server Setup was canceled after the uninstall process removed the files for the feature, and therefore, the uninstall ...
  42. SQL Server Setup was canceled before the setup process could upgrade the instance. To continue the upgrade process, uninstall ...
  43. SQL Server Setup was cancelled before this feature could be installed. Uninstall this feature, and then run the setup process ...
  44. SQL Server Setup was not able to access computer '{0}' to validate user account '{1}'. This may happen when there are network ...
  45. SQL Server Setup was not able to access computer '{0}' to validate user group '{1}'. This may happen when there are network ...
  46. SQL Server Setup was not able to access domain '{0}' to validate user account '{1}'. This may happen when there are network ...
  47. SQL Server Setup was not able to access domain '{0}' to validate user group '{1}'. This may happen when there are network ...
  48. SQL Server Setup was not able to download the product updates. Click Retry to download again, click Ignore to skip downloading, ...
  49. SQL Server Setup was not able to extract requested product update {0} to {1}. This can often happen when drive does not have ...
  50. SQL Server Setup was not able to scan for product updates within {0} minutes. This can happen when there are Internet or ...
  51. SQL Server Setup was not able to scan for product updates within {0} minutes. This can happen when there is an issue with ...
  52. SQL Server Setup will now be installed. If an update for SQL Server Setup is found and specified to be included, the update ...
  53. SQL Server Setup will verify but will not change service account credentials during the repair operation. To change service ...
  54. SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required. ...
  55. SQL Server Snapshot Agent Utility Options - PUBLICATION - /Publication /ReplicationType 1 - Transactional,Snapshot(default), ...
  56. SQL Server Trace with id %1!s! has been stopped and closed by external user. SQL Server Trace collector will attempt to re-create ...
  57. SQL Server version: {0} is not supported by this release of Upgrade Advisor, only SQL2000 SP4 above or SQL2005 SP2 above ...
  58. SQL Server version: {0} is not supported by this release of Upgrade Advisor, only SQL2005, SQL2008 or SQL2008 R2 is supported. ...
  59. SQL Server Warning: '%1!s!' has performed a forced defection of TSX server '%2!s!'. Run sp_delete_targetserver at the MSX ...
  60. SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action ...
  61. SQL Server was unable to close sessions and connections in a reasonable amount of time and is aborting "polite" shutdown. ...
  62. SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions ...
  63. SQL Trace failed to send event notification. The server has run out of memory. The same send failure may not be reported ...
  64. SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be ...
  65. SQL Trace was stopped due to server shutdown. Trace ID = '%1!s!'. This is an informational message only; no user action is ...
  66. SQL writer error: A critical component required by the SQL writer is not registered. This might happen if an error occurred ...
  67. SQL writer error: A module or function that the Writer depends on does not exist in the Operating System. This might happen ...
  68. SQL writer error: Database %1 of SQL Server instance %2 has been ignored during backup because it contains files on a raw ...
  69. SQL writer error: Different values have been specified for the same restore option for Database %1 of SQL Server instance ...
  70. SQL writer error: Differential backup failed because the previous backup metadata for Database %1 of SQL Server instance ...
  71. SQL writer error: The backup completion state failed to be recorded in the database %1 of instance %2. No new differential ...
  72. SQL writer error: The COM Server with CLSID %1 and name %2 cannot be started during Safe Mode. The SQL writer cannot start ...
  73. SQL writer error: Writers will not receive events since the COM+ database is corrupted. This might happen if an error occurred ...
  74. SQL writer information: The COM Server with CLSID %1 and name %2 cannot be started. Most likely the CPU is under heavy load. ...
  75. SQL writer Service error: The EventSystem service is disabled or is attempting to start during Safe Mode. The SQL writer ...