BizTalk Server 2010

  1. OutboundTransportType" specifies the type of the transport that will be used to send this message. This property is set by ...
  2. OutboundTransportType" specifies the type of the transport that will be used to send this message. This property is set by ...
  3. Overrides the current thread's CurrentUICulture property for all resource lookups using this strongly typed resource class. ...
  4. Parameter names are not case sensitive and may be abbreviated. Parameter values are case sensitive. PathName is required; ...
  5. Parameters have been specified for calling an orchestration, but the orchestration being called does not accept parameters. ...
  6. Parameters have been specified for starting an orchestration, but the orchestration being started does not accept parameters. ...
  7. Parameters passed to event handler {0} have the following extra parameters that are not defined in the metadata: {1}. Specify ...
  8. ParentActivityID) GO - 3. Migrate completed instance table - Add LastModified column IF EXISTS (SELECT i.name FROM sysobjects ...
  9. Parsing property indicating that a record is qualified by more than its tag identifier, specifically, by a subordinate piece ...
  10. Parsing property indicating that a subdocument break (currently only HIPAA parser) occurs at the node where this property ...
  11. Parsing property indicating that any envelope removed from the data is to be carried along with it as part of the message ...
  12. Parsing property indicating the value(s) in a trigger field which qualify the instance data for parsing into this schema ...
  13. Parties that existed prior to migration can not be deleted. If this is a new party, please make sure all artifacts are removed ...
  14. Party as receiver AS2 agreement can not be created for Party {0} because identity {1} seems to belong to both party {0} and ...
  15. Party as receiver AS2From and AS2To identities are belonging to the same partner. Please verify AS2From in party as receiver ...
  16. Party represents a trading partner, typically an enterprise organization, but can be used to represent businesses, business ...
  17. Party Send Port '{0}' has been referenced in Party '{1}' enlistment and hence cannot be removed. Resolve the Party enlistment ...
  18. Party(s) {0} enlisted under Role(s) is(are) used by this Orchestration. All the party send ports used in this binding must ...
  19. Party(s) {0} enlisted under role(s) {1} is(are) used by one or more started orchestrations. Please make sure that all the ...
  20. Party(s) {0} is(are) using this send port in binding under the role(s) {1} which is(are) used by one or more started orchestrations. ...
  21. Passed parameter {2} does not conform to its metadata {1} for event handler {0}. Specify a value that conforms to the metadata. ...
  22. Pathname to BizTalk assembly (*.dll) file. If this argument is supplied, you do not need to specify input for Name, Version, ...
  23. Performance Warning: marking %1!s! '%2!s!' as a longrunning transaction is not necessary and incurs the performance penalty ...
  24. Permission denied. BizTalk Administrator privileges and/or other database/SQL server privileges are required in order to ...
  25. Permission denied. Make sure that the current user is a BizTalk Administrator and a member of the SSO Affiliate Administrators ...
  26. Please enter the instance name for the component. Some components require to be configured correctly for the process to start. ...
  27. Please enter the name of your organization in the box below. This will be used as default company name for subsequent installations ...
  28. Please make sure that there no BAM Artifacts (Activities, Views, ActivityViews, Cubes or Rtas) with the same ID already deployed. ...
  29. Please supply a comma or semi-colon delimited list of namespace aliases definitions. Each definition should consist of an ...
  30. Plug-in type {0} has HatContextMenuPlugin attribute defined but {1} implementation(s) of the ICtxMenuPlugin interface found ...
  31. Port output value should be a byte array of length 1 with value of either 0 or 1. 0 indicates that the port will be set at ...
  32. Port types that have a combination of one-way and request-response operations are not allowed. Correct service description ...
  33. Port {0}, required for the Microsoft BizTalk RFID service to start, is already in use. Retry after changing the port number ...
  34. Port {0}, which is required by the Rule Engine Update Service, is being used by another application. Restart this computer ...
  35. Prepopulation is needed only if the actual data time range is not empty IF @MinTime IS NOT NULL AND @MaxTime IS NOT NULL ...
  36. Preview for a selected group of service instances shows up to {0} service instances. Use "Show Service Instances" context ...
  37. Preview for the selected query result ({0} items are displayed; To view more items, double-click on the query result above.) ...
  38. primaryImport WHERE primaryImport.ActivityID = @ActivityID - if the record was not found, then insert IF (@ROWCOUNT = 0) ...
  39. Principal %1 does not have sufficient privileges to perform the requested operation on device entity %2. The principal that ...
  40. Priority of the rule within the policy. The larger the number, the higher the rule priority. The default is 0 and represents ...
  41. Private key of the decryption certificate is not available. Please reinstall the certificate in "Current User\Personal" certificate ...
  42. Problem encountered while accessing one of the databases. This usually occurs when one of the databases is offline. Ensure ...
  43. Process has a logical source that has the same logical device appearing twice. Logical device name: {0}. Specify valid names ...
  44. Process {0} can be deployed or undeployed only when it is stopped. The current state is {1}. You need to stop the process ...
  45. Process {0} cannot be changed or deleted because it is currently running. You need to stop the process before attempting ...
  46. Process {0} cannot be deleted because it is either running or is in event-collection mode. You need to stop the process before ...
  47. Process {0} is busy. This operation cannot be performed at this time because another operation on this process (such as StartProcess, ...
  48. ProductName is not supported on Windows XP and Windows Server 2003. Refer to the Installation Guide for supported platforms. ...
  49. ProductName setup ended prematurely because of an error. Your system has not been modified. To install this program at a ...
  50. ProductName setup was interrupted. Your system has not been modified. To install this program at a later time, please run ...
  51. Project names cannot be empty strings nor can they contain only '.' or have any of the following characters: ; \ / ? : @ ...
  52. Properties Description: Target : Indicates if the property is a device-level or antenna-level property. Group : The standard ...
  53. Property schema "{0}" has a property identified by Guid "{1}", which is already used by some other property deployed into ...
  54. Property that controls all the namespaces used in this schema. Use this property to import, include, or redefine other schemas ...
  55. Provider %1 could not be loaded during service startup. Reason: %2. Resolve the issue that is causing the exception, and ...
  56. Provider %1 threw an exception. Try restarting the provider, or contact the provider vendor for further assistance. Exception: ...
  57. Provider %1 was unloaded during the delayed startup phase of the service. Resolve the issue that is causing the unload, and ...
  58. Provider could not listen on the specified port for incoming LLRP reader connections. See the inner exception for more details. ...
  59. Provider {0} cannot be unregistered at this point because it is in use by entities {1}. Remove the references to this provider, ...
  60. Provider {3} was not started because provider {0} has already been started with the same assembly name {1} and type name ...
  61. Provides an indication of which is the top level node for a structured message/business document schema. Default is 'None'. ...
  62. Public key token of the BizTalk assembly for which to export the binding file. If you specify inputs for Name, Version, Culture, ...
  63. Queries can be saved and reused. They can also be the basis for an alert (e.g. notify me any time a purchase order arrives ...
  64. Receive handler must remain default until some other receive handler becomes default. It is only possible to change default ...
  65. Receive handler not specified for receive location "{0}"; updating with first receive handler with matching transport type. ...
  66. Receive location "{0}" for metadata not found. (Check receive location mapping in Web.config and verify the receive location ...
  67. Receive Location '{0}' has no send pipeline. Specify a Send Pipeline for this Receive Location or its parent Receive Port. ...
  68. Receive Location name has to be unique in an Admin Group. Receive Location '{0}' is already present in the Admin Group '{1}'. ...
  69. ReceivedFileName" contains the path and name of the file from where the message was read. This property is set by FILE adapter ...
  70. ReceivedFileName" contains the path and name of the file from where the message was read. This property is set by FILE adapter ...
  71. ReceivePortName" contains the name of the receive port on which message had arrived. This property is set by BizTalk Server ...
  72. ReceivePortName" contains the name of the receive port on which message had arrived. This property is set by BizTalk Server ...
  73. Record "{0}" - If preserve_delimiter_for_empty_data is false and suppress_trailing_delimiter is true or preserve_delimiter_for_empty_data ...
  74. Record "{0}" - If preserve_delimiter_for_empty_data is true and suppress_trailing_delimiter is true, the serialized data ...
  75. Record "{0}" - If the case schema property is set to upper or lower and the positional record tag is not the same case, the ...