While trying to process document #%4 during submission "%1", the parser component named "%2" failed on the method "%3" with the error code "%5". Possible causes are: the component found unexpected data in the incoming stream; a document specification could not be found given the data; or an internal component failure occurred. If this problem continues, remove the "%2" component from the list of valid parser components or contact your system administrator.
When set to true, multiple interchanges would be detected. Otherwise, the entire message would be treated as a single interchange ...
When the host instances of this host are clustered, this property contains the cluster resource group name set by the Administrator. ...
When the send port is solicit-response, the Administration Queue should be specified, and the Acknowledgement Type should ...
While sending Edifact message to party with name {0}, no matching group could be found for transaction set with DocType {1} ...
While trying to process document #%4 during submission "%1", the parser component named "%2" failed on the method "%3" with ...
Windows account that will have permissions to access the data in the BAM Notification Services databases during Business ...
Windows account that will have permissions to access the data in the BAM Primary Import Database during Business Activity ...
Windows account with access to a specific In-Process BizTalk host instance. This account will be given Log on as Service ...
Windows account with access to a specific Isolated BizTalk host instance. This account will be given Log on as Service rights. ...