SQL Server 2016
- The storage URL will be accessed using one of the stored SQL credentials. For directions to create appropriate credentials, ...
- The StorageEngineUsed property cannot be set to TabularMetadata for database '%{DBName/}' because this feature is disabled. ...
- The store provider factory type '{0}' does not implement the IServiceProvider interface. Use a store provider that implements ...
- The stored credentials are not available for one or more data sources in this report. You might be prompted to provide credentials ...
- The stored procedure %1!s! must be run from a distirbution database. The current database %2!s! is not a distribution database. ...
- The stored procedure '%1!s!' refers to a group of numbered stored procedures. Numbered stored procedures are not available ...
- The stored procedure 'sp_tableoption' failed because a table with a nonclustered columnstore index cannot be altered to use ...
- The stored procedure or function '{0}' does not have a return type. ExecuteFunction only supports stored procedures and functions ...
- The stored procedure or function '{1}' returned the type '{0}'. ExecuteFunction only supports stored procedures and functions ...
- The stored procedure or scalar function cannot be specified as a FROM clause reference or as a target for an UPDATE, INSERT ...
- The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator. ...
- The Stored Procedure Resolver requires a non-null procedure name. Use sp_changemergearticle to set the resolver_info correctly. ...
- The Stored Procedure Resolver requires the stored procedure '%1' to return a result set that matches the column definition ...
- The Stored Procedure Resolver requires the stored procedure '%1' to return a result set whose row identifier matches the ...
- The stored procedure sp_createagentparameter failed to add one or more parameters to the system table msdb.dbo.MSagentparameterlist. ...
- The Stored Procedure, '%1!s!', failed to run because the Integration Services database (SSISDB) is not in single-user mode. ...
- The stored state of the report is not valid or supported. It may contain XML that is not well-formed or not valid based on ...
- The stream cannot be found. The stream identifier that is provided to an operation cannot be located in the report server ...
- The string '{0}' contains a combination of characters (', ", ;) that cannot not be passed into a SQL Server connection string. ...
- The string literal "%1!s!" contains an illegal escape sequence of "\%2!c!". The escape sequence is not supported in string ...
- The string literal "%1!s!" contains an illegal hexadecimal escape sequence of "\x%2!s!". The escape sequence is not supported ...
- The string literal contains an illegal escape sequence. The escape sequence is not supported in string literals in the expression ...
- The string value that starts with '{0}.' is too long for an agent parameter of type '{1}'. The maximum length allowed is ...
- The string value was truncated. The buffer received a string that was too long for the column, and the string was truncated ...
- The StringInputSettingExistsCondition element cannot be the root element of a document, it can only be used as the child ...
- The structure of the '{0}' dimension cannot be modified because it is a linked dimension. You can specify translations and ...
- The structure of the data has changed (columns were added or removed). The exceptions highlighting cannot continue and will ...
- The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database ...
- The structure, '{0}', is not valid in the cross-validation procedure call because all its models have Key Time or Key Sequence ...
- The StructureColumn function returns the value of the specified scalar mining structure column for the current model case. ...
- The StructureColumn function returns the value of the specified table mining structure column for the current model case. ...
- The stylesheet does not contain a document element. The stylesheet may be empty, or it may not be a well-formed XML document. ...
- The subreport '{0}' could not be found at the specified location {1}. Please verify that the subreport has been published ...
- The subreport '{3}' could not be processed within parent report '{4}' due to a mismatch in execution engines. Either the ...
- The subreport '{3}' could not be processed. Parent report '{4}' failed to automatically republish, or it contains a Reporting ...
- The Subscriber '%1!s!':'%2!s!' was not marked for reinitialization at the Publisher because the subscription is either anonymous ...
- The Subscriber partition information string may be truncated such that only the first %1!d! characters of the string will ...
- The subscribers ( %1!s! ) of original publisher '%2!s!' do not appear as remote servers at redirected publisher '%3!s!'. ...
- The subscription '{0}' cannot be found. The subscription identifier that is provided to an operation cannot be located in ...
- The subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, SubscriberDb=%5!s!) is not accessible. ...
- The subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, SubscriberDb=%5!s!) is not active ...
- The subscription could not be initialized using an initial snapshot because one or more tables in the subscription belong ...
- The subscription database was successfully attached. The subscription will be visible the next time you run Windows Synchronization ...
- The subscription has been marked as removed and will be absent from the list of subscriptions the next time you run Windows ...
- The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription. ...
- The subscription has expired and is no longer available. Do you want to mark the subscription for reinitialization? Reinitialization ...
- The subscription has expired. Mark the subscription for reinitialization and restart the Merge Agent to reinitialize the ...
- The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You ...
- The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, ...
- The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued ...
- The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure ...
- The subscription to publication '%1!s!' was not found but a shared agent does exist. To specify a subscription to a publication ...
- The subscription to publication '%1' could not be verified. Ensure that all Merge Agent command line parameters are specified ...
- The subscription was successfully created. The subscription will be visible the next time you run Windows Synchronization ...
- The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and ...
- The summation of all expression values in the most precise expression data type. If the expression result is integer, numeric, ...
- The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore. ...
- The sync relationship is not valid. A target entity can contain only Leaf members. Remove non-Leaf members or choose a different ...
- The synchronization agent encountered an error and failed to determine if a new snapshot must be applied during the next ...
- The synchronization method (@sync_method) must be '[bcp native', '[bcp character', 'concurrent', 'concurrent_c', 'database ...
- The syntax for the 'Process' command is incorrect. The 'Bindings' keyword cannot appear under a 'Process' command if the ...
- The syntax for the 'Process' command is incorrect. The 'Datasource' keyword cannot appear under a 'Process' command if the ...
- The syntax for the 'Process' command is incorrect. The 'DatasourceView' keyword cannot appear under a 'Process' command if ...
- The syntax for the 'Process' command is incorrect. The 'ErrorConfiguration' keyword cannot appear under a 'Process' command ...
- The syntax for the 'TestConnection' command is incorrect. Datasource node is to be provided if and only if 'TestConnection' ...
- The syntax for the 'TestConnection' command is incorrect. Out of line related information is to be provided if and only if ...
- The syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, ...
- The syntax for the ImpersonationInfo object is incorrect. The value of the ImpersonationMode property (%{strImpMode/}) is ...
- The syntax of argument "/{0}" is incorrect. Either the delimiter '=' is missing or there is one or more space characters ...
- The syntax of argument '{0}' is incorrect. Either the delimiter '=' is missing or there is one or more space characters before ...
- The syntax of the broker instance '%1!s!' is invalid. The specified broker instance is too long, the maximum size is 256 ...
- The system databases of the current instance of SQL Server cannot be rebuilt because the SQL Server service startup type ...
- The system encountered SQL Error %1!s! (severity: %2!s!, state: %3!s!), which has no corresponding error text. Refer to the ...
- The system is out of memory. If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing ...
- The system job (%s) has been queued because the maximum number of system working threads (%ld) are already running. This ...