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