UI Translation

BizTalk Server 2006 R2

  1. Click Repair to repair the installation of ProductName]. If you want to review or change any of your installation settings, ...
  2. Click this link to define how BizTalk Server generates acknowledgments in response to EDIFACT-encoded interchanges received ...
  3. Click this link to define how BizTalk Server generates acknowledgments in response to X12-encoded interchanges received from ...
  4. Click this link to define how BizTalk Server generates EDIFACT-encoded interchanges to send to the party, and how BizTalk ...
  5. Click this link to define how BizTalk Server generates the envelope for an EDIFACT-encoded interchange that it sends to the ...
  6. Click this link to define how BizTalk Server generates the envelope for an EDIFACT-encoded interchange that it sends when ...
  7. Click this link to define how BizTalk Server generates the envelope for an EDIFACT-encoded interchange that it sends when ...
  8. Click this link to define how BizTalk Server generates the envelope for an X12-encoded interchange that it sends to the party. ...
  9. Click this link to define how BizTalk Server generates the GS and ST segments for an X12-encoded interchange that it sends ...
  10. Click this link to define how BizTalk Server generates the GS and ST segments for an X12-encoded interchange that it sends ...
  11. Click this link to define how BizTalk Server generates the ISA segment for an X12-encoded interchange that it sends to the ...
  12. Click this link to define how BizTalk Server generates the ISA segment for an X12-encoded interchange that it sends when ...
  13. Click this link to define how BizTalk Server generates the UNA segment for an EDIFACT-encoded interchange that it sends to ...
  14. Click this link to define how BizTalk Server generates the UNA segment for an EDIFACT-encoded interchange that it sends when ...
  15. Click this link to define how BizTalk Server generates the UNB segment for an EDIFACT-encoded interchange that it sends to ...
  16. Click this link to define how BizTalk Server generates the UNB segment for an EDIFACT-encoded interchange that it sends when ...
  17. Click this link to define how BizTalk Server generates the UNG and UNH segments for an EDIFACT-encoded interchange that it ...
  18. Click this link to define how BizTalk Server generates the UNG and UNH segments for an EDIFACT-encoded interchange that it ...
  19. Click this link to define how BizTalk Server generates X12-encoded interchanges to send to the party, and how BizTalk Server ...
  20. Click this link to define how BizTalk Server processes acknowledgments received from the party in response to EDIFACT-encoded ...
  21. Click this link to define how BizTalk Server processes acknowledgments received from the party in response to X12-encoded ...
  22. Click this link to define how BizTalk Server processes EDIFACT-encoded interchanges sent by the party to BizTalk Server, ...
  23. Click this link to define how BizTalk Server processes the envelope and transaction sets of an EDIFACT-encoded interchange ...
  24. Click this link to define how BizTalk Server processes the envelope and transaction sets of an EDIFACT-encoded interchange ...
  25. Click this link to define how BizTalk Server processes the envelope and transaction sets of an X12-encoded interchange received ...
  26. Click this link to define how BizTalk Server processes the envelope and transaction sets of an X12-encoded interchange that ...
  27. Click this link to define how BizTalk Server processes X12-encoded interchanges sent by the party to BizTalk Server, and ...
  28. Column {0} has invalid hexadecimal value for field {1} in row {2}. A valid value for this field should contain an even number ...
  29. COMMANDS - {4} - PARAMETERS - All commands except {5} and {6} have optional '{7}' and '{8}' parameters, which default to ...
  30. Commits all BtsCatalogExplorer object changes to the database since the last time SaveChanges or SaveChangesWithTransaction ...
  31. Complete product including Rfid Service, Client Tools, Management Tools, Documentation and Sample Source code for RFID Provider ...
  32. Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
  33. Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
  34. Component {0} threw exception during initialization. Details: {1}. Resolve the issue that is causing the exception, and then ...
  35. Component {0} took too long to execute. Consider increasing the Single Event Processing Timeout parameter in the binding, ...
  36. Computer names must be used for the "GeneratorServerName", "ProviderServerName", and "DistributorServerName" properties for ...
  37. Concept for elevating pieces of message content, identified by source XPath, to an associated property collection using either ...
  38. Conditions run in sequence until a condition evaluates to TRUE. If no condition evaluates to TRUE, the Else condition runs. ...
  39. Configuration error. The message compression doesn't match the expected value. Contact the sending partner and verify compression ...
  40. Configuration error. The message compression doesn't match the expected value. Contact the sending partner and verify compression ...
  41. Configuration error. The message encryption doesn't match the expected value. Contact the sending partner and verify encryption ...
  42. Configuration error. The message encryption doesn't match the expected value. Contact the sending partner and verify encryption ...
  43. Configuration error. The message signature doesn't match the signature configured for this party. Contact the sending partner ...
  44. Configuration error. The message signature doesn't match the signature configured for this party. Contact the sending partner ...
  45. Configuration error. The message signing doesn't match the expected value. Contact the sending partner and verify signature ...
  46. Configuration error. The message signing doesn't match the expected value. Contact the sending partner and verify signature ...
  47. Configuration Failed. Please check the Config.log at the emp% directory for more information. emp%\config.xml contains passwords ...
  48. Configuration object failed to initialize because Commerce Server Developer Edition supports a maximum of four processors ...
  49. Configuration object failed to initialize because Commerce Server Standard Edition supports a maximum of two processors (CPUs). ...
  50. Configuration parameter {0} has an invalid value {1}. For further details on the valid values for this parameter, refer to ...
  51. Configuration results are listed in the following table. Please review the log file to determine how to correct this problem. ...
  52. Conflicting binding properties: MsmqAuthenticationMode={0} and MsmqProtectionLevel={1} is invalid. Change one of the properties ...
  53. Connection to configuration database has failed. Check if SQL Server is running and Distributed Transaction Coordinator service ...
  54. Connection to device {0} cannot be closed because the supplied connection GUID does not match an existing connection. Verify ...
  55. Constructor for class {0} in assembly {1} does not exist, is not accessible, or does not contain a signature matching the ...
  56. Context property with DateTime type cannot be demoted into the message content. All properties of DateTime type must be converted ...
  57. CopyTo() method can only work with single-dimensional arrays. Specifically, in this case, it cannot copy data into the {0}-dimensional ...
  58. Could not connect to the cluster. This could be due to the following: 1) BizTalk Host instances are not installed on MSCS ...
  59. Could not create a Microsoft Message Queuing (MSMQ) queue with name {0}. Either the queue already exists or the RFID Service ...
  60. Could not create key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  61. Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  62. Could not create the group hierarchy because of the following reason: {0}. Resolve the issue causing the error, and then ...
  63. Could not delete key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  64. Could not delete pipeline "{0}". Two or more receive ports, receive locations, or send ports are referencing the pipeline. ...
  65. Could not delete pipeline "{0}". Two or more receive ports, receive locations, or send ports are referencing the pipeline. ...
  66. Could not delete value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact ...
  67. Could not determine the location of the RFID data folder because the DataDir registry value could not be retrieved. Try repairing ...
  68. Could not determine whether '%1' is a multifile assembly. The assembly manifest may be corrupt. Assuming a non-multifile ...
  69. Could not find a component in assembly "{0}". Verify whether there is an event handler implementation in the assembly and ...
  70. Could not find a wrapper assembly for the COM component '%1'. %2 You can choose to create your own wrapper or a custom wrapper ...
  71. Could not find the registry key for the RFID service expiry date. Try restarting the Microsoft BizTalk RFID service. If this ...
  72. Could not find the RFID store {1} in the server {0}. Check if the database was created successfully. If the database does ...
  73. Could not get detail records for this aggregate. Make sure that permissions to obtain drillthrough records are set properly ...
  74. Could not get sub key names for key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact ...
  75. Could not get the group hierarchy of the device because of the following reason {0}. Resolve the issue causing the error, ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)