BizTalk Server 2006 R2

  1. The operation cannot be completed at this time because the the process manager is still starting up. Retry the operation ...
  2. The operation cannot be performed at this point of time as the fixed timer queue {0} is stopping. Retry the operation later. ...
  3. The operation could not be completed because the device {0} is currently disabled. This can happen if a device maintenance ...
  4. The orchestration cannot be found. It may have been deleted or renamed. The call orchestration's configuration will be lost. ...
  5. The orchestration cannot be found. It may have been deleted or renamed. The start orchestration's configuration will be lost. ...
  6. The orchestration cannot be started because it is dependent (uses Call or Start) on other orchestrations that have not been ...
  7. The orchestration cannot be stopped because there are other orchestrations which depend on it (using Call or Start) that ...
  8. The Orchestration Debugger timed out waiting for a response from the orchestration runtime. This may occur if the orchestration ...
  9. The Orchestration Designer for Business Analysts requires Automation Events be turned on. To turn on Automation Events: 1. ...
  10. The orchestrations in assembly "{0}" are compatible with previously deployed assembly versions. The names and count of orchestrations, ...
  11. The orchestrations listed are included in the assemblies available to this application. You must specify a host that will ...
  12. The ordered delivery send port %1 has stopped processing messages due to an unknown error. This can usually happen if there ...
  13. The ordered delivery send port: "%1" has stopped processing messages. The failed message with MessageID: "%3" has been successfully ...
  14. The ordered delivery send port: "%1" has stopped processing messages. To rectify the issue please use Biztalk Management ...
  15. The original request has timed out. The response arrived after the timeout interval and it cannot be delivered to the client. ...
  16. The output message of the receive pipeline "%1" failed routing because there is no subscribing orchestration or send port. ...
  17. The parameter '{0}' has invalid XML, if you have manually modified the agreement document, please revert your changes and ...
  18. The parser cannot match the current data position with the specification. Verify the specification version is consistent ...
  19. The parser cannot parse the ISA section of the X12 document. This segment has a fixed-width requirement; if fields are not ...
  20. The parser cannot use document "%1" because it does not have a specification. Please attach a specification or specify a ...
  21. The parser components do not recognize the data. This might be caused by an interchange specification that is missing or ...
  22. The parser could not find the BizTalk Framework tag "%1", or the tag did not have a value. Therefore, this document will ...
  23. 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 ...
  24. The Partner edition does not support remote database connections. You must specify the local computer name for the server ...
  25. The pipeline cannot be located in the configuration database. Please deploy the pipeline's assembly to the configuration ...
  26. The pipeline component %1 can not be found. If the component name is fully qualified, this error may occur because the pipeline ...
  27. The Policy you specified will be deployed to the Rules Engine database using the parameters shown below. Click Next to begin ...
  28. The Policy you specified will be deployed using the parameters shown below. Click Next to begin or click Back to make changes. ...
  29. The Policy you specified will be undeployed using the parameters shown below. Click Next to begin undeployment or click Back ...
  30. The Policy/Vocabulary you specified will be exported using the parameters shown below. Click Next to begin export or click ...
  31. The Policy/Vocabulary you specified will be imported using the parameters shown below. Click Next to begin import or click ...
  32. The POP3 adapter could not authenticate on the server using supplied credentials. Please check the authentication scheme ...
  33. The POP3 adapter could not delete the message from the POP3 server. This may happen if the POP3 server times out an idle ...
  34. The POP3 adapter could not download a message or could not obtain the message count from the POP3 server. URL: %1 Error: ...
  35. The POP3 adapter could not establish a connection with the POP3 server. This could be due to the following reasons: 1) The ...
  36. The POP3 adapter could not establish a secure session with the server. This could be due to the following reasons: 1) The ...
  37. The POP3 server does not support the specified authentication scheme. Please change the scheme to the one supported by POP3 ...
  38. The Portal Components are a set of services used by business people to communicate, collaborate, and reach decisions enabling ...
  39. The process %1 was deleted, but an error was encountered while attempting to delete certain resources used by the process ...
  40. The process %3 has already been automatically restarted %1 times in the last %2 minutes. It will not be restarted now. Identify ...
  41. The process has two components with the name {0}, but they do not refer to the same class. They differ either in the assembly ...
  42. The process was saved successfully. However, there was an error validating the process and its bindings. To resolve, click ...
  43. The process {0} cannot be paused to event-collecting mode because the tag-processing reliability mode of the process is Express ...
  44. The process {0} has a component that is not reachable. None of its event handler methods will ever get called. There is no ...
  45. The process {0} has a logical source that has logical devices but no components. Logical devices are: {1}. Specify at least ...
  46. The process {0} has a logical source that has logical devices. However, the first event handler has no methods that take ...
  47. The process {0} has a logical source that has no logical devices, no components, and no child logical sources. Remove this ...
  48. The process-related operation could not be completed at this point because the Microsoft BizTalk RFID service is shutting ...
  49. The processes you are trying to import already exist and are started. These processes will be stopped before importing. Do ...
  50. The product cannot be installed on this machine since it seems to be a domain controller. The products can only be installed ...
  51. The profile '%0' contains multiple properties marked as the RDN Attribute for the data source '%1'. Exactly one RDN Attribute ...
  52. The profile '%0' uses an LDAPv3-compliant data-source, but no property is marked as the RDN-attribute. Exactly one RDN Attribute ...
  53. The profile-group '%0' cannot be deleted because it contains a property that is marked as a primary-key, a hashing-key, or ...
  54. The profile: %0 contains a property marked as encrypted and it either does not contain a profile level custom attribute to ...
  55. The project '%1' does not have any configured outputs. Make sure the project settings are configured to produce some output ...
  56. The project '%1' is a FrontPage Web under source control. This version of Visual Studio .NET does not support source controlled ...
  57. The project '%1' is on an untrusted web server. Opening this project may cause code to be executed with full trust. Do you ...
  58. The project '%1' is under source control. An error occurred registering this project with source control. It is recommended ...
  59. The project '%1' is under source control. This version of Visual Studio .NET does not support source controlled projects. ...
  60. The project '%1' was created with a newer version of Visual Studio, which is incompatible with your version. You can only ...
  61. The project '%1' was created with a newer version of Visual Studio. If you open it with this version of Visual Studio, some ...
  62. The project '%1' will be upgraded to run against version %2 of the .NET Framework the next time it is built. You can use ...
  63. The project already has a Web reference to the URL '%1'. Do you want to update this reference with the latest information ...
  64. The project location "{0}" is not empty. You need to do one of the following: 1. Choose a different location for the new ...
  65. The project location is not fully trusted by the .NET runtime. This is usually because it is either a network share or mapped ...
  66. The project location is not fully trusted by the .NET runtime. This is usually because it is either a network share or mapped ...
  67. The properties of the device could not be retrieved. To view the last known properties of the device, or to modify the connection ...
  68. The property '%0' cannot be marked as multi-valued. It references a data member from an OLEDB-ANSI source of type '%1'. Only ...
  69. The property profile for devices {0} could not be applied. This can happen if the devices were offline. For details, see ...
  70. The property set for the "%1" document either is missing or does not contain a valid value for the "%2" property. Please ...
  71. The property sheet field "From" or "Send notification to" is not configured for the BizTalk.SendSMTP transport component. ...
  72. The property values in the selected versions are identical. However, the two versions might differ in the device connectivity ...
  73. The property will contain a value that is a reference number for the code list. Refer to help on code lists to know more ...
  74. The property: %0 in profile: %1 is marked as encrypted but it is either not of the correct type, not mapped to the correct ...
  75. The property: %0 in profile: %1 is marked as exported and it is either a multivalued boolean, binary, image, password or ...