BizTalk Server 2010

  1. The Block property is used to prevent specific types of derivation to be used in place of this Node. The default value is ...
  2. The BTF disassembler is in the wrong internal state. Therefore, the next payload cannot be retrieved from the message being ...
  3. The BTF dissassembler is in the wrong internal state. Therefore, the input message cannot be loaded for the disassembly. ...
  4. The Business Activity and Monitoring Portal encountered and critical error and cannot perform the requested action. The server ...
  5. The Business Activity Monitoring (BAM) Portal is used to query individual instance data stored in the Tracking database. ...
  6. The business document passed in is not in a recognizable format. Therefore, the document could not be parsed or decrypted. ...
  7. The Business Rule Engine (BRE) component has not been configured. To configure it, run the Business Rules Configuration wizard. ...
  8. The Business Rules Engine (BRE) component has encountered an internal error: current event is null. If this situation persists, ...
  9. The cabinet file '[2]' required for this installation is corrupt and cannot be used. This could indicate a network error, ...
  10. The call to the Windows SharePoint Services adapter Web service has timed out. To fix this issue, increase the Timeout property ...
  11. The called orchestration instance you are viewing has completed. The Orchestration Debugger will be detached from the running ...
  12. The certificate could not be loaded from the certificate store using the specified thumbprint. Please do one of the following: ...
  13. The children of the "%1" delimited record must either be ALL records or ALL fields. Records with no tag identifier cannot ...
  14. The CIM_LogicalElement class is the base class for all the components of the system that represent abstract system components. ...
  15. The CIM_ManagedSystemElement class is the base class for the system element hierarchy. Membership criteria: any distinguishable ...
  16. The Cluster option allows you to provide high availability for ports that use MSMQ, FTP or POP3 adapters. Based on Microsoft ...
  17. The command execution failed due to error {0}. Resolve the issue that is causing the exception, and then retry the operation. ...
  18. The command execution timed out after {0} milliseconds. The provider might still be processing the command. Retry the operation ...
  19. The command you are attempting cannot be completed because the file '%1' that must be modified cannot be changed. If the ...
  20. The command you are attempting cannot be completed because the file '{0}' that must be modified cannot be changed. If the ...
  21. The communication pattern (one-way or request-response) of the corresponding port in the binding information is different. ...
  22. The compilation is using the CustomExtensionXml tag (specified in the Grid properties) along with the ExtensionXml that is ...
  23. The component that corresponds to assembly {0} and class {1} could not be deleted because it does not exist. Verify the assembly ...
  24. The computed port URI value {0} is too long. The value cannot be longer than {1} characters. To fix this issue you will have ...
  25. The computer name or domain name contains invalid characters or spaces.The invalid characters include ` ~ ! @ # $ % ^ *( ...
  26. The computer sites cannot be resolved. Please verify the subnets in your network are configured correctly in Active Directory. ...
  27. The config file template (0) was not found. Please Repair the installation and run configuration again to configure this ...
  28. The configuration file contains an invalid command time-out value. The command time-out must be between 1 second and 18000 ...
  29. The configuration file for Microsoft BizTalk RFID could not be located in the default data directory. Check if you have an ...
  30. The configuration file for Microsoft BizTalk RFID is not in a valid format. Verify that the data that is included in the ...
  31. The configuration file for Microsoft BizTalk RFID service does not conform to the schema due to {0}. Verify that the data ...
  32. The configuration information for the running service could not be retrieved from the database. Please check the installation. ...
  33. The connection ID for device {0} is not valid. The connection may have been closed. Open the connection again to attempt ...
  34. The Continuation {0} does not have a matching ContinuationID. The activity will not complete if there is no corresponding ...
  35. The ContinuationID {0} does not have a matching Continuation. The activity will not complete if there is no corresponding ...
  36. The control 3 on dialog 2 can accept property values that are at most 5 characters long. The value 4 exceeds this limit, ...
  37. 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 ...
  38. The control 3 on dialog 2 received a browse event, but there is no configurable directory for the present selection. Likely ...
  39. The correct version of Microsoft Windows SharePoint Services was not detected on your computer. Install Microsoft Windows ...
  40. The current action cannot be completed because the server is not configured for alerting. Ask your System Administrator to ...
  41. The current definition being parsed is {0}. The stream offset where the error occured is {1}. The line number where the error ...
  42. The current threshold for the memory usage of current process (MB). The threshold may be dynamically adjusted depending on ...
  43. The custom envelope generator could not locate the XML node for the custom envelope "%1" with the property "%2". This document ...
  44. The data contains a field value ("%1") that does not meet the minimum length requirement for tag "%2". The minimum length ...
  45. The data type is not compatible with the contents of the element. A date/time value may have a custom format that needs to ...
  46. The database "{0}" on the server "{1}" is partially compatible with the version of the product installed on this computer. ...
  47. The database "{0}:{1}" associated with the deployment driver does not match the database "{2}:{3}" specified during product ...
  48. The database %1 on server %2 is not compatible with the current version of BizTalk. Please specify a different database name ...
  49. The database %1 on server %2 is not compatible with the version of Microsoft BizTalk Server you are trying to configure. ...
  50. The database operation failed because it was using a distributed transaction which was cancelled by the transaction manager. ...
  51. The database schema version is incompatible with the expected version. Current schema version in the database: {0}. Expecting ...
  52. The database server you specified already contains BizTalk databases. To perform a basic configuration, you have to provide ...
  53. The database server you specified cannot be reached. Make sure you have specified the correct server name and that the server ...
  54. The database server {0} you specified cannot be reached. Make sure you have specified the correct server name and that the ...
  55. The database {1} already exists on server {0} and is not a compatible BizTalk database. Please specify a different database ...
  56. The database {1} on server {0} is not compatible with the version of Microsoft BizTalk Server you are trying to configure. ...
  57. The database {3} on server {2} has the incorrect SQL Server Sink schema code version {0}. The expected version is {1}. Delete ...
  58. The database {3} on server {2} has the incorrect SQL Server Sink schema version {0}. The expected version is {1}. Delete ...
  59. The Date or Time value received for Field: {0} is incorrect. Make sure the date time value is valid and generated record ...
  60. The decimal value of the initial part of the service class GUID that this performance counter instance corresponds to. A ...
  61. The decoder could not verify the validity of the message because the required signer certificate was not found in the "Local ...
  62. The dedicated command execution timed out after {0} milliseconds. The provider might still be processing the command. Retry ...
  63. The default application name has been provided for you. You can change the name or accept the name given. It is recommended ...
  64. The default property schema has been changed in another document. Please save or discard changes before using the 'Quick ...
  65. The default Web access mode for this project is set to file share, but the project folder at '%1' cannot be opened with the ...
  66. The default Web access mode for this project is set to FrontPage, but the project folder at '%1' cannot be opened with FrontPage. ...
  67. The deployed schema is attempting to promote a message element into the property "{0}" (msgType="{1}"). This property is ...
  68. The designated site has already been configured a notification service. A second notification service is not allowed. To ...
  69. The destination file contains invalid data and cannot be appended to. Please select a new destination file or correct the ...
  70. The destination identifier's "%1" qualifier is too long for the output header. Please update the port with a shorter qualifier. ...
  71. The destination identifier's "%1" value is too long for the output header. Please update the port with a shorter identifier. ...
  72. The destination node "{0}" has multiple inputs. For a destination node to have multiple inputs, one of its ancestors should ...
  73. The destination node "{0}" has {1} logical functoid input(s). The maximum number of possible logical functoid inputs to this ...
  74. The destination node "{0}" is linked to by two source nodes ("{1}" and "{2}") that are from different but conflicting Equivalent ...
  75. The destination queue depth of all messagebox databases exceeds the threshold. If the host publishes to multiple queues, ...