UI Translation

.NET Framework

  1. The request to create a reliable session contains an invalid wsrm:IncompleteSequenceBehavior value. This is a WS-ReliableMessaging ...
  2. The request to create a reliable session contains the wsse:SecurityTokenReference but does not carry a wsrm:UsesSequenceSTR ...
  3. The request URI is not valid, $count cannot be applied to the segment '{0}' since $count can only follow a resource segment. ...
  4. The request URI is not valid, since the segment '{0}' refers to a singleton, and the segment '{1}' can only follow a resource ...
  5. The request URI is not valid. Since the segment '{0}' refers to a collection, this must be the last segment in the request ...
  6. The request URI is not valid. The segment '{0}' is not valid. Since the uri contains the '{1}' segment, there must be only ...
  7. The request URI is not valid. The segment '{0}' must be the last segment since its one of the following: $batch, $value, ...
  8. The request URI is not valid. The segment '{0}' must refer to a navigation property since the previous segment identifier ...
  9. The request URI is not valid. There must a segment specified after the '{0}' segment and the segment must refer to a entity ...
  10. The requested .Net Framework Data Provider's implementation does not have an Instance field of a System.Data.Common.DbProviderFactory ...
  11. The requested assembly name was neither found in the GAC nor in the manifest or the manifest's specified location is wrong. ...
  12. The requested operation could not be completed because the object implementing IEntityWithRelationships returned a null value ...
  13. The requested operation could not be completed, because a mismatched EntityKey was returned from the EntityKey property on ...
  14. The requested operation requires a Sql Server execution thread. The current thread was started by user code or other non-Sql ...
  15. The requested script resource '{0}' requires version '{1}' of the ASP.NET AJAX Framework. To use this resource, make sure ...
  16. The requested upgrade is not supported by '{0}'. This could be due to mismatched bindings (for example security enabled on ...
  17. The requested url '{0}' hosts a XAML document with root element type '{1}'; but no http handler is configured for this root ...
  18. The RequestSecurityToken message does not match the endpoint filters the service '{0}' is expecting incoming messages to ...
  19. The RequestSecurityTokenResponseCollection received has more than one RequestSecurityTokenResponse element. Only one RequestSecurityTokenResponse ...
  20. The required entry '{0}' was not found in the provided input. This entry is required by the key fields defined on type '{1}'. ...
  21. The required pattern for URI containing ";component" is "AssemblyName;Vxxxx;PublicKey;component", where Vxxxx is the assembly ...
  22. The required {0} attribute is missing from the {1} element in the {2} assertion. The ReliableSessionBindingElement could ...
  23. The resource expected to be generated by the BeforeInitializeComponent XAML build task extension was not found. Try rebuilding ...
  24. The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, ...
  25. The resource URL cannot be longer than 1024 characters. If using a CompositeScriptReference, reduce the number of ScriptReferences ...
  26. The resource URL cannot be longer than {0} characters. If using a CompositeScriptReference, reduce the number of ScriptReferences ...
  27. The ResourceReader class does not know how to read this version of .resources files. Expected version: {0} This file: {1} ...
  28. The response message must be protected. This is required by an operation of the contract ('{0}', '{1}'). The protection must ...
  29. The response requires that version 2 of the protocol be used, but the MaxProtocolVersion of the data service is set to DataServiceProtocolVersion.V1. ...
  30. The response to the request to create a reliable session contains an invalid wsrm:IncompleteSequenceBehavior value. This ...
  31. The result cannot be represented as a nodeset. Only results of type XPathResultType.NodeSet can be represented as nodesets. ...
  32. The result is out of the supported range for this calendar. The result should be between {0} (Gregorian date) and {1} (Gregorian ...
  33. The result of the dynamic binding produced by the object with type '{0}' for the binder '{1}' needs at least one restriction. ...
  34. The result type '{0}' of the dynamic binding produced by binder '{1}' is not compatible with the result type '{2}' expected ...
  35. The result type '{0}' of the dynamic binding produced by the object with type '{1}' for the binder '{2}' is not compatible ...
  36. The result type '{0}' specified in the declaration of the function '{1}' does not match the result type '{2}' of the function ...
  37. The result type of the query is neither an EntityType nor a CollectionType with an entity element type. An Include path can ...
  38. The ResultType of the query view expression specified for the EntitySet '{0}' is not assignable to the element type of the ...
  39. The ResultType of the specified expression is not compatible with the required type. The expression ResultType is '{0}' but ...
  40. The return table of the function '{0}' is not defined. Either all columns have been excluded or the table has no columns. ...
  41. The return type '{0}' of the function import '{1}' is not compatible with the return type '{2}' of the store function '{3}'. ...
  42. The return value of type {0} on method {1} of interface {2} is not web services compliant due to the following reason: {3} ...
  43. The returned wsrm:{0}Response message was missing the required wsa:RelatesTo header. This is a violation of the WS-Addressing ...
  44. The returned {0}Response was carrying the a wsa:RelatesTo header that does not correlate with the wsa:MessageId header on ...
  45. The Revision number (4th part) in Version field of Microsoft Common Language Runtime dependency section must be zero: {0}. ...
  46. The RM destination received a CreateSequenceResponse message. The RM destination does not process CreateSequenceResponse ...
  47. The RM destination received a TerminateSequenceResponse message. The RM destination does not process TerminateSequenceResponse ...
  48. The RM destination received an CloseSequenceResponse message. The RM destination does not process CloseSequenceResponse messages. ...
  49. The RM Destination requires the WS-SecureConversation protocol in the binding. This is likely caused by a binding mismatch. ...
  50. The RM source does not support an RM destination initiated close since messages can be lost. The reliable session cannot ...
  51. The RM source does not support an RM destination initiated termination since messages can be lost. The reliable session cannot ...
  52. The RM source received multiple CreateSequenceResponse messages with different sequence identifiers over the same session. ...
  53. The Role for the End with the EntitySet {0} in the AssociationSet {1} was not supplied and the End found matches one that ...
  54. The RoleProvider {0} specified in the configuration is invalid. No such provider was found registered under system.web/roleManager/providers. ...
  55. The root activity type is invalid. A root activity must inherit from the CompositeActivity class and must not have a Parent. ...
  56. The root activity's argument settings are incorrect. Either fix the workflow definition or supply input values to fix these ...
  57. The root element for the request could not be determined. When RoutingStyle is set to RequestElement, SoapExtensions configured ...
  58. The root element of a configuration file is the configuration element. The configuration element contains individual elements ...
  59. The root folder of the Web server (for example, \inetpub\wwwroot) might contain a Web.config file that has settings that ...
  60. The root map at position '{0}' (zero-based) does not match the map(s) that preceded it. Please ensure that all maps represent ...
  61. The root of a Template content section cannot contain an element of type '{0}'. Only FrameworkElement and FrameworkContentElement ...
  62. The route parameter name '{0}' is invalid. Route parameter names must be non-empty and cannot contain these characters: "{", ...
  63. The route parameter name '{0}' is invalid. Route parameter names must be non-empty and cannot contain these characters: "{", ...
  64. The route URL separator character '/' cannot appear consecutively. It must be separated by either a parameter or a literal ...
  65. The Routing Service is processing a message with ID: '{0}', Action: '{1}', Inbound URL: '{2}' Received in Transaction: {3}. ...
  66. The runtime cannot be configured with a transaction by an activity which is contained within a no persistence scope. An ancestor ...
  67. The runtime has encountered a fatal error. The address of the error was at 1$08x, on thread 2$x. The error code is 3$08x. ...
  68. The runtime transaction has been set by Activity '%1', DisplayName: '%2', InstanceId: '%3'. Execution isolated to Activity ...
  69. The runtime transaction has been set by Activity '{0}', DisplayName: '{1}', InstanceId: '{2}'. Execution isolated to Activity ...
  70. The runtime transaction is currently suppressed. Executing the TransactedReceiveScope activity '{0}' when the runtime transaction ...
  71. The runtime transaction is currently suppressed. Executing the TransactedScope activity '{0}' while the runtime transaction ...
  72. The same assembly was loaded into multiple contexts of an application domain. This might lead to runtime failures. It is ...
  73. The SamlAssertion being read did not contain any SamlStatement. A SamlAssertion must contain at least one SamlStatement. ...
  74. The SamlAssertion has been signed with a token that was not validated according to the protocol. If you are using X.509 certificates, ...
  75. The SamlAssertion is signed but the tolen that signed the SamlAssertion cannot be found. Ensure that the SecurityTokenResolver ...
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)