UI Translation

.NET Framework

  1. The WS-AT protocol service timed out waiting for a response to an outcome message from a volatile participant. If the participant ...
  2. The WS-AtomicTransaction protocol service could not unmarshal the flowed transaction. The following exception occured: {0} ...
  3. The WS-RM policy under the namespace {0} requires the wsrmp:ExactlyOnce, wsrmp:AtLeastOnce, or wsrmp:AtMostOnce assertion. ...
  4. The WS-RM policy under the namespace {0} requires the wsrmp:ExactlyOnce, wsrmp:AtLeastOnce, or wsrmp:AtMostOnce assertion. ...
  5. The WSDL binding named {0} is not valid because no match for operation {1} was found in the corresponding portType definition. ...
  6. The wsdl operation input {0} in portType {1} does not reference a message. This is either because the message attribute is ...
  7. The wsdl operation output {0} in portType {1} does not reference a message. This is either because the message attribute ...
  8. The wsdl operation {0} in portType {1} contains a fault that does not reference a message. This is either because the message ...
  9. The wsdl schema that was used to create this configuration file contained a 'RequireIssuerSerialReference' assertion for ...
  10. The wsdl:binding element in a DESCRIPTION MUST be constructed so that its soapbind:binding child element specifies the transport ...
  11. The WSHttpBinding with name {0} failed validation because it contains a BindingElement with type {1} which is not supported ...
  12. The wsrm:{0} request message's wsa:ReplyTo address containing a URI which is not equivalent to the remote address. This is ...
  13. The X.509 certificate ({0}) usage time is invalid. The usage time '{1}' does not fall between NotBefore time '{2}' and NotAfter ...
  14. The X.509 certificate {0} chain building failed. The certificate that was used has a trust chain that cannot be verified. ...
  15. The X.509 certificate {0} chain building failed. The certificate that was used has a trust chain that cannot be verified. ...
  16. The X509FindType, '{0}', requires the type of the argument findvalue to be '{1}'. The argument findValue is of type '{2}'. ...
  17. The XAML Helper class name generated by the BeforeInitializeComponent XAML build task extension ({0}) cannot be a generic. ...
  18. The XAML Helper class name generated by the BeforeInitializeComponent XAML build task extension ({0}) was not found. Try ...
  19. The XML attribute '{0}' from namespace '{1}' is already present in the current scope. Use XML attributes to specify another ...
  20. The XML element '{0}' from namespace '{1}' is already present in the current scope. Use XML attributes to specify another ...
  21. The XML element '{0}' from namespace '{1}' references a method and a type. Change the method's message name using WebMethodAttribute ...
  22. The XML element '{0}' from namespace '{1}' was not expected. The XML element name and namespace must match those provided ...
  23. The XML element named '{0}' from namespace '{1}' is already present in the current scope. Elements with the same name in ...
  24. The XmlSchemaSet on the document is either null or has no schemas in it. Provide schema information before calling Validate. ...
  25. The XName '{0}' is promoted multiple times in the promotion '{1}.' Duplicate XNames are not allowed within the same promotion. ...
  26. The XPathNodeIterator has been invalidated. XPathNodeIterators passed as arguments to IXsltContextFunctions are only valid ...
  27. The xsi:type attribute value '{0}' is not valid for the element '{1}', either because it is not a type validly derived from ...
  28. The Zone membership condition is true for all assemblies that originate from the zone listed below. Assemblies that meet ...
  29. The ZoneTemplate property can only be set in or before the Page_PreInit event for static controls. For dynamic controls, ...
  30. The {0} '{1}' has the same name as the {2} '{1}'. Duplicate names are not allowed, you must change the name of either the ...
  31. The {0} '{1}' has the same name as the {2} '{1}'. Duplicate names are not allowed. You must change the name of either the ...
  32. The {0} assertion's Milliseconds attribute does not fall within the range this binding uses. The ReliableSessionBindingElement ...
  33. The {0} assertion's required Milliseconds attribute is not schema compliant. Milliseconds must be convertible to an unsigned ...
  34. The {0} control '{1}' does not have a naming container. Ensure that the control is added to the page before calling DataBind. ...
  35. The {0} could not be registered with the MetadataWorkspace because its version ('{1}') is different from the version ('{2}') ...
  36. The {0} declared on method '{1}' in type '{2}' is invalid. {0}s are only valid on methods that are declared in a type that ...
  37. The {0} has a Binding that uses AddressingVersion '{1}' which does not support adding WS-Addressing headers. {2} requires ...
  38. The {0} method is not supported on node type {1}. If you want to read typed content of an element, use the ReadElementContentAs ...
  39. The {0} must already be defined in order to edit it. You can define the {0} in source view or by running the Configure ListView ...
  40. The {0} object could not be serialized. This type of object cannot be serialized when the RelationshipManager belongs to ...
  41. The {0} operand of {1} is not valid because its type '{2}' cannot be compared for equality. Only primitive, enumeration, ...
  42. The {0} operation was called on an incoming request that did not specify a '{1}: {2}' header or the {2} header not contain ...
  43. The {0} request's response was a message with action {1}. The response must be a {0}Response with action {2}. The reliable ...
  44. The {0} requires that a valid IOperationInvoker is set on the DispatchOperation when ApplyDispatchBehavior is called. Please ...
  45. The {0}-parameter overloads of {1}.{2} must have exactly one method specified as the default overload by decorating it with ...
  46. The {0}.{1} operation references a message element {2} that has already been exported from the {3}.{4} operation. You can ...
  47. The {0}="{1}" is invalid because the attributes have all been locked at a higher level. {2}="*" must be used to lock all ...
  48. The {0}Response was received when the {0} request had not been sent. This is a WS-ReliableMessaging protocol violation. The ...
  49. The {1} events remaining for this notification period will be discarded because the maximum number of messages allowed per ...
  50. The {1} property of the control with id {2} is set to the value {0}, which cannot be converted to the required type {3}. ...
  51. The {base type definition} must have an {attribute wildcard} and the {target namespace} of the R's {attribute declaration} ...
  52. There are conflicting changes to this activity from an implementation update and a larger workflow update. The activity attempted ...
  53. There are conflicting changes to this activity from an implementation update and larger workflow update. The activity's arguments ...
  54. There are conflicting changes to this activity from its provided implementation map and the current update. The activity ...
  55. There are conflicting changes to this activity from its provided implementation map and the current update. The activity's ...
  56. There are conflicting XmlnsCompatibleWithAttributes in assemblies '{0}' and '{1}' for OldNamespace '{2}'. Change the attributes ...
  57. There are multiple pending asynchronous operations associated with the specified userState. To be able to cancel an asynchronous ...
  58. There are no active connections available in your Web Part. You may create a new connection by selecting the links above ...
  59. There are no EntitySets defined for the specified entity type '{0}'. If '{0}' is a derived type, use the base type instead. ...
  60. There are no records in the SqlDataRecord enumeration. To send a table-valued parameter with no rows, use a null reference ...
  61. There are three configurable policy levels (enterprise, machine, and user) that the security system uses to determine what ...
  62. There are two contracts listening on the same binding ({2}) and address with conflicting settings. Specifically, the contract ...
  63. There has been an overflow or underflow in GC memory pressure . The possible cause is unbalanced AddMemoryPressure and RemoveMemoryPressure ...
  64. There is a cycle of XML compatibility definitions, such that namespace '{0}' overrides itself. This could be due to inconsistent ...
  65. There is a cycle of XML compatibility definitions, such that namespace '{0}' overrides itself. This could be due to inconsistent ...
  66. There is a cycle of XmlnsCompatibleWithAttribute definitions in assembly '{0}', such that namespace '{1}' overrides itself. ...
  67. There is a problem with the application you are attempting to administer. Please check the spelling of the URL you used to ...
  68. There is a problem with this card, and it cannot be submitted. Contact the card provider to request a new managed card file. ...
  69. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact ...
  70. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. ...
  71. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact ...
  72. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. ...
  73. There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient ...
  74. There is already a component named '{0}'. Components must have unique names, and names must be case-insensitive. A name also ...
  75. There is already a generated proxy type for the object layer type '{0}'. This occurs when the same object layer type is mapped ...
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)