BizTalk Server 2010

  1. Record "{0}" - The Default Child Delimiter property on the schema node must be set when the Child Delimiter Type property ...
  2. Record "{0}" - The value of the Source Tag Identifier property is a duplicate value. Different records at same level cannot ...
  3. Record "{0}" - Trigger Value has a duplicate value. Different records at same level that have same Tag Identifier value should ...
  4. Record {0} has child elements. The Wizard will generate a new definition for the record and delete all current child elements. ...
  5. Recoverable interchange processing does not allow a trailer spec to be used if the document spec does not contain root level ...
  6. Recoverable interchange processing requires one of the following conditions: The trailer spec %1 must have a tag for the ...
  7. Recoverable interchange processing requires the document spec to have a tag for the root record or all children of the root ...
  8. Recoverable interchange processing requires the trailer spec to have a tag for the root record or all children of the root ...
  9. Redundant search criterion may have been specified. Review the query and try rerunning it after removing one or more search ...
  10. Reference location of source schema. This will be '- Inline Schema -' if this is a multipart schema from Orchestration Designer. ...
  11. Reference location of target schema. This will be '- Inline Schema -' if this is a multipart schema from Orchestration Designer. ...
  12. Referenced assembly "{0}" could not be located on local machine's filesystem, so it's impossible to determine if its deployment ...
  13. Referenced assembly resource (Luid:"{0}") could not be retrieved from the database (Server:"{1}", Database:"{2}"). If it ...
  14. Refers to a dynamic port through which the Orchestration sends documents to an external entity. Specify a Dynamic Send Port. ...
  15. Refers to a static port through which the Orchestration sends documents to an external entity. Specify a Static Send Port ...
  16. Regenerate/update the dynamic views like completed instances and relationships views EXEC dbo].[bam_Metadata_RegenerateViews ...
  17. Register activity in RTA metadata table INSERT dbo].[bam_Metadata_RealTimeAggregations ( CubeName, RtaName, RTAWindow, Timeslice, ...
  18. Registers all the event handlers in an assembly, ignoring those that are already registered. Specify the file name using ...
  19. Registers the specified provider. The CLR type name is an optional argument and can be omitted if the provider DLL contains ...
  20. Rejects all BtsCatalogExplorer object changes to the database since the last time SaveChanges or SaveChangesWithTransaction ...
  21. Remember that before you import this application, you need to have the following applications present in the destination ...
  22. Removal of the assembly failed. Make sure that all items in the assembly you are trying to remove fulfill the following conditions: ...
  23. Removal of the MSMQT Adapter failed for the following reason: %1. For further information on how to remedy this situation, ...
  24. Remove the mapping for the BizTalk server from the host even if you cannot uninstall this instance of the BizTalk host from ...
  25. Remove"{1}"assembly "{0}", version="{2}.{3}.{4}.{5}" first, it references assembly "{6}", version="{7}.{8}.{9}.{10}" artifact ...
  26. Removes a particular application identifier for the specified object type, application instance, and application identifier. ...
  27. Removes all artifacts from the BAM definition XML. The file can be a text file containing the BAM definition XML or a BAM ...
  28. Removes one view. It is an error if a view has dependent alerts. {5} must be called for these alerts before removing the ...
  29. Removes user or group from a view role. Note that removing an account from a view removes that account and all of its members ...
  30. Removing inbound bindings (if any are present) from send ports, receive locations, and receive ports to send and receive ...
  31. Removing outbound bindings (if any are present) from orchestration ports to send ports, send port groups, and receive ports. ...
  32. Removing these artifacts will remove the assemblies they were deployed from, and all other artifacts also deployed from those ...
  33. Removing this artifact will undeploy the assembly '{0}', and all artifacts deployed from that assembly: {1} Are you sure ...
  34. Removing tracking profiles associated with the BizTalk Management Database {1} on server {0} and the BAM Primary Import Table ...
  35. Renaming namespace {0}' to {1}' would cause name collisions for the following objects: {2}. Fix up the potential collisions ...
  36. Represents a business role such as shipper or supplier, and consists of a set of port types. This adds newer functionality ...
  37. Represents a combination of a specific address at which the inbound messages arrive and the pipeline that processes the message. ...
  38. Represents a combination of a specific address at which the inbound messages arrive and the pipeline that processes the message. ...
  39. Represents a combination of a specific address, pipeline, and other properites to which the outbound messages are sent. This ...
  40. Represents the logical end point through which partners interact with the business process for sending messages. This adds ...
  41. Represents the logical end point through which the business process interacts with the outside world by sending messages. ...
  42. Represents the logical end point through which the business process interacts with the outside world by sending messages. ...
  43. Represents the root object of the hierarchical BizTalk Explorer object model. This adds additional functionality on top of ...
  44. Request-Response) Refers to a port through which the Orchestration receives data from an external entity. Specify a Request-Response ...
  45. Resource (-Type="{0}" -Luid="{1}") already in store. 1) Use BTSTask's overwrite flag or 2) Set redeploy flag to true in BizTalk ...
  46. Resource (-Type="{0}" -Luid="{1}") is already in store and is either associated with another application or with another ...
  47. Results cannot be displayed because there are one or more error(s) in the query. Correct the query and click "Execute Query". ...
  48. Resume request for the selected service instance(s) has been submitted successfully. Please refresh the query page to see ...
  49. Retrieves all artifacts on the current database as XML and saves them in a file. The command will not overwrite existing ...
  50. Retrieves the BAM configuration XML and saves it in a file. The command will not overwrite existing files. - EXAMPLES - {5} ...
  51. Returns list of all activities for which interception is enabled and the event sources for each activity. - EXAMPLES - {4} ...
  52. Returns the collection of Applications that are referenced by this Application. This collection only the goes one level deep, ...
  53. Returns the SendPipeline associated with this ReceiveLocation. Starting with Microsoft BizTalk Server 2006, SendPipelines ...
  54. Returns the value of the second parameter if the value of the first parameter is "true", and flattens the source document ...
  55. RFID Manager does not support adding a new provider on a remote server. Use the RFID Manager on the server computer to perform ...
  56. RFID Manager does not support registering a component on a remote server. Use RFID Manager on the server computer to perform ...
  57. RFID Manager is supported only under .NET 4.0 or later versions of .NET. To run RFID Manager under .NET 4.0, use the shortcut ...
  58. RFID Server can be configured to eliminate same tags, if received within a time interval. It can also be configured to store ...
  59. RFID Tray is unable to connect to the server, since the dependent WMI service is disabled or not running. Please start the ...
  60. Root KeyGenerator tModels must be signed by a valid X509 Certificate. To create one, upload a signed copy of the tModel. ...
  61. Rules Engine database is not configured. Please run the BizTalk Configuration Wizard and configure the Rules Engine portion. ...
  62. Rules policy "{0}" version {1} cannot be deleted from rules store since is already in production. Removing the policy from ...
  63. s is already assigned to the UDDI Services site on %s. Are you sure you want to re-assign %s to the UDDI Services site on ...
  64. s!': %2!s! %3!s! %4!s! may not compensate a %5!s! whose compensation block contains any transactional or synchronized scopes ...
  65. s!': '%2!s!' may have already been compensated - repeated attempts to compensate the same scope will be ignored at runtime ...
  66. s!': a direct or indirect reference to a type defined in a non-exportable module '%2!s!' is not permitted under BPEL4WS compliance ...
  67. s!': a request-response operation round-trip may not appear in multiple tasks unless wrapped in a synchronized or atomic ...
  68. s!': a sequential convoy which is initialized by an activate receive may not call or compensate a service with a receive ...
  69. s!': all messages and message parts referred to in the 'in' (resp. 'out') parameters of a transform statement, must be unique ...
  70. s!': an atomic scope may not call a service that contains a receive with a correlation filtration initialized in the calling ...
  71. s!': An XLANG/s defined exception '%2!s!' that maps to a standard BPEL fault can not have an identifier under BPEL4WS compliance ...
  72. s!': if shared data is updated in a parallel then all references in every task must be in a synchronized or atomic scope ...
  73. SaveBindingWithoutValidation cannot be called when a process is not in a stopped state. Process name: {0}. You need to stop ...
  74. Schema "{0}" and a previously deployed schema "{1}" have the same document type name "{2}". Document type names should be ...
  75. Schema "{0}" and a previously deployed schema "{1}" have the same target namespace "{2}". Target namespaces should be unique. ...