SQL Server 2012
- The SSRS service application is not mapped to this web application. Use the SSRS service application pages to associate the ...
- The SSRSSharePointModeCheck command line parameter is not supported for this Setup action or scenario. The SSRSSharePointModeCheckparameter ...
- The stage of processing when the event is raised. The event can be raised either when the DML plan is compiled or when it ...
- The start index %1!d! is not valid for function "%2!s!". The start index value must be an integer greater than 0. Start index ...
- The start index was not valid for function SUBSTRING. The start index value must be an integer greater than zero. The start ...
- The start time '{0}' of event number '{1}' is less than the start time '{2}' of event preceding it. If you need out of order ...
- The start width of the range. Measured as a percentage of the size of the gauge (height for horizontal gauges, width for ...
- The StartMode property indicates the start mode of the Win32 base service. \"Boot\" specifies a device driver started by ...
- The StartName property indicates the account name under which the service runs. Depending on the service type, the account ...
- The StartService method attempts to place the service into its startup state. It returns one of the following integer values: ...
- The startup parameter -h (Hot Add memory metadata with AWE on a 32-bit server) is enabled on the instance of SQL Server. ...
- The state indicator, {0}, was detected in the report. SQL Server 2008 Reporting Services does not support state indicators. ...
- The state indicator, {0}, was removed from the report. SQL Server 2008 Reporting Services does not support state indicators. ...
- The state of the local availability replica in availability group '%1!s!' has changed from '%2!s!' to '%3!s!'. The replica ...
- The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for ...
- The statement %1!s! is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ...
- The statement failed because column '%1!s!' (ID=%2!s!) uses collation %3!s!, which is not recognized by older client drivers. ...
- The statement failed because the sql_variant value uses collation %1!s!, which is not recognized by older client drivers. ...
- The statement is not supported on this version of the operating system. Could not find function entry point '%1!s!' in Httpapi.dll. ...
- The statement, INSERT INTO . '%s{name/}'.CASES, is not valid when used with a mining model. This statement can be used only ...
- The status of association {0} could not be changed, because the current association status is incorrect. In order for the ...
- The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data. ...
- The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication ...
- The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed ...
- The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use ...
- The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM filegroups are not included. ...
- The stoplist '%1!s!' already contains full-text stopword '%2!s!' with locale ID %3!s!. Specify a unique stopword and locale ...
- The stoplist '%1!s!' does not contain fulltext stopword '%2!s!' with locale ID %3!s!. Specify a valid stopword and locale ...
- The STOPPING_TOLERANCE parameter for the '%{modelname/}' model is not valid. STOPPING_TOLERANCE must be integer and greater ...
- The StopService method places the service in the stopped state. It returns an integer value of 0 if the service was successfully ...
- 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 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, sp_tableoption failed because a table with a nonclustered columnstore index cannot be altered to use ...
- 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 passed in for property {0} is exceeding the size limit allowed for this property. Please input a value of length ...
- 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 migrated database may differ from that of the source database because of changes in the data model of ...
- 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, ...