BizTalk Server 2010

  1. The destination queue depth of all messagebox databases. If the host publishes to multiple hosts, the weighted average across ...
  2. The device %1 might be in a bad state because an operation failed on the device while attempting to recover from a device ...
  3. The device group information in the given .xml file is not valid. The root of the group hierarchy should be RootDeviceGroup. ...
  4. The device information or name for device %1 at %2 with device identifier %3 could not be processed because it affects one ...
  5. The device or process {0} is in a corrupted state in the RFID store. If this situation persists, delete and re-add the affected ...
  6. The device {0} could not be deleted from the RFID store because of a database exception. For more information, look at the ...
  7. The directory for the log file does not exist. Verify that the directory specified for the logfile in the rfid.config file ...
  8. The disassembler cannot retrieve the document specification using this type: "%1". This is because the schema is not deployed ...
  9. The discovery message does not have any transport addresses that Biztalk RFID can recognize. Refer to the documentation for ...
  10. The discovery message has no EndpointReference specified or the EndpointReference does not have a valid URI. Refer to the ...
  11. The display format string describes how the vocabulary definition is displayed in rule conditions and actions. For example, ...
  12. The display format string describes how the vocabulary definition is displayed in rule conditions and actions. For example, ...
  13. The displayed order of the antenna names might not match the device antenna sequence property. This is because the names ...
  14. The document or segment count contained in tag "%1" (%2) does not match the number of documents or segments processed (%3). ...
  15. The document specification from assembly failed to load. Verify the schema for this document specification is deployed and ...
  16. The duration, in minutes, that the SQL Adapter waits before attempting to poll the database and submit the message batch ...
  17. The Edifact acknowledgement was generated by the system. However, it is missing a context property for Delimiter Set. It ...
  18. The Edifact Transaction set had a mismatched count in UNT01. UNT01 was {0}, whereas it should have been {1}. It has been ...
  19. The edition of Microsoft BizTalk RFID could not be determined. The service will continue to run but certain features might ...
  20. The Engine feature contains components for performing messaging, orchestration, and tracking functions. This is the core ...
  21. The envelope name "%1" does not reference a valid envelope for the BizTalk Server parser. Either the envelope name does not ...
  22. The error handling options "Disable location on failure" and "Suspend request message on failure" should not both be set ...
  23. The error occurred while loading the document. Fix the error, and then try loading the document again. The error message ...
  24. The Event Log Error Threshold was reached. The adapter will continue polling, but further event log entries will be suppressed. ...
  25. The event types that will be persisted. The default is to persist all event types. This parameter expects assembly qualified ...
  26. The execution of stored procedure {0} failed. Please check that the stored procedure exists and the permissions are set appropriately. ...
  27. The existing receive port "{0}" is incompatible with the binding information. (Delete or rename the receive port to update.) ...
  28. The exported settings xml does not confirm to the standard exported settings xml schema. Following is the error message received ...
  29. The external assembly with the fully qualified name "{0}" cannot be invoked. Make sure this assembly is in the global assembly ...
  30. The faulted WCF service host at address {0} could not be restarted, and as a result no messages can be received on the corresponding ...
  31. The field exceeds the maximum allowed length. The maximum allowed length for the field is {0} characters. The current value ...
  32. The field is missing a start and an end position, and is referenced in the "%1" positional record. Specify valid start and ...
  33. The file '%1' is open in an editor with unsaved changes. Do you want to save your changes before invoking Open With on this ...
  34. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
  35. The file 2][3 is being held in use{ by the following process: Name: 4], Id: 5], Window Title: '[6]'}. Close that application ...
  36. The file 2][3 is being held in use{ by the following process: Name: 4], ID: 5], Window Title: 6]}. Close that application ...
  37. The FILE adapter cannot disconnect from the network share %1. Please verify other modules do not use this network share. ...
  38. The FILE receive adapter cannot delete file %1. This file processed successfully. Please delete this file from the disk. ...
  39. The FILE receive adapter cannot process file %1 because of one of the following reasons: 1) The file is read-only. 2) The ...
  40. The FILE receive adapter for location "%1" was configured without a FILE mask. Please add the FILE mask to the configuration. ...
  41. The FILE send adapter cannot open file %1 for writing because it is associated with an unsupported device type. For information ...
  42. The file you are attempting to import is not valid. Please check that entity keys are unique and not already registered in ...
  43. The file you are attempting to import is not valid. Please check that the file exists, and that it is a valid UDDI resources ...
  44. The Final Property is used to indicate derivations which are not allowed from the type being defined. The default value is ...
  45. The Final property is used to indicate derivations which are not allowed from the type being defined. This is the default ...
  46. The first BizTalk Host must be an "In-Process" type host with the "Default host in group" and "Host tracking" options set. ...
  47. The first element of the batch exceeded the character count release criteria set. Please change the character count release ...
  48. The following applications are using files that need to be updated by this setup. Close these applications and then click ...
  49. The following applications from the bindings file are not present in the group. Do you want to continue importing bindings ...
  50. The following applications from the bindings file were found in the specified group: {0} Do you want to continue importing ...
  51. The following artifacts will be moved to the selected application. The list includes selected artifacts, dependencies, and ...
  52. The following categories cannot be associated with a parent category due to a parentKeyValue mismatch. Do you want to make ...
  53. The following condition has not been satisfied:(SqlCommandTimeout < RefreshInterval) And (SessionTimeout > 2 RefreshInterval) ...
  54. The following device versions were created due to configuration changes. To view changes between versions, press CTRL, select ...
  55. The following error occured when attempting to detect whether EDI batches were being processed or whether send ports or receive ...
  56. The following error was returned when trying to get the latest version of the project file: "%1" Do you want to open the ...
  57. The following exception: "%1" was thrown by MSMQ. This can be caused by a badly formatted queue path, if this is a Dynamic ...
  58. The following is a list of role links that require configuration for the application to start. Select the role link in the ...
  59. The following items could not be matched up to hosts due to name and/or trust level mismatches: Item: '{0}' Host: '{1}' Trust ...
  60. The following options or property keys are either not supported for the given resource type or the provided property value ...
  61. The following parties can not be migrated to the new party model. Please modify them in your existing deployment per the ...
  62. The following parties cannot be enlisted because they do not have send ports compatible with all operations in the role: ...
  63. The following platform components are missing and cannot be automatically installed on this computer because their language ...
  64. The following platform components failed to install and will need to be manually installed before setup can proceed: %1 Check ...
  65. The following properties cannot be promoted because they refer to schema nodes which are not fields or simple content records: ...
  66. The following registry keys for adapter configuration have been deprecated and their values will not be used. Corresponding ...
  67. The following required arguments for the event provider are missing: {0}. Please ensure the ADF file is correctly formatted. ...
  68. The following resources were not added to the application. They were either already present or were not dependencies for ...
  69. The following Schema file {0}, is not included in the Build. Set its Build Action to Compile to be able to perform any action ...
  70. The following Web Site that was packed from a 32 Bit IIS machine is being installed on to a 64 Bit IIS machine. The web site ...
  71. The following web site that was packed from a 64 bit IIS machine is being installed on to a 32 bit IIS machine. The web site ...
  72. The following Windows component may not be installed: Application Server -> Internet Information Services (IIS) -> Common ...
  73. The following Windows component may not be installed: Application Server -> Internet Information Services (IIS) -> World ...
  74. The format of the user name property is invalid for SPA authentication scheme. Make sure that the user name is specified ...
  75. The FTPS server did not accept the current security level of the FTP connection. Verify the SSL settings on the FTPS server ...