BizTalk Server 2006 R2

  1. Important: If you plan on using pre-downloaded CAB files, please make sure you have the latest CAB files by referring to ...
  2. Imports all the processes in the XML file into the store. The XML file should have been created by a previous call to ExportProcesses ...
  3. Imports BizTalk 2004 Cross-Referencing Data From Files. Usage: {0}: -file= For data file format information, see the online ...
  4. Imports BizTalk assembly binding information to BizTalk Configuration database. IMPORT SERVER=server DATABASE=database BINDING="pathname" ...
  5. In event handler {0}, the output of method {1}, whose type is {2}, matches input types of more than one method in the next ...
  6. In order to add this reference, the directory '%1' will be added to the project's ReferencePath property. This will change ...
  7. In order to start this orchestration, you must first enlist or start the following send port(s) / send port group(s): Send ...
  8. In the "%1" document under element "%2", the referenced specification contains "any" element. This type of element is not ...
  9. In the "%1" document under element "%2", the specification referenced contains empty particle(s). Empty particles are not ...
  10. In the BAM configuration XML, all of the Star Schema and Analysis server and database names must appear, or none can appear. ...
  11. In the BAM configuration XML, both the archive database name and the server name must appear, or neither can appear. You ...
  12. InboundTransportLocation" contains the URI of the receive location on which message has been received. This property is set ...
  13. InboundTransportLocation" contains the URI of the receive location on which message has been received. This property is set ...
  14. InboundTransportType" specifies the type of the adapter that had received this message. This property is set by BizTalk Server ...
  15. InboundTransportType" specifies the type of the adapter that had received this message. This property is set by BizTalk Server ...
  16. Incompatible version of BiztalkRuleEngineDb database already present (Expected version 3.3). Do you want to overwrite BiztalkRuleEngineDb ...
  17. Incompatible version of RFID database already present (Expected version 2). Do you want to overwrite RFID database with the ...
  18. Indicates how the underlying complex type of the record is derived from its 'Base Data Type' (Takes one of the values 'Extension' ...
  19. Indicates if the links stored in the map file do not contain any references to namespaces used in the schema. If this property ...
  20. Indicates if this atomic transaction should be processed in a batch. May improve performance with the possibility of losing ...
  21. Indicates that this orchestration should be notified with the DeliveryFailureException if transmission of a message fails ...
  22. Indicates the 1-based index into MIME part list. The MIME part at this index in the list will become the body part of BizTalk ...
  23. Indicates the content type of the MIME part. MIME part with this content type will become the body part of BizTalk message ...
  24. Indicates the content type of the MIME part. MIME part with this content type will become the body part of BizTalk message. ...
  25. Indicates the error message string that is associated with an orchestration that reaches this state. This message will appear ...
  26. Indicates the filter criteria applied to the properties of incoming messages. Only messages that fulfill this criteria are ...
  27. Indicates the transaction whose compensation process will be invoked. If the current transaction is specified then the default ...
  28. Indicates the version of the format/syntax of the instance data where relevant (e.g. 004010 of X12, D97B of EDIFACT, etc.) ...
  29. Indicates whether properties that are non-persistent should be applied to the device whenever the server connects to the ...
  30. Indicates whether the delivery receipt request for the BizTalk Framework document should be generated. This is used to enable ...
  31. Indicates whether this orchestration is instantiated upon receipt of a message (True) or invoked by another schedule (False). ...
  32. Information about message parts cannot be loaded. This usually happens when user doesn't have privileges to view message ...
  33. Information: this schema is neither a Base EDI nor a HIPAA schema and therefore does not have to be validated - no further ...
  34. Input instance file name is not specified for schema {0}. The instance file name can be provided in the file properties of ...
  35. Insert the correct media or browse the correct network path to a folder containing the installation package %1, and then ...
  36. Install either the BizTalk Server 2004 Engine component or the Message Queuing (also known as MSMQ) messaging system to continue. ...
  37. Insufficient permissions to perform the requested operation on device entity {0}. The principal that is performing the operation ...
  38. Insufficient permissions to start application. If your application contains unenlisted ports or orchestrations and you are ...
  39. Insufficient permissions to stop application. If you are not a BizTalk Administrator, you cannot unenlist ports and orchestrations. ...
  40. Insufficient resources to perform the requested operation. There are not enough resources to transmit a message of the specified ...
  41. InterchangeID" property contains a unique identifier that is common to all the messages that originated from same interchange ...
  42. InterchangeID" property contains a unique identifier that is common to all the messages that originated from same interchange ...
  43. InterchangeSequenceNumber" property contains the sequence number of the message within the interchange. This property is ...
  44. InterchangeSequenceNumber" property contains the sequence number of the message within the interchange. This property is ...
  45. Intermediate build of the BizTalk project containing schemas failed. Stopping further import. This usually indicates a problem ...
  46. Invalid adapter configuration is detected from the registry. The Constraints property value of the adapter must not be zero. ...
  47. Invalid array element type {0}. Expected array element type is {1}. Validations are done per element level for an array type. ...
  48. Invalid call of service {1} from atomic scope of service {0}. Services called from atomic scopes must not be transactional, ...
  49. Invalid Configuration. Either SSO Server is not set or there are no servers available in Configuration DB. Please provide ...
  50. Invalid Configuration. Unable to access SSO Configuration Store Object. Please check Component services and make sure SSOConfigStore ...
  51. Invalid host. Specify host[:port where host is the name of the server hosting the web directory and port is the optional ...
  52. Invalid invocation of a compensation handler which has out parameters. The requested scope '{0}' did not complete successfully. ...
  53. Invalid levels were specified for progress dimension {0} for alert {1}. The values must be either all empty or all non-empty. ...
  54. Invalid msgBoxServer and/or msgBoxName input parameters in UpdateCacheCounters fn for host {0}: MsgBoxServer {1}, MsgBox ...
  55. Invalid or disallowed IP address range. Starting and ending IP addresses can differ only in the last two hexadecimal digits ...
  56. Invalid parameter combination; specify parameter ASSEMBLY="pathname" or parameters NAME="assembly-name", VERSION="assembly-version", ...
  57. Invalid parameter combination; specify parameter ASSEMBLY="pathname" or parameters NAME="assembly-name", VERSION="assembly-version", ...
  58. Invalid path syntax.Use one of the following : MachineName\Private$\QueueName\Journal$ - for reading journal messages of ...
  59. Invalid path syntax.Use one of the following : MachineName\QueueName\Journal$ - for reading journal messages of a public ...
  60. Invalid SOAP action. A valid action is one of the following: 1. A single action: http://www.northwindtraders.com/Service/Operation ...
  61. Invalid type name. The root node type name has to be a valid C# identifier. It cannot be same as the type name of any other ...
  62. Invalid values were specified for time dimension {0} for alert {1}. The values must be either all empty or all non-empty. ...
  63. is a message predicate. This is added to the message by the BizTalk engine to restrict message routing to only those hosts ...
  64. is a promoted property. Promoted properties are used for message routing during subscription evaluation process. A message ...
  65. is a promoted property. Promoted properties are used for message routing during subscription evaluation process. A message ...
  66. is dependent on the following application(s). {1} For correct operation, you must ensure that the above applications are ...
  67. is not a promoted property. Such properties can be used for tracking and can be referenced by components (e.g. from Orchestration), ...
  68. is not a promoted property. Such properties can be used for tracking and can be referenced by components (e.g. from Orchestration), ...
  69. is not a valid identifier. Restoring original name. (A valid identifier consists of a letter followed by zero or more letters ...
  70. is not a valid identifier. Restoring original name. (A valid identifier consists of a letter followed by zero or more letters ...
  71. is not a valid installation package for this product because its product code is %2 which differs from the currently installed ...
  72. is not a valid installation package for this product because its version is %2 which differs from the currently installed ...
  73. is not a valid logical device name. The specified name is null, or empty, or exceeds 100 characters, or contains a character ...
  74. is not a valid name for an RFID process component. The specified name is null, or empty, or exceeds 100 characters, or contains ...
  75. is not a valid sub-site of '{1}'. Specify a different BAS SharePoint site URL or specify a URL that is only 1 level deep ...