UI Translation

BizTalk Server 2006 R2

  1. The Messaging Engine encountered an error transmitting a message; this message will be moved to the next backup transport. ...
  2. The Messaging Engine encountered an error when creating the receive adapter "%1". The Assembly is: "%2". The error occurred ...
  3. The Messaging Engine encountered an error when moving one or more messages to their backup transport. All backup transports ...
  4. The Messaging Engine encountered an error while committing a batch to the database for a transport adapter. Attempting to ...
  5. The Messaging Engine encountered an unexpected error while trying to suspend messages received by adapter "%1" that failed ...
  6. The Messaging Engine encountered errors when initializing the receive adapter cache. Verify the protocol configurations are ...
  7. The Messaging Engine encountered errors when initializing the transmit adapter cache. Verify the protocol configurations ...
  8. The Messaging Engine failed to create the receive adapter "%1". InboundAssemblyPath: "%2" InboundTypeName: "%3" Exception ...
  9. The Messaging Engine failed to create the transport adapter "%1". OutboundAssemblyPath: "%2" OutboundTypeName: "%3" Exception ...
  10. The Messaging Engine failed to create the transport adapter "%1". The Adapter's CLSID is:"%2". The component does not implement ...
  11. The Messaging Engine failed to create the transport adapter "%1". The Assembly is: "%2". The component does not implement ...
  12. The Messaging Engine failed to initialize when processing an adapter work batch. Therefore, this batch cannot be processed. ...
  13. The Messaging Engine failed to register an adapter "%1". Details: "Registering multiple adapter types within the same process ...
  14. The Messaging Engine failed to register the adapter for "%1" for the receive location "%2". Please verify that the receive ...
  15. The Messaging engine failed to resolve the receive location "%1" with URL "%2" to the receive adapter "%3". If this adapter ...
  16. The Messaging Engine failed to send the message to the two-way dynamic send port "%3" for the following URL "%1". The chosen ...
  17. The Messaging Engine failed to update the configuration database because it had to shut down the receive location "%1" with ...
  18. The Messaging Engine failed to update the configuration for the receive location "%1" with URL "%2" for adapter "%3". Reason: ...
  19. The Messaging Engine failed while executing the inbound map for a recoverable interchange message on Receive Port "%1" with ...
  20. The Messaging Engine failed while executing the inbound map for the message coming from source URL:"%1" with the Message ...
  21. The Messaging Engine failed while executing the inbound map for the response message coming from the destination URL "%1" ...
  22. The Messaging Engine failed while executing the outbound map for the message going to the destination URL "%1" with the Message ...
  23. The Messaging Engine failed while executing the outbound map for the response message going to source URL:"%1" with the Message ...
  24. The Messaging engine has throttled all inbound messages for the host "%1" due to high stress levels on the MessageBox database. ...
  25. The Messaging Engine is dropping the message due to authentication failure. This may be because party resolution has failed ...
  26. The Messaging Engine received an error from transport adapter "%1" when notifying the adapter with the BatchComplete event. ...
  27. The Messaging Engine was unable to read the cache refresh interval from the database. Therfore, the default value of 60 will ...
  28. The Messaging Engine was unable to shutdown the following receive location: "%1". This is because of an out of memory error ...
  29. The method "%1" of the BizTalk Server WMI provider class "%2" cannot be executed because of a failure to retrieve the class. ...
  30. The method "%1" of the BizTalk Server WMI provider class "%2" cannot be executed because of a failure to retrieve the method ...
  31. The method "%1" of the BizTalk Server WMI provider class "%2" cannot be executed because of a failure to set the parameter ...
  32. The method {0} has timed out. If this is a provider/device operation, the timeout can occur if the provider/device could ...
  33. The Microsoft BizTalk RFID service could not start because its version has expired. Use an updated version of Microsoft BizTalk ...
  34. The Microsoft BizTalk RFID service could not start because the evaluation period for the product has ended. You can migrate ...
  35. The Microsoft BizTalk RFID service failed to start because of exception {0}. Resolve the issue that is causing the exception, ...
  36. The Microsoft BizTalk RFID service failed to start: %1. Resolve the issue that is causing the exception, and then restart ...
  37. The Microsoft BizTalk RFID service has encountered an internal error. Details: {0}. Try restarting the Microsoft BizTalk ...
  38. The Microsoft BizTalk RFID service has encountered an unhandled exception. BizTalk RFID will attempt to log the exception ...
  39. The Microsoft Commerce Server Core library is missing, not registered, or could not load properly. Please reinstall Commerce ...
  40. The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service ...
  41. The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service ...
  42. The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service ...
  43. The Microsoft Office InfoPath integration feature cannot be used with non-XML or invalid XML messages. The current settings ...
  44. The Microsoft SQL Server 2000 Analysis Services Decision Support Objects (DSO) component is installed on the local machine. ...
  45. The Microsoft SQL Server 2000 Analysis Services Decision Support Objects (DSO) component is not installed on the local machine. ...
  46. The Microsoft Windows Management Instrumentation (WMI) layer encapsulates all administrative functions and management capabilities ...
  47. The migration utility failed because Microsoft BizTalk Server 2006 R2 is not installed. Install Microsoft BizTalk Server ...
  48. The MIME decoder cannot find a MIME part for the specified content-type. Either there was no matching content-type or there ...
  49. The MIME decoder failed to decrypt the message because the certificate has private key protection turned on or the private ...
  50. The MIME encoder failed to sign the message because the certificate has private key protection turned on or the private key ...
  51. The module '{0}' depends on the module '{1}' which has not been initialized. Either the module is not configured in web.config ...
  52. The MSMQ adapter does not support receiving messages non-transactionally. Check the transaction property that you have specified. ...
  53. The MSMQ adapter is unable to process messages at the send port %1. Reason: %2 Correct the error and restart the Biztalk ...
  54. The MSMQ adapter is unable to process messages from receive location %1. Correct the error in the event log and restart this ...
  55. The MSMQT subservice encountered an error executing initialization of the networking component. The binding IP address may ...
  56. The name %1 cannot be used Active Directory and DNS registration. The name must fit Windows requirements and cannot be the ...
  57. The name entered contains invalid characters. User-defined names may not begin with a space ( ) or a number (0 1 2 3 4 5 ...
  58. The name of one or more sources specified in the property XML does not match the names of the sources on the device. Make ...
  59. The name of the database into which the sink schema will be installed. The database will be created if it does not exist. ...
  60. The name of the profile you want to use in this agreement. In the Select My Profile window, select the self profile you want ...
  61. The name of the project's primary output file (also known as the BizTalk assembly). This property reflects the current value ...
  62. The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to ...
  63. The name, {0}, contains invalid characters or whitespace. User defined names may not begin with a space or a number, may ...
  64. The names of the sources for the device could not be retrieved. To view the last known properties of the device, or to modify ...
  65. The namespace of the property schema with location "{0}" has changed since the last time it was added into this schema. Change ...
  66. The namespace of the schema you are trying to add clashes with one of the namespaces already declared. Please choose another ...
  67. The network clients for the Distributed Transaction Coordinator (DTC) Network must have the remote clients/transactions option ...
  68. The new started synchronization has detected that the previously run synchronization has not been finalized. As a result, ...
  69. The node name you typed contains characters which are not valid for XML Schema. Click the 'OK' button to encode the name ...
  70. The number of commands in this batch of commands {0} if combined with the number of existing commands being processed would ...
  71. The number of elements in the source collection is greater than the available space from '{0}' to the end of the destination ...
  72. The number of levels of slicer dimension '{0}' for alert '{1}' must be less than or equal to the maximum number of levels ...
  73. The number of parameters supplied for activation block ID {0} of activity model {1} does not equal the number expected. Expected ...
  74. The number of sources specified in the XML does not match the number of sources on the device. Make sure that the number ...
  75. The Odette File Transfer Protocol (OFTP) (Odette File Transfer Protocol ) subsystem reported an error. Check the details. ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)