.NET Framework

  1. The number of transacted operations with the outcome committed in this service. Work done under such operations is fully ...
  2. The number of transacted operations with the outcome committed in this service. Work done under such operations is fully ...
  3. The number of transactions that flowed to operations at this endpoint per second. This counter is incremented any time a ...
  4. The number of transactions that flowed to operations at this endpoint per second. This counter is incremented any time a ...
  5. The number of transactions that flowed to operations at this endpoint. This counter is incremented any time a transaction ...
  6. The number of transactions that flowed to operations at this endpoint. This counter is incremented any time a transaction ...
  7. The number of transactions that flowed to operations in this service per second. This counter is incremented any time a transaction ...
  8. The number of transactions that flowed to operations in this service per second. This counter is incremented any time a transaction ...
  9. The number of transactions that flowed to operations in this service. This counter is incremented any time a transaction ...
  10. The number of transactions that flowed to operations in this service. This counter is incremented any time a transaction ...
  11. The number of transactions that flowed to this operation per second. This counter is incremented any time a transaction ID ...
  12. The number of transactions that flowed to this operation per second. This counter is incremented any time a transaction ID ...
  13. The number of transactions that flowed to this operation. This counter is incremented any time a transaction ID is present ...
  14. The number of transactions that flowed to this operation. This counter is incremented any time a transaction ID is present ...
  15. The object at index {0} in the specified collection of objects is in an added or deleted state. Relationships cannot be created ...
  16. The object at index {0} in the specified collection of objects is not attached to the same ObjectContext as source object ...
  17. The object cannot be added to the object context. The object's EntityKey has an ObjectStateEntry that indicates that the ...
  18. The object cannot be attached because it is already in the object context. An object can only be reattached when it is in ...
  19. The object cannot be attached because the value of a property that is a part of the EntityKey does not match the corresponding ...
  20. The object could not be added or attached because its EntityReference has an EntityKey property value that does not match ...
  21. The object could not be added to the bound collection. The specific EntitySet for the object of type '{0}' could not be determined. ...
  22. The object could not be added to the EntityCollection or EntityReference. An object that is attached to an ObjectContext ...
  23. The object could not be removed from the EntityCollection or EntityReference. An object that is attached to an ObjectContext ...
  24. The object graph contains multiple references to an instance of type '{0}' and the serializer cannot find a commonly visible ...
  25. The object in the '{0}' role cannot be automatically added to the context because it was retrieved using the NoTracking merge ...
  26. The object in the ObjectContext is of type '{0}', but the modified object provided is of type '{1}'. The two objects must ...
  27. The object is in a detached state. This operation cannot be performed on an ObjectStateEntry when the object is detached. ...
  28. The object returned from InvokeConstructor cannot be null, must match the serialization model of the type, and must derive ...
  29. The object state cannot be changed. This exception may result from one or more of the primary key properties being set to ...
  30. The object with ID {0} implements the IObjectReference interface for which all dependencies cannot be resolved. The likely ...
  31. The object {0} is being remoted by a proxy that does not support interface discovery. This type of remoted object is not ...
  32. The ObjectContext must be configured by 1) defining ContextTypeName, 2) defining both ConnectionString and DefaultContainerName, ...
  33. The ObjectStateEntry is a relationship entry. The current and original values of relationship entries cannot be modified. ...
  34. The occurrence range of element '{0}'is not a valid restriction of the wildcard's occurrence range in the base, Elt:Any - ...
  35. The ODBC managed provider requires that the TABLE_NAME restriction be specified and non-null for the GetSchema indexes collection. ...
  36. The ODBC managed provider requires that the TABLE_NAME restriction be specified and non-null for the GetSchema indexes collection. ...
  37. The offline setting exists within the section of the Web.config file for the Web site. The highlighted lines in the following ...
  38. The OLE Transactions propagation token received in the message could not be used to unmarshal a transaction. It may be invalid ...
  39. The OleDbDataReader.Read must be used from the same thread on which is was created if that thread's ApartmentState was not ...
  40. The OnCreateDynamicUpdateMap method which takes an UpdateMapMetadata parameter must not be called on a NativeActivity. The ...
  41. The one-way operation '{1}' on ServiceContract '{0}' is configured for transaction flow. Transactions cannot be flowed over ...
  42. The only additional connection string keyword that may be used when requesting the context connection is the Type System ...
  43. The open operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been ...
  44. The opening handshake properties associated with the current WebSocket connection are not available. The most likely cause ...
  45. The operation '{0}' could not be completed because the sessionful channel timed out waiting to receive a message. To increase ...
  46. The operation '{0}' could not be invoked because the property '{1}' on the OperationContract is set to '{2}'. To invoke this ...
  47. The operation '{0}' could not be loaded because it has a parameter or return type of type System.ServiceModel.Channels.Message ...
  48. The operation '{0}' could not be loaded because it specifies "rpc-style" in "literal" mode, but uses message contract types ...
  49. The operation '{0}' in implemented contract '{1}' requires transaction to be flowed, but the Receive activity is NOT in TransactedReceiveScope. ...
  50. The operation '{0}' in service contract '{1}' is different in '{2}' and '{3}'. Check the input, output and fault messages ...
  51. The operation '{0}' on callback contract '{1}' is configured with TransactionAutoComplete set to false. TransactionAutoComplete ...
  52. The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false and the InstanceContextMode ...
  53. The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false but SessionMode is not set ...
  54. The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to true and with TransactionScopeRequired ...
  55. The operation cannot be completed because EndBuild has already been called but existing submissions have not yet completed. ...
  56. The operation cannot be completed because the pipe was closed. This may have been caused by the application on the other ...
  57. The operation contract '{0}' is not self-consistent. When the '{1}' is set to '{2}', both '{3}' and '{4}' properties must ...
  58. The operation could not be completed because the object to which the relationship manager belongs was attached to the ObjectContext ...
  59. The operation could not be completed because the required metadata could not be found. Make sure that the connection used ...
  60. The operation could not be completed. Please make sure that the markup file is opened in the context of a C# or VB project. ...
  61. The operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion ...
  62. The operation failed due to a registry or installation problem. Restart this application and try again. If the problem persists, ...
  63. The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable. ...
  64. The operation has failed because it was called from a handler while the workflow was not idle. The operation requires that ...
  65. The operation has no matching binding. Check if the operation, input and output names in the Binding section match with the ...
  66. The operation is not supported because the protocol {0} is enabled for application '{1}' and the application is running in ...
  67. The operation to establish the WebSocket connection timed out. To increase this time limit, use the OpenTimeout property ...
  68. The operation with name '{0}' must be enabled to use the ReceiveContext ManualAcknowledgement mode when the BufferedReceiveServiceBehavior ...
  69. The operation {0} either has a parameter or a return type that is attributed with MessageContractAttribute. In order to represent ...
  70. The OperationContractAttribute declared on method '{0}' in type '{1}' is invalid. OperationContractAttributes are only valid ...
  71. The OperationFormatter could not deserialize any information from the Message because the Message is empty (IsEmpty = true). ...
  72. The operations in a wsdl:binding in a DESCRIPTION MUST result in wire signatures that are different from one another. An ...
  73. The operator '{0}' at position {1} of expression '{2}' is not supported for the 'null' literal; only equality checks are ...
  74. The optional '{0}' property's value was not set to the specified value and setting the property to the specified value was ...
  75. The original value for the property '{0}' cannot be set because it is a complex property. Individual scalar properties can ...