BizTalk Server 2010

  1. The FTPS server rejected the secure FTP connection. Make sure the FTPS server allows SSL and that the SSL is configured properly ...
  2. The given assembly ("{0}") is not strong named. A strong named assembly is required if any of the global assembly cache (gac) ...
  3. The given BizTalk assembly ("{0}") is not strong named. A strong named BizTalk assembly is required if any of the options ...
  4. The given index name is invalid. Valid index names must start with a letter or an underscore and can contain letters, numbers, ...
  5. The goal is to find the parent activity of the activity we are trying to update - this information is stored in the continuations ...
  6. The goal is to find the parent activity of the activity we are trying to update - this information is stored in the continuations ...
  7. The group receiver settings are not configured for agreement of batch {0}. This needs to be configured before batching can ...
  8. The header specification name must be specified when generating a header without using the functionality for preserving headers. ...
  9. The Health and Activity Tracking (HAT) tool provides features for reporting, analyzing, and debugging data and messages that ...
  10. The highlighted volumes (if any) do not have enough disk space available for the currently selected features. You can either ...
  11. The highlighted volumes do not have enough disk space available for the currently selected features. You can either remove ...
  12. The Host "%1" was clustered, but was not made dependant on a Network Name resource. This could be because of the following ...
  13. The host instance is in an inconsistent state for this BizTalk service. Therefore, the service will shutdown. Please delete ...
  14. The Host was clustered, but was not made dependant on a Network Name resource. This could be because no Network Name resources ...
  15. The HTTP port of the IIS Web site where the Windows SharePoint Services adapter Web service is installed. By default, this ...
  16. The HTTP response status code specified in the message context is outside the acceptable range of values. You must specify ...
  17. The identity {0} is moved to party {1}. Note that if there were any send ports that were used for sending a message to this ...
  18. The identity {0} is moved to party {1}. Note that if there were any send ports that were used for sending a message to this ...
  19. The InboundTransportLocation is disallowed. This could be because the receive location is disabled or its service window ...
  20. The information entered to connect to SQL Server is incomplete, SQL Server Authentication was selected, but the sql username ...
  21. The information in the .btm file is not in proper .btm format and cannot be opened in the BizTalk Mapper. The file might ...
  22. The information in the .ODX file is not in proper .ODX format and cannot be opened with the Orchestration Designer. The file ...
  23. The input XML file does not contain any device or source property information. Specify an XML file that contains the property ...
  24. The InstallDate property is a datetime value indicating when the object was installed. The lack of a value does not indicate ...
  25. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. ...
  26. The installer has insufficient privileges to access this directory: 2]. The installation cannot continue. If you are not ...
  27. The installer has insufficient privileges to access this directory: 2]. The installation cannot continue. Log on as an administrator ...
  28. The installer must restart your system before configuration of 2 can continue. Click Yes to restart now or No if you plan ...
  29. The installer must restart your system before configuration of 2 can continue. Click Yes to restart now or No if you plan ...
  30. The instance completed without consuming all its messages. The instance and its unconsumed messages have been suspended. ...
  31. The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended. ...
  32. The instance is no longer valid. No operations can be performed on an instance after dehydration or completion of that instance. ...
  33. The instance was reactivated elsewhere and all work related to this instance should be abandoned. This could be due to a ...
  34. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error in/before the first functional ...
  35. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error. A likely cause is invalid segment ...
  36. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error. Last structurally valid functional ...
  37. The interchange with id '{0}', with sender id '{1}', receiver id '{2}' had structural error. The part after the error is ...
  38. The interval in seconds after which the file will be downloaded again. Applicable if both DeleteAfterDownload and Enable ...
  39. The Isolated host represents service instances that are created, deleted, and controlled outside of administration tools, ...
  40. The IsReplacedBy tModel can not be used to refer back to the entity that owns the keyedreference containing the IsReplacedBy ...
  41. The key {0} has already been marked for custody transfer and cannot be present in more than one outstanding transfer request. ...
  42. The kill codes that were provided do not match. Ensure that the values typed in Kill Code and Confirm Kill Code are the same. ...
  43. The license key required to use Xceed FTP Library was not found or is invalid. Make sure that you have called the License ...
  44. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group ...
  45. The log file %1 that was provided in the configuration file cannot be used. Reason: %2. The default log file %3 will be used. ...
  46. The logon account does not have sufficient privileges to validate the account specified. On Windows 2000 the required privilege ...
  47. The machine is part of a Windows cluster but clustering functionality is supported only in the Enterprise Edition of Microsoft ...
  48. The machine you are executing the script on is a 32 bit machine and the following script executable is found to be 64 bit. ...
  49. The machine you are installing on is a 32 bit machine and the following component is found to be 64 bit. Installation could ...
  50. The Management database on SQL Server "{0}" / database "{1}" is incompatible with the expected schema version of this BizTalk ...
  51. The map contains a functoid that is not registered on this machine. Please contact the original author to obtain the required ...
  52. The map contains a reference to a schema node that is not valid. Perhaps the schema has changed. Try reloading the map in ...
  53. The map contains following invalid functoid(s) and/or link(s). Please validate the contents of your map. Saving the map file ...
  54. The map contains invalid functoids and links. Please validate the contents of your map. Saving the map file will delete all ...
  55. The map contains invalid functoids. Please validate the contents of your map. Saving the map file will delete all references ...
  56. The map contains invalid links. Please validate the contents of your map. Saving the map file will delete all references ...
  57. The map contains the CustomXslt tag, but does not contain the CustomExtensionXml tag. You will need this file if you have ...
  58. The map is referencing a destination schema ({0}) that is not in the project. Add the schema to this project or a referenced ...
  59. The map is referencing a source schema ({0}) that is not in the project. Add the schema to this project or a referenced project. ...
  60. The Map name should be of the form ' . ', where Project namespace and UniqueMapName are valid identifiers and UniqueMapName ...
  61. The map needs to be migrated from a previous version and cannot be compiled. Migrate this map file first before compiling ...
  62. The mapping xml does not confirm to the standard mapping xml schema. Following is the error message received upon validation ...
  63. The maximum delay imposed for Message Publishing Throttling. Zero indicates that Message Publishing Throttling is disabled. ...
  64. The maximum number of archive tables can be referenced by the archive view is 256. Please manually combine some of the tables ...
  65. The maximum time (milliseconds) that one event may be processed in the process pipeline. If the event exceeds this time, ...
  66. The measure {0} defined for the alert {1} does not exist. Make sure that the name of the measure specified in the alert matches ...
  67. The member '{0}' in '{1}' type is of a type that is not allowed. Only primitive types, strings and System.DateTime types ...
  68. The member '{0}' of type '{1}' cannot have the Property attribute. This attribute may only be associated with primitive fields ...
  69. The message agent or one of its internal objects is not initialized or has been uninitialized due to incorrect calling semantics. ...
  70. The Message Box is the primary repository for active messages in the BizTalk Server system. For scalability, BizTalk Server ...
  71. The message cannot be routed to the batching orchestration as the Encoding type could not be determined. The encoding type ...
  72. The message context is no longer available. The message or associated service instance may have been terminated in another ...
  73. The message currently opened in the message viewer is marked for tracking. Message gets tracked by the BizTalk Server when ...
  74. The message found multiple request response subscriptions. A message can only be routed to a single request response subscription. ...
  75. The message from the file "%1" cannot be authenticated. The file has been deleted without processing because the receive ...