BizTalk Server 2006 R2
- ReceivedFileName" contains the path and name of the file from where the message was read. This property is set by FILE adapter ...
- ReceivedFileName" contains the path and name of the file from where the message was read. This property is set by FILE adapter ...
- ReceiveFunction {0} depends on missing channel {1} to perform. Please clear this receive function or add related port or ...
- ReceivePortName" contains the name of the receive port on which message had arrived. This property is set by BizTalk Server ...
- ReceivePortName" contains the name of the receive port on which message had arrived. This property is set by BizTalk Server ...
- Record "{0}" - If preserve_delimiter_for_empty_data is false and suppress_trailing_delimiter is true or preserve_delimiter_for_empty_data ...
- Record "{0}" - If preserve_delimiter_for_empty_data is true and suppress_trailing_delimiter is true, the serialized data ...
- Record "{0}" - If the case schema property is set to upper or lower and the positional record tag is not the same case, the ...
- Record "{0}" - The Default Child Delimiter property on the schema node must be set when the Child Delimiter Type property ...
- Record "{0}" - The value of the Source Tag Identifier property is a duplicate value. Different records at same level cannot ...
- Record "{0}" - Trigger Value has a duplicate value. Different records at same level that have same Tag Identifier value should ...
- Record {0} has child elements. The Wizard will generate a new definition for the record and delete all current child elements. ...
- Recoverable interchange processing does not allow a trailer spec to be used if the document spec does not contain root level ...
- Recoverable interchange processing requires one of the following conditions: The trailer spec %1 must have a tag for the ...
- Recoverable interchange processing requires the document spec to have a tag for the root record or all children of the root ...
- Recoverable interchange processing requires the trailer spec to have a tag for the root record or all children of the root ...
- Redundant search criterion may have been specified. Review the query and try rerunning it after removing one or more search ...
- Referenced assembly "{0}" could not be located on local machine's filesystem, so it's impossible to determine if its deployment ...
- Referenced assembly resource (Luid:"{0}") could not be retrieved from the database (Server:"{1}", Database:"{2}"). If it ...
- Refers to a dynamic port through which the Orchestration sends documents to an external entity. Specify a Dynamic Send Port. ...
- Refers to a static port through which the Orchestration sends documents to an external entity. Specify a Static Send Port ...
- Registers all the event handlers in an assembly, ignoring those that are already registered. Specify the file name using ...
- Registers the specified provider. The CLR type name is an optional argument and can be omitted if the provider DLL contains ...
- Rejects all BtsCatalogExplorer object changes to the database since the last time SaveChanges or SaveChangesWithTransaction ...
- Remember that before you import this application, you need to have the following applications present in the destination ...
- Removal of the assembly failed. Make sure that all items in the assembly you are trying to remove fulfill the following conditions: ...
- Remove the extra End shape(s) and use Join shapes to structure the Orchestration such that all branches terminate at a single ...
- Remove the mapping for the BizTalk server from the host even if you cannot uninstall this instance of the BizTalk host from ...
- Remove"{1}"assembly "{0}", version="{2}.{3}.{4}.{5}" first, it references assembly "{6}", version="{7}.{8}.{9}.{10}" artifact ...
- Removes a particular application identifier for the specified object type, application instance, and application identifier. ...
- Removes all artifacts from the BAM definition XML. The file can be a text file containing the BAM definition XML or a BAM ...
- Removes BizTalk assembly from BizTalk Configuration database. REMOVE SERVER=server DATABASE=database (ASSEMBLY="pathname" ...
- Removes one view. It is an error if a view has dependent alerts. {5} must be called for these alerts before removing the ...
- Removes user or group from a view role. Note that removing an account from a view removes that account and all of its members ...
- Removing inbound bindings (if any are present) from send ports, receive locations, and receive ports to send and receive ...
- Removing outbound bindings (if any are present) from orchestration ports to send ports, send port groups, and receive ports. ...
- Removing these artifacts will remove the assemblies they were deployed from, and all other artifacts also deployed from those ...
- Removing this artifact will undeploy the assembly '{0}', and all artifacts deployed from that assembly: {1} Are you sure ...
- Removing tracking profiles associated with the BizTalk Management Database {1} on server {0} and the BAM Primary Import Table ...
- Renaming namespace {0}' to {1}' would cause name collisions for the following objects: {2}. Fix up the potential collisions ...
- Repair failed because multiple receive locations exist that use the reserved name "Sts.Outbox" and the reserved address '{0}'. ...
- Represents a business role such as shipper or supplier, and consists of a set of port types. This adds newer functionality ...
- Represents a combination of a specific address at which the inbound messages arrive and the pipeline that processes the message. ...
- Represents a combination of a specific address at which the inbound messages arrive and the pipeline that processes the message. ...
- Represents a combination of a specific address, pipeline, and other properites to which the outbound messages are sent. This ...
- Represents the logical end point through which partners interact with the business process for sending messages. This adds ...
- Represents the logical end point through which the business process interacts with the outside world by sending messages. ...
- Represents the logical end point through which the business process interacts with the outside world by sending messages. ...
- Represents the root object of the hierarchical BizTalk Explorer object model. This adds additional functionality on top of ...
- Request-Response) Refers to a port through which the Orchestration receives data from an external entity. Specify a Request-Response ...
- Required processing instruction "ms-tpmIsNew" is missing from the document. You will not be able to submit this document ...
- Resource (-Type="{0}" -Luid="{1}") already in store. 1) Use BTSTask's overwrite flag or 2) Set redeploy flag to true in BizTalk ...
- Resource (-Type="{0}" -Luid="{1}") is already in store and is either associated with another application or with another ...
- Results cannot be displayed because there are one or more error(s) in the query. Correct the query and click "Execute Query". ...
- Resume request for the selected service instance(s) has been submitted successfully. Please refresh the query page to see ...
- Retrieves all artifacts on the current database as XML and saves them in a file. The command will not overwrite existing ...
- Retrieves the BAM configuration XML and saves it in a file. The command will not overwrite existing files. - EXAMPLES - {5} ...
- Returns list of all activities for which interception is enabled and the event sources for each activity. - EXAMPLES - {4} ...
- Returns the collection of Applications that are referenced by this Application. This collection only the goes one level deep, ...
- Returns the SendPipeline associated with this ReceiveLocation. Starting with Microsoft BizTalk Server 2006, SendPipelines ...
- Returns the value of the second parameter if the value of the first parameter is true, and flattens the source document hierarchy. ...
- RFID Manager does not support adding a new provider on a remote server. Use the RFID Manager on the server computer to perform ...
- RFID Manager does not support registering a component on a remote server. Use RFID Manager on the server computer to perform ...
- RFID Server can be configured to eliminate same tags, if received within a time interval. It can also be configured to store ...
- RFID Tray is unable to connect to the server, since the dependent WMI service is disabled or not running. Please start the ...
- Rules Engine database is not configured. Please run the BizTalk Configuration Wizard and configure the Rules Engine portion. ...
- Rules policy "{0}" version {1} cannot be deleted from rules store since is already in production. Removing the policy from ...
- s!': %2!s! %3!s! %4!s! may not compensate a %5!s! whose compensation block contains any transactional or synchronized scopes ...
- s!': '%2!s!' may have already been compensated - repeated attempts to compensate the same scope will be ignored at runtime ...
- s!': a direct or indirect reference to a type defined in a non-exportable module '%2!s!' is not permitted under BPEL4WS compliance ...
- s!': a request-response operation round-trip may not appear in multiple tasks unless wrapped in a synchronized or atomic ...
- s!': a sequential convoy which is initialized by an activate receive may not call or compensate a service with a receive ...
- s!': all messages and message parts referred to in the 'in' (resp. 'out') parameters of a transform statement, must be unique ...
- s!': an atomic scope may not call a service that contains a receive with a correlation filtration initialized in the calling ...
- s!': An XLANG/s defined exception '%2!s!' that maps to a standard BPEL fault can not have an identifier under BPEL4WS compliance ...