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