.NET Framework

  1. The call to EndCommit on the CommittableTransaction with id = '%1' threw a TransactionException with the following message: ...
  2. The call to EndCommit on the CommittableTransaction with id = '{0}' threw a TransactionException with the following message: ...
  3. The call to method '%1!ls!' needs to be dynamically dispatched, but cannot be because it is part of a base access expression. ...
  4. The call to OnGetExtension on the WorkflowInstance '{0}' threw an exception. This is considered fatal. See inner exception ...
  5. The call to OnRequestAbort on the WorkflowInstance '{0}' threw an exception. This is considered fatal. See inner exception ...
  6. The call to QI for interface '%1$s' with IID '%2$s' failed with HRESULT 3$s (%4$s). One likely reason this failed is that ...
  7. The callback contract of contract {0} either does not exist or does not define any operations. If this is not a duplex contract, ...
  8. The callback passed to operation '{0}' was called more than once. This indicates an internal error in the implementation ...
  9. The CallerFilePathAttribute applied to parameter '%1!ls!' will have no effect because it applies to a member that is used ...
  10. The CallerFilePathAttribute cannot be applied because there are no standard conversions from type '%1!ls!' to type '%2!ls!' ...
  11. The CallerLineNumberAttribute applied to parameter '%1!ls!' will have no effect because it applies to a member that is used ...
  12. The CallerLineNumberAttribute cannot be applied because there are no standard conversions from type '%1!ls!' to type '%2!ls!' ...
  13. The CallerMemberNameAttribute applied to parameter '%1!ls!' will have no effect because it applies to a member that is used ...
  14. The CallerMemberNameAttribute cannot be applied because there are no standard conversions from type '%1!ls!' to type '%2!ls!' ...
  15. The card collection for Windows CardSpace could not be found or was corrupt. If you have a backup of your card collection, ...
  16. The card is not valid. Verify that there is valid metadata in the EndPointReference element and that the URI scheme is HTTPS. ...
  17. The card provider has declined to provide a preview of the data that will be sent. For more information, click What data ...
  18. The card provider requires you to use a newer version of the card. If you do not have a newer version of this card, exit ...
  19. The cast to value type '{0}' failed because the materialized value is null. Either the result type's generic parameter or ...
  20. The certificate '{0}' must have a private key that is capable of key exchange. The process must have access rights for the ...
  21. The certificate for the client has not been provided. The certificate can be set on the ClientCredentials or ServiceCredentials. ...
  22. The certificate for this site or managed card provider cannot be displayed or is not available. Contact the site or the managed ...
  23. The change cannot be tracked because the state of the object changed from '{0}' to '{1}' since the previous call to EntityMemberChanging ...
  24. The changes that you selected will invalidate one or more signatures that are applied to this document. Are you sure you ...
  25. The changes that you selected will invalidate one or more signatures that are applied to this document. Are you sure you ...
  26. The changes that you selected will invalidate one or more signatures that are applied to this document. Are you sure you ...
  27. The changes to the database were committed successfully, but an error occurred while updating the object context. The ObjectContext ...
  28. The changes you just made to security policy might prevent the .NET Framework Configuration tool from running the next time ...
  29. The channel is configured to use interactive initializer '{0}', but the channel was Opened without calling DisplayInitializationUI. ...
  30. The channel received an unexpected fault input message with Action = '{0}' while closing. You should only close your channel ...
  31. The channel received an unexpected input message with Action '{0}' while closing. You should only close your channel when ...
  32. The ChannelDispatcher at '{0}' is unable to open its IChannelListener as there are no endpoints for the ChannelDispatcher. ...
  33. The ChannelDispatcher with ListenUri '{0}' has endpoints with the following contracts: {1}. Metadata endpoints cannot share ...
  34. The children of the soap:Body element in a ENVELOPE MUST be namespace qualified. The use of unqualified element names may ...
  35. The cipher key negotiated by SSL is too small ('{0}' bits). Keys of such lengths are not allowed as they may result in information ...
  36. The Claim '{0}' was not able to be removed. It is either not part of this Identity or it is a claim that is owned by the ...
  37. The Class '{0}' does not exist in the user code file. Please make sure that the 'ClassName' property of the parent scope ...
  38. The class {0} can be designed, but is not the first class in the file. Visual Studio requires that designers use the first ...
  39. The client requested creation of a two way session. A one way session was created. The session cannot continue without as ...
  40. The client token at least needs to have the SecurityImpersonationLevel of at least Impersonation for Out of process Webhost ...
  41. The client was unable to establish a connection because of an error during connection initialization process before login. ...
  42. The client was unable to process the callback request due to an internal error. For more information about the error, either ...
  43. The client was unable to process the callback request due to an internal error. For more information about the error, either ...
  44. The client's security session did not receive a 'close response' message from the service within the configured timeout ({0}). ...
  45. The ClientCredentials cannot be added to the binding parameters because the binding parameters already contains a SecurityCredentialsManager ...
  46. The ClockController.Seek method was called using TimeSeekOrigin.Duration as the seekOrigin parameter for a Clock that has ...
  47. The ClockController.Seek method was called with arguments that describe a seek destination that seeks a child with Slip but ...
  48. The ClockController.Seek method was called with arguments that describe a seek destination with a negative value. The seek ...
  49. The close operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been ...
  50. The close status description '{0}' is too long. The UTF8-representation of the status description must not be longer than ...
  51. The CloseSequence request's reply message must carry a final acknowledgement. This is a violation of the WS-ReliableMessaging ...
  52. The CLR has been unable to transition from COM context 1$x to COM context 2$x for 60 seconds. The thread that owns the destination ...
  53. The CLR marshaler encountered an error while attempting to associate a SafeHandle with an unmanaged resource. This may cause ...
  54. The CLR marshaler encountered an error while attempting to release the reference to a SafeHandle it acquired in order to ...
  55. The CLR marshaler encountered an error while attempting to restore the thread culture after a call from unmanaged to managed ...
  56. The CLR Type '{0}' could not be loaded during service compilation. Verify that this type is either defined in a source file ...
  57. The CLR Type '{0}' could not be loaded during service compilation. Verify that this type is either defined in a source file ...
  58. The CLR type '{0}', provided as the Factory attribute of the ServiceHost directive in the '.svc' file, does not derive from ...
  59. The CLSID specified in the service file is not configured in the specified application. (The CLSID is {0}, the AppID is {1}.) ...
  60. The Code Group Properties dialog box allows you to edit this code group's name, description, membership condition, and permission ...
  61. The collection data contract type '{0}' cannot be deserialized in partial trust because it does not have a public parameterless ...
  62. The collection data contract type '{0}' specifies '{1}' for the KeyName property. This is not allowed since the type is not ...
  63. The collection data contract type '{0}' specifies '{1}' for the ValueName property. This is not allowed since the type is ...
  64. The collection data contract type '{0}' specifies the same value '{1}' for both the KeyName and the ValueName properties. ...
  65. The collection in the projection is of type '{0}'. For a collection to be materialized to a projection, it must be of type ...
  66. The collection name '{0}' matches at least two collections with the same name but with different case, but does not match ...
  67. The collection navigation property '{0}' of type '{1}' returned null. For a collection to be initialized automatically, it ...
  68. The CollectionView that originates this CurrentChanging event is in a state that does not allow the event to be canceled. ...
  69. The color used to display header day and trailing day text. Header and trailing days are the days from the previous and following ...
  70. The column '{0}' on the table/view '{1}' was excluded, and is a key column. The remaining key(s) were used and table/view ...
  71. The column '{0}' on the table/view '{1}' was excluded, and is a key column. The table/view has been excluded. Please fix ...
  72. The column or association '{0}' in the mapping had no corresponding member in type '{1}'. Mapping members from above root ...
  73. The columns of table {1} are mapped to AssociationSet {2}'s End {3} but the key columns of table {4} are not mapped to the ...
  74. The COM+ Integration service '{0}' specified in configuration is not in a supported format and could not be started. Ensure ...
  75. The combined value '{0}' of flags attribute is invalid. Allowed flag values are: 0 (none), 1 (proxy), 2 (NoServiceNameCheck), ...