SQL Server 2016

  1. The SQL Server 2012 Data Mining Add-ins for Office help you uncover hidden patterns and relationships in your data and then ...
  2. The SQL Server 2012 features that have been selected to be upgraded to SQL Server 2016 are not at the required service pack. ...
  3. The SQL Server 2016 Setup wizard has encountered an internal error as it was not able to find a way to determine what changes ...
  4. The SQL Server Agent Service '{0}' could not be started, please check the System Event log and the Agent Log files to find ...
  5. The SQL Server Agent service (SQLServerAgent) is missing and must be re-created as part of the repair operation. Since the ...
  6. The SQL Server Agent service (SQLServerAgent) is missing and must be re-created as part of the repair operation. To continue, ...
  7. The SQL Server Agent service account '{0}' cannot be used along with a proxy. Please change the SQL Server Agent service ...
  8. The SQL Server Agent Service account '{0}' cannot be used to run the Managed Instance job because it is a built-in account. ...
  9. The SQL Server Agent service must be started. If the specified instance of SQL Server is a SQL Server failover cluster instance, ...
  10. The SQL Server Agent service on the UCP must be started. If the specified instance of SQL Server is a SQL Server failover ...
  11. The SQL Server Analysis Services (PowerPivot) service account information that is managed by SQL Server Configuration Manager ...
  12. The SQL Server Analysis Services (PowerPivot) service cannot be provisioned on this computer because it is no longer current. ...
  13. The SQL Server Analysis Services feature failed when it was initially installed. The feature must be removed before the current ...
  14. The SQL Server authentication credentials you specified for the connection will be persisted on the server. These credentials ...
  15. The SQL Server Browser is closing Analysis Services discovery support. There are no SQL Server Analysis Services instances ...
  16. The SQL Server Browser is closing SQL Server and connectivity discovery support. There are no SQL Server instances or the ...
  17. The SQL Server Browser processing of requests against a particular IP address has encountered a critical error. Processing ...
  18. The SQL Server Compact connection cannot be acquired. {0} Click Yes if you want to save the current settings. Click No if ...
  19. The SQL Server Compact Server Tools Setup Wizard has requested a reboot. Please reboot your computer before using the SQL ...
  20. The SQL Server Database Engine is not configured with a valid server collation and cannot be used as the Reporting Services ...
  21. The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current ...
  22. The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL ...
  23. The SQL Server failover cluster instance '{0}' was not correctly detected. The instance was discovered on the local node ...
  24. The SQL Server failover cluster instance name '{0}' already exists as a clustered resource. Specify a different failover ...
  25. The SQL Server failover cluster instance name '{0}' already exists as a server on the network. Specify a different failover ...
  26. The SQL Server failover cluster services is not online, or the cluster cannot be accessed from one of its nodes. To continue, ...
  27. The SQL Server feature '{0}' is not in a supported state for repair, as it was installed in preparation to be clustered. ...
  28. The SQL Server feature '{0}' is not in a supported state for repair, as it was never successfully configured on remote node ...
  29. The SQL Server feature '{0}' is not in a supported state for repair, as it was never successfully configured. Only features ...
  30. The SQL Server features on this computer are shown below. To remove a feature, select the checkbox next to the feature name. ...
  31. The SQL Server Installation Wizard is not supported on Windows Server Core. You must use Full Quiet mode by specifying the ...
  32. The SQL Server instance '%1!s!' is not a replication publisher. Run sp_adddistributor on SQL Server instance '%2!s!' with ...
  33. The SQL Server instance '%1!s!' is not configured to support replication. To enable the SQL Server instance to serve as a ...
  34. The SQL Server instance '%1!s!' with distributor '%2!s!' and distribution database '%3!s!' cannot be used with publisher ...
  35. The SQL Server instance '{0}' already has an Instance ID '{1}' that is different than the specified Instance ID '{2}'. Specifying ...
  36. The SQL Server instance '{0}' which was already upgraded on machine '{1}' has an Instance ID '{2}' that is different than ...
  37. The SQL Server instance hosting the service {0} and broker instance {1} was not found. Ensure the tool is connected to this ...
  38. The SQL Server instance hosting the service {0} was not found. Ensure the tool is connected to this server to allow investigation ...
  39. The SQL Server instance is unavailable. The Integration Services process (Process ID {0}) for the operation {1} (GUID:{2}) ...
  40. The SQL Server instance specified in SSIS service configuration is not present or is not available. This might occur when ...
  41. The SQL Server instance that you are trying to connect to does not include an installation of Data Quality Services. To finalize ...
  42. The SQL Server Integration Services service requires Integration Services to be installed by one of these editions of %SQL_PRODUCT_SHORT_NAME%: ...
  43. The SQL Server license agreement cannot be located for the selected edition, {0}. This could be a result of corrupted media ...
  44. The SQL Server Network Interface found a duplicate IP address in the SQL Server TCP listening settings. Remove the duplicate ...
  45. The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) %1!s! for the SQL Server service. ...
  46. The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. ...
  47. The SQL Server Network Interface library could not register the Service Principal Name (SPN) %1!s! for the SQL Server service. ...
  48. The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. ...
  49. The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) %1!s! for the SQL Server ...
  50. The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) %1!s! for the SQL Server ...
  51. The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. ...
  52. The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will ...
  53. The SQL Server patch package expects the installed SQL Server product to be at product version {0}, architecture {1}. Disqualified ...
  54. The SQL Server patch package is part of a general distribution release (GDR). This package cannot be applied since this SQL ...
  55. The SQL Server performance counter '%s' (instance '%s') of object '%s' is now above the threshold of %s (the current value ...
  56. The SQL Server performance counter '%s' (instance '%s') of object '%s' is now below the threshold of %s (the current value ...
  57. The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity ...
  58. The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation ...
  59. The SQL Server removal of SQL Server failover cluster '{0}' encountered an error deleting cluster resource '{1}'. The exception ...
  60. The SQL Server repair operation has set registry keys to default values, as follows: '{0}', field: '{1}'. Previous value: ...
  61. The SQL Server Reporting Services feature failed when it was initially installed. The feature must be removed before the ...
  62. The SQL Server Reporting Services Shared service cannot be repaired at the same time as dependent services or databases. ...
  63. The SQL Server resource group must be owned by the current cluster node. Setup requires access to shared cluster resources. ...
  64. The SQL Server Sertup user interface cannot be shown because it is already running. Wait for the other Setup operation to ...
  65. The SQL Server Service account does not have permission to register the supplied URL on the endpoint '%1!s!'. Use sp_reserve_http_namespace ...
  66. The SQL Server service account login or password is not valid. Use SQL Server Configuration Manager to update the service ...
  67. The SQL server specified by these connection properties does not support managed objects. Please choose a different server. ...
  68. The SQL Server version cannot be determined. Make sure the SQL Server can be connected and the SERVERPROPERTY('ProductVersion') ...
  69. The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a ...
  70. The SQL statement cannot be executed because filegroup '%1!s!' is offline. Use the sys.database_files or sys.master_files ...
  71. The SQL statement has been manually edited and the displayed values may not reflect the metadata of the destination table ...
  72. The SQL statement is not valid because it contains the following duplicate column names: {0}. Correct the statement by providing ...
  73. The SQL statement is not valid because it contains the following duplicate column names: {0}. Correct the statement by providing ...
  74. The SQL, AS and/or RS features of the instance chosen to upgrade have been installed into separate folders. This is not a ...
  75. The SQLMerge ActiveX control failed with error code 1!x! when attempting to access the registry key '%2'. Ensure that the ...