BizTalk Server 2010

  1. The specified Repository on {0} with the name {1} is invalid. Please ensure that the Repository is installed correctly and ...
  2. The specified RFID Service account cannot be the same as the currently logged in user account. Please specify a different ...
  3. The specified ROSpec identifier is invalid because there is no matching ROSpec on the device. Specify a valid ROSpec identifier. ...
  4. The specified Rules Engine database does not match the pre-configured database for the BizTalk Server group. The pre-configured ...
  5. The specified Rules Engine database does not match the pre-configured database. The previously configured database for Rules ...
  6. The specified SQL database server "%1" / database name "%2" already exists and it cannot be re-used. Specify another SQL ...
  7. The specified timeout value exceeds the maximum value. It should be less than or equal to 10675199 when the time-out unit ...
  8. The specified timeout value exceeds the maximum value. It should be less than or equal to 35791394 when the time-out unit ...
  9. The specified timeout value exceeds the maximum value. It should be less than or equal to 596523 when the time-out unit is ...
  10. The specified username was rejected by the FTP server or the FTP server requires SSL to be enabled on the client. Check the ...
  11. The specified Windows group name was found in SQL Server with a Security Identifier (SID) different from the actual SID of ...
  12. The specified Windows SharePoint Services document library that stores Office templates documents was not found. There is ...
  13. The specified {0} is not associated with any running context. Either the entity has been detached or the parent context disposed. ...
  14. The SQL Server Sink component accepts date time parameters only within the range supported by Microsoft SQL Server. The specified ...
  15. The SSO backup file password is the current password of {0} as of {1} appended to {0}. For example, Domain\UsernamePassword. ...
  16. The start date/time must be greater than or equal to the current date/time. Do you want to change the start date time to ...
  17. The start of the character range must be less than or equal to the end of the character range. The character range that you ...
  18. The Status property is a string indicating the current status of the object. Various operational and non-operational statuses ...
  19. The stored procedure used for assembly removal failed for unknown reason. One possible cause may be foreign key constraint ...
  20. The string passed to the WSS.ConfigPropertiesXml message context property is not a valid xml document. The XmlDocument.Load ...
  21. The submitted BizTalk Framework document has "reliability" information specified. A synchronous call does not permit this ...
  22. The supplied expression is incorrect. All macros must be enclosed in '%'. The supported escape sequences are '\%' and '\'. ...
  23. The supplied KeepAlive interval is lower than the minimum supported value. Specify a KeepAlive interval greater than or equal ...
  24. The supplied timeout value is smaller than the minimum supported value of {0} ms. This range restriction does not apply to ...
  25. The supplied URL is pointing to a Windows SharePoint Services folder. The receive adapter cannot retrieve messages directly ...
  26. The supplied URL is pointing to a Windows SharePoint Services list. The receive adapter does not support retrieving messages ...
  27. The system application is by default referenced by all other applications and cannot be removed from referenced applications ...
  28. The table looping functoid has invalid or no table data. Either the column count is set wrong in the Functoid Input Configuration ...
  29. The Table looping functoid must be connected to at least one record or field element of the target schema whose descendants ...
  30. The tag-processing reliability mode for process {0} cannot be modified. It can only be set the first time that a process ...
  31. The target namespace of a schema cannot have the value: http://www.w3.org/2001/XMLSchema-instance or http://www.w3.org/2001/XMLSchema. ...
  32. The target namespace of the following property schema(s) has been changed since they have been added into this schema. Delete ...
  33. The target namespace of this schema cannot be blank because this schema has a prefix associated with the target namespace. ...
  34. The target node '{0}' has more than one Nil-Value functoid connected to it, with at least one being conditional. Depending ...
  35. The TDDS service attempted to access the tracking database while partitioning data was being changed. Make sure that repartitioning ...
  36. The third and fourth parameters of the Database Lookup functoid, which represent the table name and column name, must be ...
  37. The throttling state of the message delivery. A non-zero value indicates that the message delivery is being throttled due ...
  38. The throttling state of the message publishing. A non-zero value indicates that the message publishing is being throttled ...
  39. The time interval, in seconds, between two consecutive queries performed by the adapter to see if any new messages are available ...
  40. The time to receive the message expired. The message was still in its local outgoing queue (generated locally by sender). ...
  41. The time window defined in one or more real-time aggregated alert instances is less than the time window for real-time aggregation ...
  42. The time window defined in the real-time aggregated alert '{0}' is greater than the time window for the real-time aggregation ...
  43. The timeout, in milliseconds, for the adapter runtime web service calls made to the Windows SharePoint Services adapter Web ...
  44. The Tracking database on SQL Server "{0}" / database "{1}" is incompatible with the expected schema version of this BizTalk ...
  45. The Tracking Profile Editor cannot start the activity from the location from which you have selected the ActivityID or ContinuationID ...
  46. The transaction set control number is not valid. Transaction set control number should alphanumeric value <= 9 characters ...
  47. The transaction specified cannot be imported. This error is sometimes reported during a remote transactional recieve operation ...
  48. The transactions option "Transactional" and the error handling option "Suspend request message on failure" should not both ...
  49. The transmit adapter "%1" is trying to do both synchronous and asynchronous transmission in the same transport batch. This ...
  50. The transport batch from adapter "%1" has been rejected by the messaging engine because the batch is empty. Contact the adapter ...
  51. The transport proxy method %1 failed for adapter %2: Reason: "Messaging engine has no record of delivering the message to ...
  52. The type does not contain any web methods. Type should contain at least one public method with attribute System.Web.Serv ...
  53. The type of the specified object "{0}" is not a supported type. Only primitives, arrays of primitives, and DSPI types are ...
  54. The type of value to search for in the store. For example, if this value is set to FindBySubjectDistinguishedName the find ...
  55. The type of WMI context property "%1" is invalid. Date is expected to be passed as string in DMTF time format. Use SWbemDateTime ...
  56. The type {0}.{1} cannot be used because it is not Epcis serializable. Mark the type with the EpcisSerializableAttribute attribute. ...
  57. The upgrade process could take a considerable amount of time if you have a large tracking (DTA) database. It is strongly ...
  58. The user 2 does not have enough privileges. Do you want to grant the user the required privileges and continue the installation? ...
  59. The user 2 is an invalid user, or the password entered is incorrect. System error = 3 (error = 4]). Please check the spelling ...
  60. The user can also select any aggregate amount (e.g. 400 invoices still in "evaluation") and see the underlying individual ...
  61. The user is an invalid user, or the password entered is incorrect. Please check the spelling of the user name and try again. ...
  62. The user must be part of the "EDI Subsystem Users" group and the BizTalk/EDI/HIPAA databases must be on-line to migrate EDI ...
  63. The user must be part of the "EDI Subsystem Users" group and the BizTalk/EDI/HIPAA databases must be on-line. Please make ...
  64. The user you specified, %1, has admin privileges on this computer. To make your computer more secure, specify a user with ...
  65. The value of the name that has been supplied to the VendorEntityKey constructor is null or empty. Specify the name that corresponds ...
  66. The value of the property "%1" is different from the previous value for the property. This property cannot be updated and ...
  67. The value of the property "%1" is different from the previous value for the property. This property cannot be updated and ...
  68. The version of Microsoft BizTalk RFID that you are using is no longer valid. Use a newer version of Microsoft BizTalk RFID. ...
  69. The version of Microsoft SQL Server Analysis Services on server %1 must be the equivalent version as on the SQL server of ...
  70. The version of Microsoft SQL Server Analysis Services on server {0} must be the equivalent version as on the SQL server of ...
  71. The version of Microsoft SQL Server on server %1 must be the same version as on the server of the BAM Primary Import Database. ...
  72. The version of the schema being used by the Web server ({0}) is not compatible with the version of the schema being used ...
  73. The version of the schema used by the Notification server located on %s (%s) is not compatible with the version of the schema ...
  74. The version of the schema used by the Web server located on %s (%s) is not compatible with the version of the schema being ...
  75. The View name or Activity name are incorrect. The View or Activity may have been removed or you may not have access to them ...