.NET Framework

  1. A COM client has called managed method '%1$s' on type '%2$s'. This method does not have an HRESULT return type and an exception ...
  2. A CompensableActivity cannot be nested inside the Compensation, Confirmation or Cancellation Handler of a parent CompensableActivity. ...
  3. A CompletionWorkItem has been scheduled for parent Activity '%1', DisplayName: '%2', InstanceId: '%3'. Completed Activity ...
  4. A CompletionWorkItem has been scheduled for parent Activity '{0}', DisplayName: '{1}', InstanceId: '{2}'. Completed Activity ...
  5. A CompletionWorkItem has completed for parent Activity '%1', DisplayName: '%2', InstanceId: '%3'. Completed Activity '%4', ...
  6. A CompletionWorkItem has completed for parent Activity '{0}', DisplayName: '{1}', InstanceId: '{2}'. Completed Activity '{3}', ...
  7. A configuration item alias for '{0}' cannot have the name '{1}' because it starts with the reserved prefix 'config' or 'lock'. ...
  8. A connection to the specified database could not be opened. See InnerException for details. However, there is a database ...
  9. A connection was successfully established with the server, but then an error occurred when obtaining the security/SSPI context ...
  10. A connection with Active Directory cannot be established. Verify that there are sufficient permissions to perform this operation. ...
  11. A constraint clause has already been specified for type parameter '%1!ls!'. All of the constraints for a type parameter must ...
  12. A constructor selection convention that would apply to Type '{0}' has been overridden by attributes applied in the source ...
  13. A constructor which accepts no parameters was not found for type '{0}'. Every entity type must have a constructor which accepts ...
  14. A ContractTypeName cannot have an empty 'Name'. A 'Name' and optionally a 'Namespace' must be provided for the ContractTypeName. ...
  15. A coordinator recovery log entry was corrupt and could not be deserialized. Data loss may result from this error.%r Transaction ...
  16. A coordinator recovery log entry was corrupt and could not be deserialized. Data loss may result from this error.%r Transaction ...
  17. A correlation query yielded an empty result set. Please ensure correlation queries for the endpoint are correctly configured. ...
  18. A custom wrapper for this COM component has been installed on your machine after you added this reference. This wrapper may ...
  19. A data item was not found in the container. The container must either implement IDataItemContainer, or have a property named ...
  20. A default value cannot be supplied for DependencyProperty '{0}' because its type is a reference type. Default values are ...
  21. A Dequeue operation timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. ...
  22. A DESCRIPTION MUST NOT use Solicit-Response and Notification type operations in a wsdl:portType definition. Solicit-Response ...
  23. A DESCRIPTION MUST specify a non-empty location attribute on the wsdl:import element. Although the wsdl:import statement ...
  24. A DESCRIPTION MUST use the same value of, either 'rpc' or 'document' for the style attribute for all of its operations in ...
  25. A DESCRIPTION SHOULD NOT include extension elements with a wsdl:required attribute value of "true" on any WSDL construct ...
  26. A DESCRIPTION using the WSDL namespace and the WSDL SOAP binding namespace MUST be valid according to the XML Schemas found ...
  27. A deserialization error occurred inside of ObjectStateFormatter. A property was typed as Type but the Type instance could ...
  28. A deserialization error occurred inside of ObjectStateFormatter. A property was typed as Type but the Type instance could ...
  29. A deserialization error occurred inside of ObjectStateFormatter. Deserialization was attempted using a string TypeConverter. ...
  30. A deserialization error occurred inside of ObjectStateFormatter. Deserialization was attempted using binary serialization. ...
  31. A document-literal binding in a DESCRIPTION MUST NOT have the namespace attribute specified on contained soapbind:body, soapbind:header, ...
  32. A document-literal binding in a DESCRIPTION MUST refer, in each of its soapbind:body element(s), only to wsdl:part element(s) ...
  33. A document-literal binding in a DESCRIPTION MUST, in each of its soapbind:body element(s), have at most one part listed in ...
  34. A downloaded file required for setup is corrupted. Setup cannot continue. This indicates the setup package is corrupted or ...
  35. A duplicate CorrelationQuery was found with Where='%1'. This duplicate query will not be used when calculating correlation. ...
  36. A duplicate CorrelationQuery was found with Where='{0}'. This duplicate query will not be used when calculating correlation. ...
  37. A FaultWorkItem has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'. The exception was propagated from ...
  38. A FaultWorkItem has been scheduled for Activity '{0}', DisplayName: '{1}', InstanceId: '{2}'. The exception was propagated ...
  39. A FaultWorkItem has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'. The exception was propagated from Activity ...
  40. A FaultWorkItem has completed for Activity '{0}', DisplayName: '{1}', InstanceId: '{2}'. The exception was propagated from ...
  41. A feed containing items that are not buffered (i.e. the items are not stored in an IList) cannot clone its items. Buffer ...
  42. A file is being created with information needed to reproduce your compiler problem. This information includes software versions, ...
  43. A file is being created with information needed to reproduce your compiler problem. This information includes: software versions, ...
  44. A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
  45. A file that is required cannot be installed because the cabinet file 2 is not digitally signed. This may indicate that the ...
  46. A fixup on an object implementing ISerializable or having a surrogate was discovered for an object which does not have a ...
  47. A function mapping for EntitySet '{0}' requires that corresponding Associations in AssociationSet '{1}' are loaded. Load ...
  48. A function mapping includes parameter bindings for two different Ends of the same AssociationSet. Only one End of a particular ...
  49. A generic instantiation for type '%1' from assembly '%2' was too deep. Is this generic type defined or used recursively? ...
  50. A GridView with EnableSortingAndPagingCallbacks set to true must be parented to a naming container before Render is called. ...
  51. A group by expression can only contain non-constant scalars that are comparable by the server. The expression with type '{0}' ...
  52. A group placeholder must be specified on ListView '{0}' when the GroupTemplate is defined. Specify a group placeholder by ...
  53. A group placeholder must be specified on ListView '{0}' when the GroupTemplate is defined. Specify a group placeholder by ...
  54. A header placeholder must be specified on Wizard '{0}' when HeaderTemplate is set. Specify a placholder by setting a control's ...
  55. A header placeholder must be specified on Wizard '{0}' when HeaderText is set. Specify a placholder by setting a control's ...
  56. A leg of the federated security chain contains multiple IssuedSecurityTokenParameters. The InfoCard system only supports ...
  57. A leg of the federated security chain contains multiple IssuedSecurityTokenParameters. Windows CardSpace only supports one ...
  58. A listener with no type name specified references the sharedListeners section and cannot have any attributes other than 'Name'. ...
  59. A local variable named '%1!ls!' cannot be declared in this scope because it would give a different meaning to '%1!ls!', which ...
  60. A mapping function binding specifies a function {0} that is not supported. Only functions that cannot be composed are supported. ...
  61. A mapping function binding specifies a function {0} with an unsupported parameter: {1}. Output parameters may only be mapped ...
  62. A member fixup was registered for an object which implements ISerializable or has a surrogate. In this situation, a delayed ...
  63. A message can be a normal MSMQ message, a positive or negative (arrival and read) acknowledgment message, or a report message. ...
  64. A message received on inbound Request-Reply url '{0}' was routed to a list with backup endpoints. Error handling is not possible ...
  65. A message received on inbound Request-Reply url '{0}' was routed to multiple endpoint lists. Multicast is not supported with ...
  66. A message received on inbound url '{0}' was routed to a list with backup endpoints. The binding the message was received ...
  67. A message was dispatched to the UnhandledDispatchOperation, but was invoked without a Message as input. This error might ...
  68. A message was received with a sequence number higher than the sequence number of the last message in this sequence. This ...
  69. A message was received with a sequence number of {0}. Sequence numbers cannot be less than 1. The reliable session was faulted. ...
  70. A message was received with a WS-Addressing ReplyTo or FaultTo header targeted at the "None" address. These values are not ...
  71. A message was received with a WS-Addressing ReplyTo or FaultTo header targeted at the "None" address. These values are not ...
  72. A message with action {0} is an empty message. This message cannot be processed because the body of this WS-ReliableMessaging ...
  73. A mismatch between the binding and MSMQ configuration was detected. The client cannot send messages. To use the custom dead ...
  74. A mismatch between the binding and MSMQ queue configuration was detected. The service cannot be started. The ExactlyOnce ...
  75. A mismatch occurred between the binding and the MSMQ configuration. Messages cannot be sent. The custom dead letter queue ...