SQL Server 2008 R2
- The number of max worker threads is set too low. On this computer, the number must be more than %1!s!. You should increase ...
- The number of max worker threads that is configured %1!s! is less than the minimum allowed on this computer. The default ...
- The number of members specified for validation exceeds the system limit of {0} members. Reduce the number of members in the ...
- The number of message fragments from the transport that are successfully delivered into local target queues per second. Note ...
- The number of messages from local endpoints and the transport that are successfully delivered into local target queues per ...
- The number of messages from local endpoints that are successfully delivered directly into local target queues per second. ...
- The number of messages from the transport that are successfully delivered into local target queues per second. This includes ...
- The number of package items in parameter '{0}' is not equal to the number of packages defined in MSI extension metadata '{1}'. ...
- The number of parameters in the replication command does not match what is defined in the DTS package. Regenerate the package. ...
- The number of params passed to sp_execute is not equal to the number of params used when the handle was prepared (%1!s!). ...
- The number of priority 1 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 10 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 2 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 3 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 4 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 5 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 6 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 7 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 8 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of priority 9 messages from local endpoints and the transport that are successfully delivered into local target ...
- The number of rowsets created as a result of aborted online index build operations that are waiting to be dropped by the ...
- The number of rowsets per second created as a result of aborted online index build operations that were skipped by the background ...
- The number of rowsets per second created as a result of aborted online index build operations that were successfully dropped ...
- The number of seconds that must elapse before the Report Server assumes the command failed or took too much time to perform ...
- The number of seconds to wait before returning from a failed Report Server Database login attempt. A value of 0 allows for ...
- The number of spatial elements for {0} '{1}' exceeds the maximum limit for the map. The remaining spatial data does not appear ...
- The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %1!s!. This ...
- The number of threads required for this pipeline is %1!d!, which is more than the system limit of %2!d!. The pipeline requires ...
- The number of times that a leaf page cookie could not be used during an index search since changes happened on the leaf page. ...
- The number of times that a tree page cookie could not be used during an index search since changes happened on the parent ...
- The number of times the SQL Server has been successfully restarted by SQL Server Agent, since the last SQL Server Agent restart. ...
- The number of transport receives I/O per second. Note that a transport receive I/O may contain more than one message fragment. ...
- The numeric indicator, {0}, was detected in the report. SQL Server 2008 Reporting Services does not support numeric indicators. ...
- The numeric indicator, {0}, was removed from the report. SQL Server 2008 Reporting Services does not support numeric indicators. ...
- The NumKeyColumns value is not valid. In the %1!s!, the value for the NumKeyColumns custom property must be between 1 and ...
- The object %1!s! is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication. ...
- The object '%1!s!'.'%2!s!' is not a valid resource governor classifier user-defined function. A valid classifier user-defined ...
- The object '{0}' referenced by the indexed view '{1}' cannot be used as the alternate schema object for article '{2}' because ...
- The object '{0}' was created, but an error occurred setting extended properties. Use the object properties dialog to set ...
- The object cannot be added because another object with the same name already exists in the collection. Use a different name ...
- The object does not implement IDispatch. This error occurs when a property object or properties collection attempts to access ...
- The object does not support type information. This occurs when the runtime attempts to get the type information from an object ...
- The object ID cannot be changed from '%{strID/}' to '%{strNewID/}' for the '%{name/}' %{typename/}. The object ID cannot ...
- The object ID is missing from the object definition of %{strName/}. When a CREATE statement has set the object overwrite ...
- The object is in a zombie state. An object may enter a zombie state when either ITransaction::Commit or ITransaction::Abort ...
- The object model cannot be used since there is no available session context. This typically occurs because the AdomdServer ...
- The object model does not accept the calls from non-server threads. This typically occurs because the AdomdServer object ...
- The object name cannot be changed from "%1!s!" to "%2!s!" because another object in the collection already uses that name. ...
- The object with ID "{0}" referred by to a ForEachPropertyMapping is not a ForEach Loop container. The offending ForEachPropertyMapping ...
- The object with ID of '%{id/}', Name of '%{name/}' is of type '%{typename/}' which does not support the requested operation. ...
- The ObjectData element is missing in the XML block of a hosted object. This occurs when the XML parser attempts to locate ...
- The objects "%1!s!" and "%2!s!" in the FROM clause have the same exposed names. Use correlation names to distinguish them. ...
- The OLAP binding of the '%{column/}' nested table should reference the same cube as the binding of the '%{struct/}' mining ...
- The OLAP Cube-based mining structure or model, %{name/}, cannot be processed with out-of-line bindings (e.g. the INSERT INTO ...
- The OLE Automation extended stored procedures (XPs) allow Transact-SQL batches, stored procedures, and triggers to reference ...
- The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" could not set the range for table "%3!s!" because of column "%4!s!". ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" could not set the range for table "%3!s!". %4!s!. For possible cause ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" does not contain the table "%3!s!". The table either does not exist ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" reported a change in schema version between compile time ("%3!s!") ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" reported different metadata at run time for table "%3!s!", column "%4!s!". ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" returned a "%3!s!" index "%4!s!" with the incorrect bookmark ordinal ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata for a column. The column "%3!s!" (compile-time ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata for a column. The name was changed at ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata. An extra column was supplied during ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata. The object "%3!s!" was missing the ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" supports column level collation, but failed to provide collation data ...
- The OLE DB provider "%1!s!" for linked server "%2!s!" supports column level collation, but failed to provide the metadata ...
- The OLE DB provider '%1!s!' for linked server '%2!s!' provided invalid collation. LCID = %3!s!, Compflags = %4!s!, SortOrder ...
- The OLE DB provider used by the OLE DB adapter does not support IConvertType. Set the adapter's ValidateColumnMetaData property ...
- The OLE DB Provider {0} is not installed or is not valid. Do you want to reset the connection string? If you click OK, the ...
- The ON clause at line %d{Line/}, column %d{Column/}, is not valid. Columns specified in the ON clause must be scalar, and ...
- The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online. ...
- The online restore to database '%1!s!' failed. It may be appropriate to perform an offline restore instead. An offline restore ...
- The online restore to database '%1!s!' failed. It may be appropriate to perform an offline restore instead. To force an offline ...