UI Translation

BizTalk Server 2006 R2

  1. A BAS parameter schema must be annotated with one or more role link types. Select "Role Link Types" property in the properties ...
  2. A BizTalk message could not be created from the MSMQ message. Details: %1. The message was dropped during a non-transactional ...
  3. A BizTalk Server Group contains the configuration information used across all hosts and applications contained in the group. ...
  4. A BizTalk Server Group is a collection of settings that govern the way BizTalk Server behaves and the data stores it uses. ...
  5. A body part or a part with the same name has already been added to this message. A message can have only one body part and ...
  6. A BTS MIME error was encountered when attempting to decode an AS2 message. AS2-From: {0}, AS2-To: {1}, MessageId: {2}, Error: ...
  7. A business process defines how the information from RFID tags is processed and stored. You can create and manage processes, ...
  8. A call to retrieve the list of fact retrievers on the constraint administration component failed with the following error. ...
  9. A connection could not be established to the device. Either the device is offline or the given credentials were incorrect.{0}Reason ...
  10. A connection could not be established to the device. To view the last known properties of the device or to modify the connection ...
  11. A connection is not possible to the specified device as the name of the provider is null. Specify a valid provider name in ...
  12. A custom wrapper for this COM component has been installed on your machine after you added this reference. This wrapper may ...
  13. A data dimension cannot be defined. Please define at least one alias of text business data before defining a data dimension. ...
  14. A data item or milestone with the same name already exists. Please choose a different name for the data item or milestone. ...
  15. A dependent schema used by the Source schema in the above map file has been changed outside the editor. Do you wish to reload ...
  16. A dependent schema used by the Target Schema in the above map file has been changed outside the editor. Do you wish to reload ...
  17. A device identifier was not reported by the provider for device %1 at %2 either during discovery or during a connection attempt. ...
  18. A device identifier was not specified by the provider for device {0} at {1}. There must be a specified device identifier ...
  19. A device reads RFID tags and communicates the tag information to BizTalk RFID. You can create and configure devices, and ...
  20. A different BAS site URL: '%1' has already been configured for use with this BizTalk group. By proceeding, you will overwrite ...
  21. A direct binding implies that the port does not connect to a fixed endpoint, but instead connects directly to the MessageBox ...
  22. a direct bound partner port must be annotated with a DirectBindingAttribute with two arguments referring to the current service ...
  23. a direct or indirect reference to a messagetype containing custom formatted user classes as parts is not permitted under ...
  24. A discovery event with updated connection information was discarded because the service failed to connect based on the new ...
  25. A discovery event with updated connection information was discarded because the service failed to connect based on the new ...
  26. A domain controller for the specified domain could not be located. Verify that the specified domain is correct, available, ...
  27. A duplicate attribute exists with the same name and namespace in the current scope. Two attributes in the same scope cannot ...
  28. A duplicate element exists with the same name in the current scope. Two elements in the same scope which have same name should ...
  29. A duplicate element exists with the same name in the current scope. Two elements under the schema node cannot have the same ...
  30. A failure occured in processing Edifact message on send port {0}. No agreement exists for receiver and sender identifier/qualifer ...
  31. A failure occured in processing Edifact message on send port {0}. No agreement exists for receiver and sender identifier/qualifer ...
  32. A failure occured in processing X12 message on send port {0}. No agreement exists for receiver and sender identifier/qualifer ...
  33. A failure occured in processing X12 message on send port {0}. No agreement exists for receiver and sender identifier/qualifer ...
  34. A failure occurred when connecting to the BizTalk management database %1. Please verify the Windows account used by the BizTalk ...
  35. A failure occurred when moving the file from the spooling folder to the destination folder. Please verify the destination ...
  36. A failure occurred when registering the BizTalk Server NT service control handler with the Windows service control manager. ...
  37. A failure occurred while evaluating the distinguished field {0} against the message part data. The message part data does ...
  38. A failure occurred while evaluating the property {0} against the message part data. The message part data does not contain ...
  39. A failure occurred while installing the Windows NT service %1. Please verify the following: 1) The credentials supplied are ...
  40. A failure occurred while trying to create XPaths for XLANG/s properties on a type '{0}'. This could happen if the XLANG/s ...
  41. A file load exception occurred while attempting to install the assembly into the Global Assembly Cache. This error may occur ...
  42. A file name must contain letters, numbers, spaces, or the characters . $ % ' - _ @ { } ~ ` ! # ( ) and have no more than ...
  43. A file not found exception occurred while reflecting BizTalk assembly "{0}". This problem may occur if one or more dependencies ...
  44. A file or folder with the name '%1' already exists on disk at this location. Please choose another name. If this file or ...
  45. A file or folder with the name '%1' already exists. Provide a unique name for the item you are adding, or delete the existing ...
  46. A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
  47. A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
  48. A file that is required cannot be installed because the cabinet file 2 is not digitally signed. This may indicate that the ...
  49. A group must consist of at least 2 or more business milestones from the same activity. Please redefine the activities to ...
  50. A Host Instance is a run-time instance of a host. It runs within the security boundaries of the host and executes message ...
  51. A host is a logical container representing one or more BizTalk Server run-time instances. It represents a virtual process ...
  52. A large number of records exist for this aggregate. Only the first %1 records will be displayed. In addition, there is an ...
  53. A lock file is used to handle multiple clients. Enter the name of the lock file to check for when logging on to the FTP server ...
  54. A logical device binds an RFID process to devices or device groups. For example, you can bind a logical device named "Shipping" ...
  55. A lower and/or a higher range have been specified for a default value {0} that is non-numeric. Since it is non-numeric the ...
  56. A Map with Source Schema '{0}' is already referenced by the ReceivePort '{1}'. Map with same Source Schema cannot be referenced ...
  57. A Map with Source Schema '{0}' is already referenced by the SendPort '{1}'. Map with same Source Schema cannot be referenced ...
  58. A Mass-Copy functoid is connected to the target tree, but there is code being generated at child nodes of this Target Node. ...
  59. A message going to a one-way send port is being suspended. Reason:The send port configuration corresponding to the message ...
  60. A message queuing error (error code -2147024891) has been thrown. This might occur if using a local user for impersonation ...
  61. A message received by adapter "%3" on receive location "%5" with URI "%4" is suspended. Error details: %6 MessageId: %1 InstanceID: ...
  62. A message sent to adapter "%3" on send port "%5" with URI "%4" is suspended. Error details: %6 MessageId: %1 InstanceID: ...
  63. A message was encountered with root element name of {0}. It could not be classified as an X12 or Edifact message. The root ...
  64. A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. Verify that you ...
  65. A moniker that identifies the send port location. A default value is generated based on the connection string property, using ...
  66. A moniker that uniquely identifies the receive location. The URI value is generated based on the connection string property, ...
  67. A new device has been added based on a discovery event. Its name %1 was automatically generated by Microsoft BizTalk RFID ...
  68. A newly discovered device with name %1 and device information %2 was successfully added to the RFID store in an unconfigured ...
  69. A non-loop transition with the specified child step already exists. Steps can be the child of only one non-loop transition ...
  70. A NULL property bag input parameter was found. To load and save the pipeline component values, please provide a valid property ...
  71. A numeric range dimension cannot be defined. Please define at least one alias of integer or decimal business data or durations ...
  72. A partial set has been detected but a valid full backup set does not exist yet. Please force a full backup on the source ...
  73. A Partner Profile provides information about a partner company. Business Activity Services uses profiles to create relationships ...
  74. A persistence exception has occured during the batch submission in the batching Orchestration. Party Id = {0}, ErrorMessage ...
  75. A physical (declarative with shortcut) binding implies that the endpoint port is created in the orchestration and bound to ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)