text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 GSSAPI operation failed with status: {0} (Minor status: {1}). Unrecognized System.Transactions.IsolationLevel enumeration value: {0}. Cannot access Kerberos ticket. Ensure Kerberos has been initialized with 'kinit'. The given value of type {0} from the data source cannot be converted to type {1} of the specified target column. Invalid attempt to call {0} when the stream is non-seekable. The connection was not closed. {0} {0}.Prepare method requires parameters of type '{1}' have an explicitly set Precision and Scale. Value cannot be converted to SqlVariant. {0} DeriveParameters only supports CommandType.StoredProcedure, not CommandType.{1}. Unable to get the address of the distributed transaction coordinator for the server, from the server. Is DTC enabled on the server? Specified parameter name '{0}' is not valid. Use of key '{0}' requires the key '{1}' to be present. {0} requires the command to have a transaction when the connection assigned to the command is in a pending local transaction. The Transaction property of the command has not been initialized. A time zone was specified. SqlDateTime does not support time zones. Operation aborted due to an exception (see InnerException for details). The collection '{0}' is missing from the metadata XML. A transport-level error has occurred when sending the request to the server. There is already an open DataReader associated with this Command which must be closed first. The connection is broken and recovery is not possible. The connection is marked by the server as unrecoverable. No attempt was made to restore the connection. No mapping exists from DbType {0} to a known {1}. Invalid attempt to read from column ordinal '{0}'. With CommandBehavior.SequentialAccess, you may only read from column ordinal '{1}' or greater. Operation cancelled by user. Received an unsupported token '{0}' while reading data from the server. Invalid SQLUserInstance.dll found at the location specified in the registry. Verify that the Local Database Runtime feature of SQL Server Express is properly installed. The sort order and ordinal must either both be specified, or neither should be specified (SortOrder.Unspecified and -1). The values given were: order = {0}, ordinal = {1}. Protocol error: A received message contains a valid signature but it was not encrypted as required by the effective Protection Level. A restriction exists for which there is no matching row in the restrictions collection. Invalid attempt to call {0} when the stream is closed. Precision '{0}' required to send all values in column '{1}' exceeds the maximum supported precision '{2}'. The values must all fit in a single precision. Format of the initialization string does not conform to specification starting at index {0}. Invalid routing information received. Must not specify SqlBulkCopyOption.UseInternalTransaction and pass an external Transaction at the same time. Target name should be non-empty if default credentials are passed. {0} '{1}'. Next reconnection attempt will exceed query timeout. Reconnection was terminated. The length of the parameter '{0}' exceeds the limit of 128 characters. Type {0} is not supported on this platform. Cannot connect to SQL Server Browser. Ensure SQL Server Browser has been started. The Stream does not support seeking. .database.usgovcloudapi.net The {0} is already contained by another {1}. Invalid parameter Size value '{0}'. The value must be greater than or equal to 0. No support for channel binding on operating systems other than Windows. The currently loaded System.Transactions.dll does not support Global Transactions. Buffer offset '{1}' plus the bytes available '{0}' is greater than the length of the passed in buffer. The input wasn't in a correct format. The keyword '{0}' is not supported on this platform. More restrictions were provided than the requested schema ('{0}') supports. Invalid array size. Database cannot be null, the empty string, or string of only whitespace. SSE Instance re-direction is not supported for non-local user instances. Metadata for field '{0}' of record '{1}' did not match the original record's metadata. The transaction is either not associated with the current connection or has been completed. Invalid index {0} for this {1} with Count={2}. Cannot obtain Local Database Runtime error message Can not start another operation while there is an asynchronous operation pending. Cannot enlist in the transaction because a local transaction is in progress on the connection. Finish local transaction and retry. The server did not preserve the exact client TDS version requested during a recovery attempt, connection recovery is not possible. SqlDbType.SmallDateTime overflow. Value '{0}' is out of range. Must be between 1/1/1900 12:00:00 AM and 6/6/2079 11:59:59 PM. Invalid min or max pool size values, min pool size cannot be greater than the max pool size. SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM. SQL Type has already been loaded with data. Subclass did not override a required method. SQL Type has not been loaded with data. The metadata XML is invalid. The {0} collection must contain a {1} column and it must be a string column. Invalid ConnectRetryCount value (should be 0-255). {1}[{0}]: the Size property has an invalid size of 0. The connection's current state: {0}. The collection name '{0}' matches at least two collections with the same name but with different case, but does not match any of them exactly. Timeout specified is invalid. Timeout cannot be < 0. Unexpected routing information received. One of the required DataSourceInformation tables columns is missing. The keyword 'Network Library' is not supported on this platform, prefix the 'Data Source' with the protocol desired instead ('tcp:' for a TCP connection, or 'np:' for a Named Pipe connection). Invalid column ordinals in schema table. ColumnOrdinals, if present, must not have duplicates or gaps. Parameter value '{0}' is out of range. Invalid source buffer (size of {0}) offset: {1} Scale value '{0}' is either less than 0 or greater than the maximum allowed scale of 7. Connection currently has transaction enlisted. Finish current transaction and retry. The connection's current state is fetching. The sort ordinal {0} was not specified. Cannot initialize SSPI package. .database.chinacloudapi.cn The given ColumnName '{0}' does not match up with any column in data source. Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. SqlParameter.TypeName is an invalid multipart name Divide by zero error encountered. Operation aborted. SqlDependency does not support calling Start() with different connection strings having the same server, user, and database in the same app domain. System.Data.SqlClient is not supported on this platform. SqlDbType.SmallMoney overflow. Value '{0}' is out of range. Must be between -214,748.3648 and 214,748.3647. There are not enough fields in the Structured type. Structured types must have at least one field. The connection has been disabled. Invalid parameter Offset value '{0}'. The value must be greater than or equal to 0. This {0} has completed; it is no longer usable. Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. ClientConnectionId before routing:{0} The ConnectionString property has not been initialized. Arithmetic Overflow. Invalid flag value. Data is Null. This method or property cannot be called on Null values. Destination array is not long enough to copy all the items in the collection. Check array index and length. Mappings must be either all name or all ordinal based. {0} '{1}', the current limit of '{2}' is insufficient. Invalid Packet Size. Invalid transaction or invalid name for a point at which to save within the transaction. Processing of results from SQL Server failed because of an invalid multipart name The duration spent while attempting to connect to this server was - [Pre-Login] initialization={0}; The DataSourceInformation table must contain exactly one row. The connection's current state is closed. Failed to obtain column collation information for the destination table. If the table is not in the current database the name must be qualified using the database name (e.g. [mydb]..[mytable](e.g. [mydb]..[mytable]); this also applies to temporary-tables (e.g. #mytable would be specified as tempdb..#mytable). Expecting argument of type {1}, but received type {0}. SqlDependency.Start has been called for the server the command is executing against more than once, but there is no matching server/user/database Start() call for current command. SqlDependency.OnChange does not support multiple event registrations for the same delegate. Server provided routing information, but timeout already expired. Invalid destination buffer (size of {0}) offset: {1} Internal DbConnection Error: {0} Conversion from SqlDecimal to Decimal overflows. No SqlDependency exists for the key. Connection Timeout Expired. The timeout period elapsed while attempting to create and initialize a socket to the server. This could be either because the server was unreachable or unable to respond back in time. Invalid attempt to {0} when stream is closed. No mapping exists from object type {0} to a known managed provider native type. A connection was successfully established with the server, but then an error occurred during the pre-login handshake. An error occurred while reading. Specified SeekOrigin value is invalid. NTLM authentication is not possible with default credentials on this platform. Invalid value for argument '{0}'. The value must be greater than or equal to 0. DBNull value for parameter '{0}' is not supported. Table-valued parameters cannot be DBNull. This SqlCommand object is already associated with another SqlDependency object. The {0} only accepts non-null {1} type objects, not {2} objects. Connection Timeout Expired. The timeout period elapsed at the start of the login phase. This could be because of insufficient time provided for connection timeout. Invalid value for this metadata. The metadata XML is invalid. The {1} column of the {0} collection must contain a non-empty string. The connection's current state is executing. Cannot access destination table '{0}'. Precision value '{0}' is either less than 0 or greater than the maximum allowed precision of 38. This failure occurred while attempting to connect to the routing destination. The duration spent while attempting to connect to the original server was - [Pre-Login] initialization={0}; handshake={1}; [Login] initialization={2}; authentication={3}; [Post-Login] complete={4}; Data length '{0}' is less than 0. Two strings to be concatenated have different collation. Invalid attempt to read when no data is present. The SQL Server instance returned an invalid or unsupported protocol version during login negotiation. The duration spent while attempting to connect to this server was - [Pre-Login] initialization={0}; handshake={1}; [Login] initialization={2}; The schema table contains no columns. HTTP Provider Named Pipes Provider Session Provider Sign Provider Shared Memory Provider SMux Provider SSL Provider TCP Provider SQL Network Interfaces TypeName specified for parameter '{0}'. TypeName must only be set for Structured parameters. The stored procedure '{0}' doesn't exist. Unsupported SQL Server version. The .Net Framework SqlClient Data Provider can only be used with SQL Server versions 7.0 and later. Unable to build schema collection '{0}'; The command execution cannot proceed due to a pending asynchronous operation already in progress. When using SqlDependency without providing an options value, SqlDependency.Start() must be called for each server that is being executed against. Invalid numeric precision/scale. Connection Timeout Expired. The timeout period elapsed while attempting to authenticate the login. This could be because the server failed to authenticate the user or the server was unable to respond back in time. Data returned is larger than 2Gb in size. Use SequentialAccess command behavior in order to get all of the data. The value's length for key '{0}' exceeds it's limit of '{1}'. SqlBulkCopy.WriteToServer failed because the SqlBulkCopy.DestinationTableName is an invalid multipart name The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. Failed to convert parameter value from a {0} to a {1}. Connection has been closed by peer Physical connection is not usable Timeout error No server name supplied TerminateListener() has been called Win9x not supported Function not supported Shared-Memory heap error Cannot find an ip/ipv6 type address to connect Cannot open a Shared Memory connection to SQL Server 2000 Shared memory connectivity to SQL Server 2000 is either disabled or not available on this machine Packet size too large for SSL Encrypt/Decrypt operations SSRP error Invalid attempt bind to shared memory segment Encryption(ssl/tls) handshake failed The Shared Memory dll used to connect to SQL Server 2000 was not found The SQL Server 2000 Shared Memory client dll appears to be invalid/corrupted Could not connect to the Shared Memory pipe An internal exception was caught Unable to locate the registry entry for SQLUserInstance.dll file path. Verify that the Local Database Runtime feature of SQL Server Express is properly installed. Registry value contains an invalid SQLUserInstance.dll file path. Verify that the Local Database Runtime feature of SQL Server Express is properly installed. Unable to load the SQLUserInstance.dll from the location specified in the registry. Verify that the Local Database Runtime feature of SQL Server Express is properly installed. Invalid SQLUserInstance.dll found at the location specified in the registry. Verify that the Local Database Runtime feature of SQL Server Express is properly installed. Local Database Runtime error occurred. An instance name was not specified while connecting to a Local Database Runtime. Specify an instance name in the format (localdb)\instance_name. Unable to locate a Local Database Runtime installation. Verify that SQL Server Express is properly installed and that the Local Database Runtime feature is enabled. Invalid Local Database Runtime registry configuration found. Verify that SQL Server Express is properly installed. Shared Memory is not supported for clustered server connectivity Server doesn't support requested protocol Cannot open a new thread in server process Couldn't load library Encryption is enforced but there is no valid certificate Connection has been closed Error getting enabled protocols list from registry Error Locating Server/Instance Specified Connection string is not valid Cannot post event to completion port Connecting to a SQL Server instance using the MultiSubnetFailover connection option is only supported when using the TCP protocol. Connecting to a named SQL Server instance using the MultiSubnetFailover connection option is not supported. Could not compose Service Principal Name (SPN) for Windows Integrated Authentication. Possible causes are server(s) incorrectly specified to connection API calls, Domain Name System (DNS) lookup failure or memory shortage Connecting with the MultiSubnetFailover connection option to a SQL Server instance configured with more than 64 IP addresses is not supported. Cannot open a Shared Memory connection to a remote SQL server Could not open a connection to SQL Server An error occurred while obtaining the dedicated administrator connection (DAC) port. Make sure that SQL Browser is running, or check the error log for the port number Could not establish dedicated administrator connection (DAC) on default port. Make sure that DAC is enabled Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. Internal Error Requested protection level is not supported with the GSSAPI implementation currently installed. The requested collection ({0}) is not defined. DateType column for field '{0}' in schema table is null. DataType must be non-null. Unexpected existing transaction. User Instance and Failover are not compatible options. Please choose only one of the two in the connection string. Attempt to invoke bulk copy on an object that has a pending operation. The {0} type parameter '{1}' must have a valid type name. The server is attempting to use a feature that is not supported on this platform. Attempted to remove an {0} that is not contained by this {1}. String or binary data would be truncated. The DestinationTableName property must be set before calling this method. There are multiple collections named '{0}'. Invalid attempt to GetBytes on column '{0}'. The GetBytes function can only be used on columns of type Text, NText, or Image. A transport-level error has occurred while sending information to the server. {0}: Connection property has not been initialized. ClientConnectionId:{0} The connection's current state is open. The instance of SQL Server you attempted to connect to does not support encryption. Function must not be called during event. Invalid 3 part name format for TypeName. The size of column '{0}' is not supported. The size is {1}. A transport-level error has occurred when receiving results from the server. Routing Destination:{0} The server did not acknowledge a recovery attempt, connection recovery is not possible. Invalid SqlDateTime. Column '{0}' does not allow DBNull.Value. Invalid operation. The connection is closed. The given ColumnMapping does not match up with any column in the source or destination. A transport-level error has occurred during SSPI handshake. LocalDB is not supported on this platform. Batching updates is not supported on the context connection. Internal .Net Framework Data Provider error {0}. Two strings to be compared have different collation. Only single dimensional arrays are supported for the requested action. Connection open and login was successful, but then an error occurred while enlisting the connection into the current distributed transaction. SqlDbType.Time overflow. Value '{0}' is out of range. Must be between 00:00:00.0000000 and 23:59:59.9999999. Invalid SSPI packet size. {0} returned {1}. .database.windows.net The dbType {0} is invalid for this constructor. A user instance was requested in the connection string but the server specified does not support this option. The only acceptable value for the property '{0}' is '{1}'. Timeout Value '{0}' is less than 0. The connection's current state is connecting. Non-negative number required. Timeout attempting to open the connection. The time period elapsed prior to attempting to open the connection has been exceeded. This may have occurred because of too many simultaneous non-pooled connection attempts. Numeric arithmetic causes truncation. A severe error occurred on the current command. The results, if any, should be discarded. Local Database Runtime: Cannot load SQLUserInstance.dll. Connecting to a mirrored SQL Server instance using the ApplicationIntent ReadOnly connection option is not supported. The connection cannot be used because there is an ongoing operation that must be finished. {0} '{1}', incorrect usage of quotes. Parameter '{0}' exceeds the size limit for the sql_variant datatype. Memory allocation for internal connection failed. Open result count exceeded. Invalid attempt to GetStream on column '{0}'. The GetStream function can only be used on columns of type Binary, Image, Udt or VarBinary. The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts. {0}: CommandText property has not been initialized Connection Timeout Expired. The timeout period elapsed while making a pre-login handshake request. This could be because the server was unable to respond back in time. Specified length '{0}' is out of range. The instance of SQL Server you attempted to connect to requires encryption but this machine does not support it. The server did not preserve SSL encryption during a recovery attempt, connection recovery is not possible. The transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements. Invalid attempt to access a closed XmlReader. Invalid attempt to GetChars on column '{0}'. The GetChars function can only be used on columns of type Text, NText, Xml, VarChar or NVarChar. {0} does not support parallel transactions. Invalid attempt to call {0} when the stream non-writable. Connection open and login was successful, but then an error occurred while enabling MARS for this connection. Cannot convert object of type '{0}' to object of type '{1}'. .database.cloudapi.de The specified value is not valid in the '{0}' enumeration. The locale id '{0}' of the source column '{1}' and the locale id '{2}' of the destination column '{3}' do not match. Conversion overflows. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Server {0}, database {1} is not configured for database mirroring. An {0} with {1} '{2}' is not contained by this {3}. requested collection ({0}) is not supported by this version of the provider. Invalid value for key '{0}'. SqlCommand.DeriveParameters failed because the SqlCommand.CommandText property value is an invalid multipart name There are no records in the SqlDataRecord enumeration. To send a table-valued parameter with no rows, use a null reference for the value instead. This method is not implemented by this class. GSSAPI operation failed with error - {0} ({1}). Connection Timeout Expired. The timeout period elapsed at the start of the pre-login phase. This could be because of insufficient time provided for connection timeout. Internal connection fatal error. Insufficient buffer space. Required: {0} Actual: {1}. The requested security package is not supported. The sort ordinal {0} on field {1} exceeds the total number of fields. The type of column '{0}' is not supported. The type is '{1}' Invalid internal packet size: The duration spent while attempting to connect to this server was - [Pre-Login] initialization={0}; handshake={1}; {0} requires an open and available Connection. {1} The Collation specified by SQL Server is not supported. The version of SQL Server in use does not support datatype '{0}'. The parameter data type of {0} is invalid. Null {0}.Prepare method requires all variable length parameters to have an explicitly set non-zero Size. {0}.Prepare method requires all parameters to have an explicitly set type. Invalid attempt to GetTextReader on column '{0}'. The GetTextReader function can only be used on columns of type Char, NChar, NText, NVarChar, Text or VarChar. The duration spent while attempting to connect to this server was - [Pre-Login] initialization={0}; handshake={1}; [Login] initialization={2}; authentication={3}; Invalid attempt to call {0} when the stream non-readable. Message Unable to build the '{0}' collection because execution of the SQL query failed. See the inner exception for details. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Invalid command sent to ExecuteXmlReader. The command must return an Xml result. Failed to generate SSPI context. The sort ordinal {0} was specified twice. Instance failure. When using SqlDependency without providing an options value, SqlDependency.Start() must be called prior to execution of a command added to the SqlDependency instance. Invalid ConnectRetryInterval value (should be 1-60). Failed to establish a MARS session in preparation to send the request to the server. Cannot remove the specified item because it was not found in the specified Collection. ParameterDirection '{0}' specified for parameter '{1}' is not supported. Table-valued parameters only support ParameterDirection.Input. Not allowed to change the '{0}' property. {1} The Stream does not support writing. Invalid CommandTimeout value {0}; the value must be >= 0. Associating port with I/O completion mechanism failed Protocol not supported I/O Error detected in read/write operation Asynchronous operations not supported Connection was terminated Invalid parameter(s) found Invalid connection found when setting up new session protocol Unsupported protocol specified Server implementation is not supported. The {0} enumeration value, {1}, is not supported by the .Net Framework SqlClient Data Provider. The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection. Mismatched end method call for asyncResult. Expected call to {0} but {1} was called instead. Specified QuotePrefix and QuoteSuffix values do not match. The mapped collection is in use and cannot be accessed at this time; The method '{0}' cannot be called more than once for the same execution. Invalid 'Packet Size'. The value must be an integer >= 512 and <= 32768. The {0} enumeration value, {1}, is invalid. The Stream does not support reading. {0} failed with error {1}. The acceptable values for the property '{0}' are '{1}' or '{2}'. '{0}' is not a supported handle type. One or more of the required columns of the restrictions collection is missing. The {0} enumeration value, {1}, is not supported by the {2} method. The duration spent while attempting to connect to this server was - [Pre-Login] initialization={0}; handshake={1}; [Login] initialization={2}; authentication={3}; [Post-Login] complete={4}; Invalid {2} attempt at dataIndex '{0}'. With CommandBehavior.SequentialAccess, you may only read from dataIndex '{1}' or greater. A connection was successfully established with the server, but then an error occurred when obtaining the security/SSPI context information for integrated security login. Two or more redirections have occurred. Only one redirection per login is allowed. Global Transactions are not enabled for this Azure SQL Database. Please contact Azure SQL Database support for assistance. Error Number:{0},State:{1},Class:{2} A transport-level error has occurred during connection clean-up. The connection does not support MultipleActiveResultSets. A connection was successfully established with the server, but then an error occurred during the login process. {0} cannot be changed while async operation is in progress. Failure while attempting to promote transaction. The SQL Server Service Broker for the current database is not enabled, and as a result query notifications are not supported. Please enable the Service Broker for this database if you wish to use notifications. The name is too long. This failure occurred while attempting to connect to the {0} server. The metadata XML is invalid. Number of fields in record '{0}' does not match the number in the original record. Invalid attempt to GetXmlReader on column '{0}'. The GetXmlReader function can only be used on columns of type Xml. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. Keyword not supported: '{0}'. Scale value '{0}' is either less than 0 or greater than the maximum allowed scale of 38. The {0} only accepts non-null {1} type objects. Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. Invalid attempt to call {0} when reader is closed. The requested operation cannot be completed because the connection has been broken.