UI Translation

.NET Framework

  1. The Receive is in a state in which instance update is not supported. Update can be made only when the Receive is waiting ...
  2. The Receive operation timed out after '{0}'. For duplex sessionful channels, the receive timeout is also the idle timeout ...
  3. The ReceiveContext delete operation failed because the message with Id '{0}' could not be received from the lock subqueue. ...
  4. The ReceiveContext unlock operation failed because the message with Id '{0}' could not be moved from the lock subqueue to ...
  5. The received derived key token has a invalid generation value specified. Value: {0}. The value should be greater than or ...
  6. The received derived key token has a invalid offset value specified. Value: {0}. The value should be greater than or equal ...
  7. The received message type '{2}' is invalid after calling {0}. {0} should only be used if no more data is expected from the ...
  8. The received message type is invalid after calling {0}. {0} should only be used if no more data is expected from the remote ...
  9. The received transaction has an isolation level of '{0}' but the service is configured with a TransactionIsolationLevel of ...
  10. The receiver returned an error indicating that the content type was missing on the request to {0}. See the inner exception ...
  11. The recipient did not provide its certificate. This certificate is required by the TLS protocol. Both parties must have access ...
  12. The recursive policy fetching limit has been reached. Check to determine if there is a loop in the federation service chain. ...
  13. The redist list file "{0}" has a null or empty Redist name in the FileList element. Make sure the Redist Name is not null ...
  14. The ref syntax for groups is not supported with encoded SOAP. Please change definition of schema type '{0}' from namespace ...
  15. The referenced Variable object (Name = '{0}') is not visible at this scope. There may be another location reference with ...
  16. The RegEx engine has timed out while trying to match a pattern to an input string. This can occur for many reasons, including ...
  17. The registry value '{0}' has type {1} rather than the expected type REG_SZ. This indicates an invalid or corrupted install. ...
  18. The RelatedEnd cannot be returned by this RelationshipManager. A RelatedEnd can only be returned by a RelationshipManager ...
  19. The RelatedEnd with role name '{0}' from relationship '{1}' has already been loaded. This can occur when using a NoTracking ...
  20. The relationship '{0}' does not contain the role '{1}'. Make sure that EdmRelationshipAttribute that defines this relationship ...
  21. The relationship '{0}' has columns that are not part of the key of the table on the primary side of the relationship. The ...
  22. The relationship '{0}' uses the set of foreign keys '{1}' that are partially contained in the set of primary keys '{2}' of ...
  23. The relationship being added conflicts with an existing relationship. Consider deleting the previous relationship and calling ...
  24. The relationship cannot be defined because the EntitySet name '{0}.{1}' is not valid for the role '{2}' in association set ...
  25. The relationship manager supplied by the object implementing IEntityWithRelationships is not the expected relationship manager. ...
  26. The relationship manager was defined with an owner of type '{0}', which is not compatible with the type '{1}' for the source ...
  27. The ReleaseInstanceMode property on OperationBehaviorAttribute can only be set on non-callback operations. Method '{0}' violates ...
  28. The reliable session infrastructure detected a system clock change. This will temporarily result in a less optimal message ...
  29. The remote endpoint closed the sequence before message transfer was complete. This is not supported since all messages could ...
  30. The remote endpoint closed the session before acknowledging all responses. All replies could not be delivered. The reliable ...
  31. The remote endpoint did not include a final acknowledgement in the reply to the close sequence request message. This is a ...
  32. The remote endpoint failed to include a required SequenceAcknowledgement header on a reliable reply message. The reliable ...
  33. The remote endpoint has closed the underlying secure session before the reliable session fully completed. The reliable session ...
  34. The remote endpoint has responded to a request message with an invalid reply. The reply has a RelatesTo header with an unexpected ...
  35. The remote endpoint has responded to a {0} request message with an invalid reply. The reply has a wsa:RelatesTo header with ...
  36. The remote endpoint has sent an fault message with an unexpected sequence identifier over a session. The fault may be intended ...
  37. The remote endpoint has sent an unrecognized fault with namespace, {0}, name {1}, and reason {2}. The channel could not be ...
  38. The remote endpoint has sent an unrecognized fault with namespace, {0}, name {1}, and reason {2}. The reliable session was ...
  39. The remote endpoint no longer recognizes this sequence. This is most likely due to an abort on the remote endpoint. {0} The ...
  40. The remote endpoint of the socket ({0}) did not respond to a close request within the allotted timeout ({1}). It is likely ...
  41. The remote endpoint replied to a request for a one way session with an offer for a two way session. This is a WS-ReliableMessaging ...
  42. The remote endpoint replied to a request for a two way session with an offer for a one way session. This is a WS-ReliableMessaging ...
  43. The remote endpoint replied to a request for a two way session with an offer for a one way session. This is likely caused ...
  44. The remote endpoint replied to the request for a sequence with a response that could not be parsed. See inner exception for ...
  45. The remote endpoint requested an address for acknowledgements that is not the same as the address for application messages. ...
  46. The remote endpoint responded to the create sequence request with a response with action {0}. The response must be a create ...
  47. The remote endpoint responded to the {0} request with a response with action {1}. The response must be a {0}Response with ...
  48. The remote endpoint responded to the {0} request with a response with action {1}. The response must be a {0}Response with ...
  49. The remote endpoint returned a {0}Response when the {0} request had not been sent. This is a WS-ReliableMessaging protocol ...
  50. The remote endpoint sent a TerminateSequence protocol message before fully acknowledging all messages in the reply sequence. ...
  51. The remote endpoint sent a wsrm:{0} request message with a wsa:ReplyTo address containing a URI which is not equivalent to ...
  52. The remote endpoint sent an unexpected request for an ack. Simplex clients do not send acks and do not process requests for ...
  53. The remote endpoint sent conflicting requests to create a reliable session. The conflicting requests have inconsistent filter ...
  54. The remote endpoint sent conflicting requests to create a reliable session. The remote endpoint requested both a one way ...
  55. The remote endpoint sent inconsistent responses to the same create sequence request. The sequence identifiers are not identical. ...
  56. The remote endpoint specified a last message number that is smaller than a sequence number that has already been seen. The ...
  57. The remote endpoint specified two different last message numbers. The reliable session is in an inconsistent state since ...
  58. The remote endpoint terminated the sequence before message transfer was complete. This is not supported since all messages ...
  59. The remote installed version of Windows Communication Foundation on '{0}' does not match the version of the WSAT configuration ...
  60. The RenderMode property cannot directly be set to 'Custom', to use a custom ToolStripRenderer, set the Renderer property ...
  61. The repair could not be completed because some required components have been removed. To successfully repair, download the ...
  62. The request channel timed out attempting to send after {0}. Increase the timeout value passed to the call to Request or increase ...
  63. The request channel timed out while waiting for a reply after {0}. Increase the timeout value passed to the call to Request ...
  64. The request could not be performed because of an unexpected I/O exception. The following error code was returned: '{0:x}' ...
  65. The request message has FaultTo='{0}' but IContextChannel.LocalAddress is '{1}'. When ManualAddressing is false, these values ...
  66. The request message has FaultTo='{0}' but IContextChannel.RemoteAddress is '{1}'. When ManualAddressing is false, these values ...
  67. The request message has From='{0}' but IContextChannel.LocalAddress is '{1}'. When ManualAddressing is false, these values ...
  68. The request message has From='{0}' but IContextChannel.RemoteAddress is '{1}'. When ManualAddressing is false, these values ...
  69. The request message has ReplyTo='{0}' but IContextChannel.LocalAddress is '{1}'. When ManualAddressing is false, these values ...
  70. The request message has ReplyTo='{0}' but IContextChannel.RemoteAddress is '{1}'. When ManualAddressing is false, these values ...
  71. The request message must be protected. This is required by an operation of the contract ('{0}','{1}'). The protection must ...
  72. The request operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been ...
  73. The Request property in activity '{0}' cannot be null. It must be set to the Receive activity that belongs to this request/reply ...
  74. The Request property in activity '{0}' cannot be null. It must be set to the Send activity that belongs to this request/reply ...
  75. The request to create a reliable session carries a wsrm:UsesSequenceSTR header, but does not contain the wsse:SecurityTokenReference. ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)