UI Translation

.NET Framework

  1. The IsReference setting for type '{0}' is '{1}', but the same setting for its parent class '{2}' is '{3}'. Derived types ...
  2. The IssuedSecurityTokenProvider cannot support the FederatedClientCredentialsParameters. The FederatedClientCredentialsParameters ...
  3. The ITransactionLocal interface is not supported by the '{0}' provider. Local transactions are unavailable with the current ...
  4. The IXmlSerializable type '{0}' cannot be deserialized in partial trust because it does not have a public parameterless constructor. ...
  5. The key does not match the indexer key. When setting the value of a specific index, the key of the desired value must match ...
  6. The key in the image-list value that represents the image to display. when the list view item is in the unselected state. ...
  7. The key properties of all entity types returned by the function import '{0}' must be mapped to the same non-nullable columns ...
  8. The language for this file does not support the necessary code parsing and generation services. Please ensure the file you ...
  9. The lazily evaluated value of type '{0}' passed to the ReflectionModelServices API as part of the argument '{1}' must not ...
  10. The length of the default directory specified in the setup.sdb file cannot be greater then 100 characters. The directory ...
  11. The length of the install path is too long. If setup is being run from a network drive, map the network drive to a shorter ...
  12. The length of the unattend file name and path cannot be greater then 250 characters. Rerun setup using a shorter unattend ...
  13. The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error. ...
  14. The LinkDemands on override {0} do not exactly match the following LinkDemands on base method {1}: {2}. Add, remove, or modify ...
  15. The LinkDemands on override {0} do not exactly match the LinkDemands on base method {1}. Add, remove, or modify LinkDemands ...
  16. The listener '{0}' added to source '{1}' must have a listener with the same name defined in the main Trace listeners section. ...
  17. The location of the root folder from which to start browsing. Only the specified folder and any subfolders that are beneath ...
  18. The location with name '{0}' cannot be retrieved as a Location of type '{1}' because it is a Location of type '{2}'. The ...
  19. The lock is being disposed while still being used. It either is being held by a thread and/or has active waiters waiting ...
  20. The major ('{0}') or minor ('{1}') component of the assembly version number was truncated when generating the default Windows ...
  21. The managed coclass wrapper class '%1!ls!' for interface '%2!ls!' cannot be found (are you missing an assembly reference?) ...
  22. The manifest is missing required hashes for some application components. The manifest signature is regarded as not valid. ...
  23. The map at position '{0}' (zero-based) for Activity ID '{1}' does not match the map(s) that preceded it. Please ensure that ...
  24. The mapping and metadata information for EntityContainer '{0}' no longer matches the information used to create the pre-generated ...
  25. The mapping of CLR type to EDM type is ambiguous because multiple CLR types match the EDM type '{0}'. Previously found CLR ...
  26. The maximum array length quota ({0}) has been exceeded while reading XML data. This quota may be increased by changing the ...
  27. The maximum array length quota ({0}) or the maximum items in object graph quota has been exceeded while reading XML data. ...
  28. The maximum buffer size ({0}) has been exceeded while reading MTOM data. This quota may be increased by changing the maxBufferSize ...
  29. The maximum interval of time that a chunk of a message or a full message can remain buffered in memory before being sent ...
  30. The maximum message size quota for incoming messages ({0}) has been exceeded. To increase the quota, use the MaxReceivedMessageSize ...
  31. The maximum message size quota for incoming messages has been exceeded for the remote channel. See the server logs for more ...
  32. The maximum message size quota for incoming messages has been exceeded. To increase the quota, use the maxRequestLength attribute ...
  33. The maximum nametable character count quota ({0}) has been exceeded while reading XML data. The nametable is a data structure ...
  34. The maximum number of pending asynchronous accept threads that are available for processing incoming connections on the service. ...
  35. The maximum number of results for the find operation must be greater than zero. To terminate the find operation based on ...
  36. The maximum number of times a reliable channel attempts to retransmit a message it has not received an acknowledgement for, ...
  37. The maximum read depth ({0}) has been exceeded because XML data being read has more levels of nesting than is allowed by ...
  38. The maximum retry count has been exceeded with no response from the remote endpoint. The reliable session was faulted. This ...
  39. The maximum string content length quota ({0}) has been exceeded while reading XML data. This quota may be increased by changing ...
  40. The maximumCount argument must be a positive number. If a maximum is not required, use the constructor without a maxCount ...
  41. The MaximumResolvedReferences property of MetadataExchangeClient must be greater than or equal to one. '{0}' was specified. ...
  42. The MaxReceivedMessageSize of the associated listener ({0}) is greater than the MaxReceivedMessageSize of the PeerNode ({1}) ...
  43. The Member '{0}.{1}' differs only in case from an existing Member, and is not compatible with the current language option. ...
  44. The member named '{0}' was found as both a property and an event on type '{1}'. Members with the same name are not supported. ...
  45. The member or parameter '{0}' is marked with multiple Import and ImportMany attributes. Only the first attribute encountered ...
  46. The membership condition determines whether or not an assembly meets specific requirements to get the permissions associated ...
  47. The merged dictionary is invalid. Either a ResourceDictionary is being placed into its own MergedDictionaries collection ...
  48. The message cannot be deserialized into MessageContract type {0} since it does not have a default (parameterless) constructor. ...
  49. The message cannot be sent because it's missing an MsmqIntegrationMessageProperty. All messages sent over MSMQ integration ...
  50. The message cannot be sent because its message ID ({0}) is already associated with an existing message. Please ensure that ...
  51. The message containing this stream has been closed. Note that request streams cannot be accessed after the service operation ...
  52. The message contains a callback context header with an endpoint reference for AddressingVersion '{0}'. Callback context can ...
  53. The message contains a callback context message property. Callback context can be transmitted only when the ContextBindingElement ...
  54. The message could not be dispatched because the service at the endpoint address '{0}' is unavailable for the protocol of ...
  55. The message could not be dispatched because the transport manager has been stopped. This can happen if the application is ...
  56. The message could not be processed. This is most likely because the action '{0}' is incorrect or because the message contains ...
  57. The message could not be sent because its size ({0}) was larger than the maximum supported datagram size for this transport ...
  58. The message could not be sent over the network adapter with index {0} because the index specified is invalid or the transport ...
  59. The message could not be transferred within the allotted timeout of {0}. There was no space available in the reliable channel's ...
  60. The message is not encrypted with a key derived from the encrypted key. The binding's token parameter '{0}' requires key ...
  61. The message is not encrypted with a key derived from the encryption token. The binding's token parameter '{0}' requires key ...
  62. The message property '{0}' inside the HttpRequestMessage is not with expected type '{1}'. Please make sure this property ...
  63. The message property '{0}' is missing in the HttpRequestMessage. Please make sure this property not removed or changed from ...
  64. The message received from the server could not be parsed. Common causes for this error are when the response is modified ...
  65. The message received from the server could not be parsed. Common causes for this error are when the response is modified ...
  66. The message sequence information for the specified EndpointDiscoveryMetadata cannot be obtained because it is not part of ...
  67. The message time to live (TTL) is too large. The message cannot be sent. The message TTL cannot exceed the Int32 maximum ...
  68. The message type '{0}' is not allowed for the '{1}' operation. Valid message types are: '{2}, {3}'. To close the WebSocket, ...
  69. The message version of the outgoing message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured ...
  70. The message with Action '{0}' cannot be processed at the receiver because this Action is reserved for the connection opening ...
  71. The message with Action '{0}' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. ...
  72. The message with To '{0}' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. ...
  73. The MessageFilterTable has not been configured for this RoutingService. Verify that either the routing behavior filterTableName ...
  74. The metadata document has Schema elements in the '{0}' and '{1}' namespaces, but only a single namespace per document is ...
  75. The metadata for this file is corrupted. Invalid metadata token. Seek to row {0}, but table {1} ({2}) only has {3} rows. ...
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)