UI Translation

BizTalk Server 2006 R2

  1. The installer was interrupted before ProductName could be installed. You need to restart the installer to try again. Click ...
  2. The installer was interrupted before ProductName could be removed. You need to restart the installer to try again. Click ...
  3. The installer will create a network image at the following location. To create an image in this folder, click "Next". To ...
  4. The installer will install ProductName to the following folder. To install in this folder, click "Next". To install to a ...
  5. The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended. ...
  6. The instance is no longer valid. No operations can be performed on an instance after dehydration or completion of that instance. ...
  7. The instance was reactivated elsewhere and all work related to this instance should be abandoned. This could be due to a ...
  8. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error in/before the first functional ...
  9. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error. A likely cause is invalid segment ...
  10. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error. Last structurally valid functional ...
  11. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error. The part after the error is ...
  12. The interrupt URL for this HWS installation has not been specified in the configuration database. Use the HWS Management ...
  13. The Isolated host represents service instances that are created, deleted, and controlled outside of administration tools, ...
  14. The join key '%0' references more than one data member from a single source. A join key may map to only one member from a ...
  15. The key (ST01, Version/Release, Target Namespace) should be unique. ({0}, {1}, {2}) already exists, specify a different value. ...
  16. The key (UNH2.1, UNH2.2, UNH2.3, UNH2.5, Target Namespace) should be unique. ({0}, {1}, {2}, {3}, {4}) already exists, specify ...
  17. The key (UNH2.1, UNH2.2, UNH2.3, UNH2.5, UNG 2.1, UNG 2.2) should be unique. ({0}, {1}, {2}, {3}, {4}, {5}) already exists, ...
  18. The kill codes that were provided do not match. Ensure that the values typed in Kill Code and Confirm Kill Code are the same. ...
  19. The license key required to use Xceed FTP Library was not found or is invalid. Make sure that you have called the License ...
  20. The list below includes the drives you can install ProductName to, along with each drive's available and required disk space. ...
  21. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group ...
  22. The log file %1 that was provided in the configuration file cannot be used. Reason: %2. The default log file %3 will be used. ...
  23. The logon account does not have sufficient privileges to validate the account specified. On Windows 2000 the required privilege ...
  24. The Loop shape contains one Condition and represents a process that can be repeated. If the Condition evaluates to TRUE, ...
  25. The machine is part of a Windows cluster but clustering functionality is supported only in the Enterprise Edition of Microsoft ...
  26. The machine you are executing the script on is a 32 bit machine and the following script executable is found to be 64 bit. ...
  27. The machine you are installing on is a 32 bit machine and the following component is found to be 64 bit. Installation could ...
  28. The Management database on SQL Server "{0}" / database "{1}" is incompatible with the expected schema version of this BizTalk ...
  29. The map contains a functoid that is not registered on this machine. Please contact the original author to obtain the required ...
  30. The map contains a reference to a schema node that is not valid. Perhaps the schema has changed. Try reloading the map in ...
  31. The map contains following invalid functoid(s) and/or link(s). Please validate the contents of your map. Saving the map file ...
  32. The map contains invalid functoids and links. Please validate the contents of your map. Saving the map file will delete all ...
  33. The map contains invalid functoids. Please validate the contents of your map. Saving the map file will delete all references ...
  34. The map contains invalid links. Please validate the contents of your map. Saving the map file will delete all references ...
  35. The map contains the CustomXslt tag, but does not contain the CustomExtensionXml tag. You will need this file if you have ...
  36. The Map name should be of the form ' . ', where Project namespace and UniqueMapName are valid identifiers and UniqueMapName ...
  37. The map needs to be migrated from a previous version and cannot be compiled. Migrate this map file first before compiling ...
  38. The maximum number of archive tables can be referenced by the archive view is 256. Please manually combine some of the tables ...
  39. The maximum time (milliseconds) that one event may be processed in the process pipeline. If the event exceeds this time, ...
  40. The measure {0} defined for the alert {1} does not exist. Make sure that the name of the measure specified in the alert matches ...
  41. The member '{0}' of type '{1}' cannot have the Property attribute. This attribute may only be associated with primitive fields ...
  42. The message agent or one of its internal objects is not initialized or has been uninitialized due to incorrect calling semantics. ...
  43. The Message Box is the primary repository for active messages in the BizTalk Server system. For scalability, BizTalk Server ...
  44. The message cannot be routed to the batching orchestration as the Encoding type could not be determined. The encoding type ...
  45. The message context is no longer available. The message or associated service instance may have been terminated in another ...
  46. The message currently opened in the message viewer is marked for tracking. Message gets tracked by the BizTalk Server when ...
  47. The message found multiple request response subscriptions. A message can only be routed to a single request response subscription. ...
  48. The message from the file "%1" cannot be authenticated. The file has been deleted without processing because the receive ...
  49. The message posted to a dynamic port had an incorrect URL format:"%1". The format should be in the following form: "protocol://address". ...
  50. The message produced by the receive pipeline: "%1" for receive location: "%2" has an invalid value(%3) for a message context ...
  51. The message size cannot be bigger than 4 GB (approximately 4,294,967,295 in bytes). Please specify a smaller message and ...
  52. The message was not decrypted because the decoder could not find the decryption certificate in the "Current User\Personal" ...
  53. The message was not found in the Message Box or the Tracking databases. This may be caused by one of the following conditions: ...
  54. The message was routed to a subscription based upon a non-unique correlation set. Please either clean up the data before ...
  55. The MessageBox cannot be deleted because it may still contain incomplete instances. Ensure that there are no incomplete instances ...
  56. The MessageBox cannot be deleted because it still contains tracking data. Restart the tracking host to move the data to the ...
  57. The MessageBox object is successfully deleted from the Management database but not all of the SQL replication configuration ...
  58. The messages will be processed in order or serially. Setting this property to true will also make optimal use of the resources ...
  59. The messages will be processed serially. Setting this property to true will enforce ordered delivery of messages and will ...
  60. The Messaging engine could not contact the SSO server to retrieve the endpoint configuration. Make sure that the SSO service ...
  61. The Messaging Engine could not find the receive location for URI:"%1".\ Please verify the receive location exists and is ...
  62. The Messaging Engine could not promote the message context properties after transformation of the message coming from source ...
  63. The Messaging Engine could not promote the message context properties after transformation of the message going to destination ...
  64. The Messaging Engine could not send the message because the destination party was not found. Verify that the destination ...
  65. The Messaging Engine could not send the message to the dynamic send port. The outbound transport could not be resolved because ...
  66. The Messaging Engine could not send the message to the dynamic send port. The outbound transport could not be resolved because ...
  67. The Messaging Engine did not recognize the InboundTransportLocation:Unknown. Please check the receive location configuration. ...
  68. The Messaging Engine encountered an error "%1" persisting one or more inbound messages. The batch being processed contained ...
  69. The Messaging Engine encountered an error committing a batch for the transport adapter "Unknown" containing %1 message(s) ...
  70. The Messaging Engine encountered an error committing a transport adapters batch containing the following work items: %1 message(s) ...
  71. The Messaging Engine encountered an error committing a transport adapters batch containing the following work items: %1 messages ...
  72. The Messaging Engine encountered an error creating the receive adapter "%1". The Assembly's CLSID is: "%2". The component ...
  73. The Messaging Engine encountered an error publishing a batch of "%1" messages to the Message Box database for the transport ...
  74. The Messaging Engine encountered an error transmitting a batch of %1 message(s); these messages will be moved to the next ...
  75. The Messaging Engine encountered an error transmitting a batch of %1 message(s); these messages will be resubmitted for transmission. ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)