UI Translation

BizTalk Server 2006 R2

  1. The control 3 on dialog 2 can accept property values that are at most 5 characters long. The value 4 exceeds this limit, ...
  2. The control 3 on dialog 2 needs the icon 4 in size 5]x[5], but that size is not available. Loading the first available size ...
  3. The control 3 on dialog 2 received a browse event, but there is no configurable directory for the present selection. Likely ...
  4. The correct version of Microsoft Windows SharePoint Services was not detected on your computer. Install Microsoft Windows ...
  5. The current action cannot be completed because the server is not configured for alerting. Ask your System Administrator to ...
  6. The current action caused an error that could indicate a configuration problem. Contact your administrator for technical ...
  7. The current definition being parsed is {0}. The stream offset where the error occured is {1}. The line number where the error ...
  8. The current ranges defined overlap. Please distinguish from having any overlapping ranges. For example, a valid set of ranges ...
  9. The current threshold for the memory usage of current process (MB). The threshold may be dynamically adjusted depending on ...
  10. The custom envelope generator could not locate the XML node for the custom envelope "%1" with the property "%2". This document ...
  11. The data contains a field value ("%1") that does not meet the minimum length requirement for tag "%2". The minimum length ...
  12. The data type is not compatible with the contents of the element. A date/time value may have a custom format that needs to ...
  13. The database "{0}" on the server "{1}" is partially compatible with the version of the product installed on this computer. ...
  14. The database "{0}:{1}" associated with the deployment driver does not match the database "{2}:{3}" specified during product ...
  15. The database %1 on server %2 is not compatible with the current version of BizTalk. Please specify a different database name ...
  16. The database %1 on server %2 is not compatible with the version of Microsoft BizTalk Server you are trying to configure. ...
  17. The database operation failed because it was using a distributed transaction which was cancelled by the transaction manager. ...
  18. The database server you specified already contains BizTalk databases. To perform a basic configuration, you have to provide ...
  19. The database server you specified cannot be reached. Make sure you have specified the correct server name and that the server ...
  20. The database server {0} you specified cannot be reached. Make sure you have specified the correct server name and that the ...
  21. The database type {0} for the name {1} does not have the required DatabaseAssembler attribute required to build the database ...
  22. The database you have chosen needs to be upgraded to HWS RTM version. Please apply upgrade script to the database before ...
  23. The database {1} already exists on server {0} and is not a compatible BizTalk database. Please specify a different database ...
  24. The database {1} on server {0} is not compatible with the version of Microsoft BizTalk Server you are trying to configure. ...
  25. The database {3} on server {2} has the incorrect SQL Server Sink schema code version {0}. The expected version is {1}. Delete ...
  26. The database {3} on server {2} has the incorrect SQL Server Sink schema version {0}. The expected version is {1}. Delete ...
  27. The Date or Time value received for Field: {0} is incorrect. Make sure the date time value is valid and generated record ...
  28. The decimal value of the initial part of the service class GUID that this performance counter instance corresponds to. A ...
  29. The decoder could not verify the validity of the message because the required signer certificate was not found in the "Local ...
  30. The dedicated command execution timed out after {0} milliseconds. The provider might still be processing the command. Retry ...
  31. The default application name has been provided for you. You can change the name or accept the name given. It is recommended ...
  32. The default property schema has been changed in another document. Please save or discard changes before using the 'Quick ...
  33. The default Web access mode for this project is set to file share, but the project folder at '%1' cannot be opened with the ...
  34. The default Web access mode for this project is set to FrontPage, but the project folder at '%1' cannot be opened with FrontPage. ...
  35. The defaultAnonymous catalogset ('{0}') as specified in the CommerceServer\catalog\catalogSets section of web.config does ...
  36. The defaultAuthenticated catalogset ('{0}') as specified in the CommerceServer\catalog\catalogSets section of web.config ...
  37. The deployed schema is attempting to promote a message element into the property "{0}" (msgType="{1}"). This property is ...
  38. The destination identifier's "%1" qualifier is too long for the output header. Please update the port with a shorter qualifier. ...
  39. The destination identifier's "%1" value is too long for the output header. Please update the port with a shorter identifier. ...
  40. The destination node "{0}" has {1} logical functoid input(s). The maximum number of possible logical functoid inputs to this ...
  41. The destination node "{0}" is linked to by two source nodes ("{1}" and "{2}") that are from different but conflicting Equivalent ...
  42. The destination queue depth of all messagebox databases exceeds the threshold. If the host publishes to multiple queues, ...
  43. The destination queue depth of all messagebox databases. If the host publishes to multiple hosts, the weighted average across ...
  44. The device %1 might be in a bad state because an operation failed on the device while attempting to recover from a device ...
  45. The device group information in the given .xml file is not valid. The root of the group hierarchy should be RootDeviceGroup. ...
  46. The device information or name for device %1 at %2 with device identifier %3 could not be processed because it affects one ...
  47. The device or process {0} is in a corrupted state in the RFID store. If this situation persists, delete and re-add the affected ...
  48. The device {0} could not be deleted from the RFID store because of a database exception. For more information, look at the ...
  49. The directory for the log file does not exist. Verify that the directory specified for the logfile in the rfid.config file ...
  50. The disassembler cannot retrieve the document specification using this type: "%1". This is because the schema is not deployed ...
  51. The display format string describes how the vocabulary definition is displayed in rule conditions and actions. For example, ...
  52. The display format string describes how the vocabulary definition is displayed in rule conditions and actions. For example, ...
  53. The displayed order of the antenna names might not match the device antenna sequence property. This is because the names ...
  54. The document or segment count contained in tag "%1" (%2) does not match the number of documents or segments processed (%3). ...
  55. The document specification from assembly failed to load. Verify the schema for this document specification is deployed and ...
  56. The duration, in minutes, that the SQL Adapter waits before attempting to poll the database and submit the message batch ...
  57. The EDI Subsystem service is disabled. If you have deployed EDI schemas then you must manually start the EDI Subsystem service ...
  58. The Edifact acknowledgement was generated by the system. However, it is missing a context property for Delimiter Set. It ...
  59. The Edifact Transaction set had a mismatched count in UNT01. UNT01 was {0}, whereas it should have been {1}. It has been ...
  60. The edition of Microsoft BizTalk RFID could not be determined. The service will continue to run but certain features might ...
  61. The Engine feature contains components for performing messaging, orchestration, and tracking functions. This is the core ...
  62. The envelope name "%1" does not reference a valid envelope for the BizTalk Server parser. Either the envelope name does not ...
  63. The error handling options "Disable location on failure" and "Suspend request message on failure" should not both be set ...
  64. The error occurred while loading the document. Fix the error, and then try loading the document again. The error message ...
  65. The evaluationContextHandle object provided to the ExpressionEvaluator.EvaluateInContext() method is not a valid Commerce.EvalCtxtToken. ...
  66. The Event Log Error Threshold was reached. The adapter will continue polling, but further event log entries will be suppressed. ...
  67. The event types that will be persisted. The default is to persist all event types. This parameter expects assembly qualified ...
  68. The execution of stored procedure {0} failed. Please check that the stored procedure exists and the permissions are set appropriately. ...
  69. The existing receive port "{0}" is incompatible with the binding information. (Delete or rename the receive port to update.) ...
  70. The expected parameter '{0}' for the BAS artifact is either missing or invalid. The parameter 'Name' cannot be empty. The ...
  71. The Export XML dialog cannot be launched. It may be that the workbook is hosted in internet explorer. Please use Save-As ...
  72. The faulted WCF service host at address {0} could not be restarted, and as a result no messages can be received on the corresponding ...
  73. The field is missing a start and an end position, and is referenced in the "%1" positional record. Specify valid start and ...
  74. The file '%1' is open in an editor with unsaved changes. Do you want to save your changes before invoking Open With on this ...
  75. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)