UI Translation

BizTalk Server 2010

  1. The message posted to a dynamic port had an incorrect URL format:"%1". The format should be in the following form: "protocol://address". ...
  2. The message produced by the receive pipeline: "%1" for receive location: "%2" has an invalid value(%3) for a message context ...
  3. The message size cannot be bigger than 4 GB (approximately 4,294,967,295 in bytes). Please specify a smaller message and ...
  4. The message was not decrypted because the decoder could not find the decryption certificate in the "Current User\Personal" ...
  5. The message was not found in the Message Box or the Tracking databases. This may be caused by one of the following conditions: ...
  6. The message was routed to a subscription based upon a non-unique correlation set. Please either clean up the data before ...
  7. The MessageBox cannot be deleted because it may still contain incomplete instances. Ensure that there are no incomplete instances ...
  8. The MessageBox cannot be deleted because it still contains tracking data. Restart the tracking host to move the data to the ...
  9. The MessageBox object is successfully deleted from the Management database but not all of the SQL replication configuration ...
  10. The messages will be processed in order or serially. Setting this property to true will also make optimal use of the resources ...
  11. The messages will be processed serially. Setting this property to true will enforce ordered delivery of messages and will ...
  12. The Messaging engine could not contact the SSO server to retrieve the endpoint configuration. Make sure that the SSO service ...
  13. The Messaging Engine could not find the receive location for URI:"%1".\ Please verify the receive location exists and is ...
  14. The Messaging Engine could not promote the message context properties after transformation of the message coming from source ...
  15. The Messaging Engine could not promote the message context properties after transformation of the message going to destination ...
  16. The Messaging Engine could not send the message because the destination party was not found. Verify that the destination ...
  17. The Messaging Engine could not send the message to the dynamic send port. The outbound transport could not be resolved because ...
  18. The Messaging Engine could not send the message to the dynamic send port. The outbound transport could not be resolved because ...
  19. The Messaging Engine did not recognize the InboundTransportLocation:Unknown. Please check the receive location configuration. ...
  20. The Messaging Engine encountered an error "%1" persisting one or more inbound messages. The batch being processed contained ...
  21. The Messaging Engine encountered an error committing a batch for the transport adapter "Unknown" containing %1 message(s) ...
  22. The Messaging Engine encountered an error committing a transport adapters batch containing the following work items: %1 message(s) ...
  23. The Messaging Engine encountered an error committing a transport adapters batch containing the following work items: %1 messages ...
  24. The Messaging Engine encountered an error creating the receive adapter "%1". The Assembly's CLSID is: "%2". The component ...
  25. The Messaging Engine encountered an error publishing a batch of "%1" messages to the Message Box database for the transport ...
  26. The Messaging Engine encountered an error transmitting a batch of %1 message(s); these messages will be moved to the next ...
  27. The Messaging Engine encountered an error transmitting a batch of %1 message(s); these messages will be resubmitted for transmission. ...
  28. The Messaging Engine encountered an error transmitting a message; this message will be moved to the next backup transport. ...
  29. The Messaging Engine encountered an error when creating the receive adapter "%1". The Assembly is: "%2". The error occurred ...
  30. The Messaging Engine encountered an error when moving one or more messages to their backup transport. All backup transports ...
  31. The Messaging Engine encountered an error while committing a batch to the database for a transport adapter. Attempting to ...
  32. The Messaging Engine encountered an unexpected error while trying to suspend messages received by adapter "%1" that failed ...
  33. The Messaging Engine encountered errors when initializing the receive adapter cache. Verify the protocol configurations are ...
  34. The Messaging Engine encountered errors when initializing the transmit adapter cache. Verify the protocol configurations ...
  35. The Messaging Engine failed to create the receive adapter "%1". InboundAssemblyPath: "%2" InboundTypeName: "%3" Exception ...
  36. The Messaging Engine failed to create the transport adapter "%1". OutboundAssemblyPath: "%2" OutboundTypeName: "%3" Exception ...
  37. The Messaging Engine failed to create the transport adapter "%1". The Adapter's CLSID is:"%2". The component does not implement ...
  38. The Messaging Engine failed to create the transport adapter "%1". The Assembly is: "%2". The component does not implement ...
  39. The Messaging Engine failed to initialize when processing an adapter work batch. Therefore, this batch cannot be processed. ...
  40. The Messaging Engine failed to register an adapter "%1". Details: "Registering multiple adapter types within the same process ...
  41. The Messaging Engine failed to register the adapter for "%1" for the receive location "%2". Please verify that the receive ...
  42. The Messaging engine failed to resolve the receive location "%1" with URL "%2" to the receive adapter "%3". If this adapter ...
  43. The Messaging Engine failed to send the message to the two-way dynamic send port "%3" for the following URL "%1". The chosen ...
  44. The Messaging Engine failed to update the configuration database because it had to shut down the receive location "%1" with ...
  45. The Messaging Engine failed to update the configuration for the receive location "%1" with URL "%2" for adapter "%3". Reason: ...
  46. The Messaging Engine failed while executing the inbound map for a recoverable interchange message on Receive Port "%1" with ...
  47. The Messaging Engine failed while executing the inbound map for the message coming from source URL:"%1" with the Message ...
  48. The Messaging Engine failed while executing the inbound map for the response message coming from the destination URL "%1" ...
  49. The Messaging Engine failed while executing the outbound map for the message going to the destination URL "%1" with the Message ...
  50. The Messaging Engine failed while executing the outbound map for the response message going to source URL:"%1" with the Message ...
  51. The Messaging engine has throttled all inbound messages for the host "%1" due to high stress levels on the MessageBox database. ...
  52. The Messaging Engine is dropping the message due to authentication failure. This may be because party resolution has failed ...
  53. The Messaging Engine received an error from transport adapter "%1" when notifying the adapter with the BatchComplete event. ...
  54. The Messaging Engine was unable to read the cache refresh interval from the database. Therfore, the default value of 60 will ...
  55. The Messaging Engine was unable to shutdown the following receive location: "%1". This is because of an out of memory error ...
  56. The method "%1" of the BizTalk Server WMI provider class "%2" cannot be executed because of a failure to retrieve the class. ...
  57. The method "%1" of the BizTalk Server WMI provider class "%2" cannot be executed because of a failure to retrieve the method ...
  58. The method "%1" of the BizTalk Server WMI provider class "%2" cannot be executed because of a failure to set the parameter ...
  59. The method {0} has timed out. If this is a provider/device operation, the timeout can occur if the provider/device could ...
  60. The Microsoft BizTalk RFID service could not start because its version has expired. Use an updated version of Microsoft BizTalk ...
  61. The Microsoft BizTalk RFID service could not start because the evaluation period for the product has ended. You can migrate ...
  62. The Microsoft BizTalk RFID service failed to start because of exception {0}. Resolve the issue that is causing the exception, ...
  63. The Microsoft BizTalk RFID service failed to start: %1. Resolve the issue that is causing the exception, and then restart ...
  64. The Microsoft BizTalk RFID service has encountered an internal error. Details: {0}. Try restarting the Microsoft BizTalk ...
  65. The Microsoft BizTalk RFID service has encountered an unhandled exception. BizTalk RFID will attempt to log the exception ...
  66. The Microsoft BizTalk RFID service is going to terminate because World Wide Web Publishing Service has stopped. To resolve ...
  67. The Microsoft BizTalk RFID service is going to terminate because World Wide Web Publishing Service has stopped. To resolve ...
  68. The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service ...
  69. The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service ...
  70. The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service ...
  71. The Microsoft Office InfoPath integration feature cannot be used with non-XML or invalid XML messages. The current settings ...
  72. The Microsoft Windows Management Instrumentation (WMI) layer encapsulates all administrative functions and management capabilities ...
  73. The migration utility failed because Microsoft BizTalk Server is not installed. Install Microsoft BizTalk Server, and then ...
  74. The MIME decoder cannot find a MIME part for the specified content-type. Either there was no matching content-type or there ...
  75. The MIME decoder failed to decrypt the message because the certificate has private key protection turned on or the private ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)