BizTalk Server 2006 R2

  1. The adapter failed to transmit message going to send port "%1" with URL "%2". It will be retransmitted after the retry interval ...
  2. The administrator requested an instance operation that could not be performed because the instance is locked by another process. ...
  3. The Advanced option allows you to select an existing Correlation Type for the Correlation Set you are configuring. A Correlation ...
  4. The agreement '{0}' is either not found on BAS site or it is an inherited agreement. Adding inherited agreement to an application ...
  5. The amount of required disk space exceeds the amount of available disk space. The highlighted items indicate the drives with ...
  6. The annotation information for version {0}, track point {1} does not exist. Try re-deploying via Tracking Profile Editor. ...
  7. The answer returned by the TPM Management Web Service could not be understood. Contact your administrator for more information. ...
  8. The application base for provider {0} could not be deleted because of {1}. Try removing this directory manually after unregistering. ...
  9. The application domain for the process engine is being unloaded without the process being stopped. Process name: {0}, sender: ...
  10. The application identity will be set to the following account. Components in the application will run under this account. ...
  11. The application name in the bindings file and group do not match. Do you want to import the bindings into this application? ...
  12. The application name specified in the binding file ({0}) does not match the name of the application ({1}) into which the ...
  13. The application root {0} is either not a directory or the service has insufficient permissions to access it. Verify if the ...
  14. The application specified in the bindings file does not exist. Please create the application first and then import bindings. ...
  15. The application was successfully imported to the group . Note that this application depends on the following applications ...
  16. The application {0} was successfully exported to the file {1}. To deploy this application to another environment, you must ...
  17. The AS2 Decoder encountered an exception during processing. Details of the message and exception are as follows: AS2-From:"{0}" ...
  18. The AS2 Decoder encountered an exception during processing. Details of the message and exception are as follows: AS2-From:"{0}" ...
  19. The AS2 Decoder failed processing when validating the MIC value returned in the MDN. Details of the MDN message are as follows: ...
  20. The AS2 Decoder failed processing when validating the MIC value returned in the MDN. Details of the MDN message are as follows: ...
  21. The AS2 Decoder failure processing because the MDN indicated the AS2 message failed processing. Details of the MDN message ...
  22. The AS2 Decoder failure processing because the MDN indicated the AS2 message failed processing. Details of the MDN message ...
  23. The AS2 Decoder failure processing because the MDN signing did not match our request. Details of the MDN message are as follows: ...
  24. The AS2 Decoder failure processing because the MDN signing did not match our request. Details of the MDN message are as follows: ...
  25. The AS2 Decoder was unable to locate the Disposition-Notification-Options HTTP header which is required for MDN generation. ...
  26. The assembly does not contain any web service proxy types. Assembly should contain at least one public type derived from ...
  27. The assembly name {0} could not be parsed. Reason: {1}. For details on resolving the issue, refer to the AssemblyName class ...
  28. The attempt to connect to device %1 failed continuously %2 time(s). The error message for the last failure is: %3. This device ...
  29. The attempt to initialize the SQL Server Sink event handler from the specified parameter list failed. Verify if the event ...
  30. The authentication information for the worker process account was not found in the RFID store. Try repairing your installation ...
  31. The BAM activity name, {0}, contains invalid characters or whitespace. User defined names may not begin with a space or a ...
  32. The BAM DB Connection dialog cannot be launched because the workbook is read-only. Please use Save-As to save a writable ...
  33. The BAM definition XML file could not be generated. At least one milestone or business data item must be specified to generate ...
  34. The BAM definition XML file could not be generated. Verify that your milestone names, business data item names, and activity ...
  35. The Bam Definition Xml has successfully been imported. You may now use the items in the BAM menu to edit the activities and ...
  36. The BAM Interceptor detected the following error : In host process '{0}', connection string to BAM Primary Import Database ...
  37. The BAM Interceptor detected the following error : In host process '{0}', for EventSource '{1}' OnEvent '{2}' BAM activity ...
  38. The BAM Interceptor detected the following error : In host process '{0}', for EventSource '{1}' OnEvent '{2}' BAM activity ...
  39. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  40. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  41. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  42. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  43. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  44. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  45. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for technology '{1}' ...
  46. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for technology '{1}' ...
  47. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration polling interval '{1}' ...
  48. The BAM Interceptor detected the following error : In host process '{0}', invalid interceptor setting '{1}' found in application ...
  49. The BAM Interceptor detected the following error : In host process '{0}', invalid stack argument '{1}' for Boolean operation ...
  50. The BAM Interceptor detected the following error : In host process '{0}', new connection string '{1}' does not match previous ...
  51. The BAM Interceptor detected the following error : In host process '{0}', the connection is already enlisted in a distributed ...
  52. The BAM Interceptor detected the following error : In host process '{0}', the interceptor configuration for EventSource '{1}' ...
  53. The BAM Interceptor detected the following error : In host process '{0}', the interceptor configuration for EventSource '{1}' ...
  54. The BAM Interceptor detected the following error : In host process '{0}', unable to create additional BAM Interceptor performance ...
  55. The BAM Interceptor detected the following error : In host process '{0}', unable to find event source name for technology ...
  56. The BAM Interceptor detected the following error : In host process '{0}', unable to parse application configuration parameter ...
  57. The BAM Interceptor detected the following error : In host process '{0}', unable to parse data into BAM data type '{1}' during ...
  58. The BAM Interceptor detected the following error : In host process '{0}', unable to parse string '{1}' into BAM data type ...
  59. The BAM Interceptor detected the following warning : In host process '{0}', unable to create performance counters : {1} Please ...
  60. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', '{1}' configuration ...
  61. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', error evaluating ...
  62. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', error inspecting ...
  63. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', error inspecting ...
  64. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', interceptor ...
  65. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', invalid context ...
  66. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', invalid definition, ...
  67. The BAM Interceptor for Windows Communication Foundation detected the following error : In host process '{0}', invalid definition, ...
  68. The BAM Interceptor for Windows Communication Foundation detected the following error : interceptor configuration for EventSource ...
  69. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', BAM Tracking Service ...
  70. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', in the interceptor ...
  71. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', interceptor configuration ...
  72. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', interceptor configuration ...
  73. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', interceptor configuration ...
  74. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', interceptor configuration ...
  75. The BAM Interceptor for Windows Workflow Foundation detected the following error : In host process '{0}', interceptor configuration ...