BizTalk Server 2010

  1. The MIME encoder failed to sign the message because the certificate has private key protection turned on or the private key ...
  2. The MSMQ adapter does not support receiving messages non-transactionally. Check the transaction property that you have specified. ...
  3. The MSMQ adapter is unable to process messages at the send port %1. Reason: %2 Correct the error and restart the Biztalk ...
  4. The MSMQ adapter is unable to process messages from receive location %1. Correct the error in the event log and restart this ...
  5. The MSMQT subservice encountered an error executing initialization of the networking component. The binding IP address may ...
  6. The name %1 cannot be used Active Directory and DNS registration. The name must fit Windows requirements and cannot be the ...
  7. The name of one or more sources specified in the property XML does not match the names of the sources on the device. Make ...
  8. The name of the database into which the sink schema will be installed. The database will be created if it does not exist. ...
  9. The name of the project's primary output file (also known as the BizTalk assembly). This property reflects the current value ...
  10. The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to ...
  11. The name you entered exceeds the maximum number of characters allowed. Type a new name, using fewer characters, and try again. ...
  12. The names of the sources for the device could not be retrieved. To view the last known properties of the device, or to modify ...
  13. The namespace of the property schema with location "{0}" has changed since the last time it was added into this schema. Change ...
  14. The namespace of the schema you are trying to add clashes with one of the namespaces already declared. Please choose another ...
  15. The network clients for the Distributed Transaction Coordinator (DTC) Network must have the remote clients/transactions option ...
  16. The node name you typed contains characters which are not valid for XML Schema. Click the 'OK' button to encode the name ...
  17. The number of bits in the encoded byte array is not equal to 96. Only 96-bit encodings are currently supported. Specify a ...
  18. The number of characters specified ({0}) in the Government Managed Identifier is larger than the maximum allowed. Specify ...
  19. The number of commands in this batch of commands {0} if combined with the number of existing commands being processed would ...
  20. The number of inputs to the scripting functoid does not match with the number of inputs expected by the xsl:call-template. ...
  21. The number of levels of slicer dimension '{0}' for alert '{1}' must be less than or equal to the maximum number of levels ...
  22. The number of sources specified in the XML does not match the number of sources on the device. Make sure that the number ...
  23. The operation cannot be completed at this time because the the process manager is still starting up. Retry the operation ...
  24. The operation cannot be performed at this point of time as the fixed timer queue {0} is stopping. Retry the operation later. ...
  25. The operation could not be completed because the connection information for device {0} is not in a valid state. This can ...
  26. The operation could not be completed because the device {0} is currently disabled. This can happen if a device maintenance ...
  27. The operation of transferring ownership of this entity is failed with the following error. Click Back to select a different ...
  28. The orchestration cannot be found. It may have been deleted or renamed. The call orchestration's configuration will be lost. ...
  29. The orchestration cannot be found. It may have been deleted or renamed. The start orchestration's configuration will be lost. ...
  30. The orchestration cannot be started because it is dependent (uses Call or Start) on other orchestrations that have not been ...
  31. The orchestration cannot be stopped because there are other orchestrations which depend on it (using Call or Start) that ...
  32. The Orchestration Debugger timed out waiting for a response from the orchestration runtime. This may occur if the orchestration ...
  33. The orchestrations in assembly "{0}" are compatible with previously deployed assembly versions. The names and count of orchestrations, ...
  34. The orchestrations listed are included in the assemblies available to this application. You must specify a host that will ...
  35. The ordered delivery send port %1 has stopped processing messages due to an unknown error. This can usually happen if there ...
  36. The ordered delivery send port: "%1" has stopped processing messages. The failed message with MessageID: "%3" has been successfully ...
  37. The ordered delivery send port: "%1" has stopped processing messages. To rectify the issue please use Biztalk Management ...
  38. The original request has timed out. The response arrived after the timeout interval and it cannot be delivered to the client. ...
  39. The output message of the receive pipeline "%1" failed routing because there is no subscribing orchestration or send port. ...
  40. The parser cannot match the current data position with the specification. Verify the specification version is consistent ...
  41. The parser cannot parse the ISA section of the X12 document. This segment has a fixed-width requirement; if fields are not ...
  42. The parser cannot use document "%1" because it does not have a specification. Please attach a specification or specify a ...
  43. The parser components do not recognize the data. This might be caused by an interchange specification that is missing or ...
  44. The parser could not find the BizTalk Framework tag "%1", or the tag did not have a value. Therefore, this document will ...
  45. The parser did not read the data. Verify the code page is set correctly for the data. If the data is UNICODE, verify no byte ...
  46. The Partner edition does not support remote database connections. You must specify the local computer name for the server ...
  47. The path for the Application Server service executable retrieved from the installation package is null. Please repair the ...
  48. The pipeline cannot be located in the configuration database. Please deploy the pipeline's assembly to the configuration ...
  49. The pipeline component %1 can not be found. If the component name is fully qualified, this error may occur because the pipeline ...
  50. The Policy you specified will be deployed to the Rules Engine database using the parameters shown below. Click Next to begin ...
  51. The Policy you specified will be deployed using the parameters shown below. Click Next to begin or click Back to make changes. ...
  52. The Policy you specified will be undeployed using the parameters shown below. Click Next to begin undeployment or click Back ...
  53. The Policy/Vocabulary you specified will be exported using the parameters shown below. Click Next to begin export or click ...
  54. The Policy/Vocabulary you specified will be imported using the parameters shown below. Click Next to begin import or click ...
  55. The POP3 adapter could not authenticate on the server using supplied credentials. Please check the authentication scheme ...
  56. The POP3 adapter could not delete the message from the POP3 server. This may happen if the POP3 server times out an idle ...
  57. The POP3 adapter could not download a message or could not obtain the message count from the POP3 server. URL: %1 Error: ...
  58. The POP3 adapter could not establish a connection with the POP3 server. This could be due to the following reasons: 1) The ...
  59. The POP3 adapter could not establish a secure session with the server. This could be due to the following reasons: 1) The ...
  60. The POP3 server does not support the specified authentication scheme. Please change the scheme to the one supported by POP3 ...
  61. The Portal Components are a set of services used by business people to communicate, collaborate, and reach decisions enabling ...
  62. The process %1 was deleted, but an error was encountered while attempting to delete certain resources used by the process ...
  63. The process %3 has already been automatically restarted %1 times in the last %2 minutes. It will not be restarted now. Identify ...
  64. The process has two components with the name {0}, but they do not refer to the same class. They differ either in the assembly ...
  65. The process was saved successfully. However, there was an error validating the process and its bindings. To resolve, click ...
  66. The process {0} cannot be paused to event-collecting mode because the tag-processing reliability mode of the process is Express ...
  67. The process {0} has a component that is not reachable. None of its event handler methods will ever get called. There is no ...
  68. The process {0} has a logical source that has logical devices but no components. Logical devices are: {1}. Specify at least ...
  69. The process {0} has a logical source that has logical devices. However, the first event handler has no methods that take ...
  70. The process {0} has a logical source that has no logical devices, no components, and no child logical sources. Remove this ...
  71. The process-related operation could not be completed at this point because the Microsoft BizTalk RFID service is shutting ...
  72. The processes you are trying to import already exist and are started. These processes will be stopped before importing. Do ...
  73. The product cannot be installed on this machine since it seems to be a domain controller. This product can only be installed ...
  74. The project '%1' does not have any configured outputs. Make sure the project settings are configured to produce some output ...
  75. The project '%1' is a FrontPage Web under source control. This version of Visual Studio .NET does not support source controlled ...