BizTalk Server 2006 R2

  1. The synchronization has failed due to a failure of the StsWebService Web method Synchronize. Check the connectivity to the ...
  2. The system application is by default referenced by all other applications and cannot be removed from referenced applications ...
  3. The table looping functoid has invalid or no table data. Either the column count is set wrong in the functoid properties ...
  4. The Table looping functoid must be connected to at least one record or field element of the target schema whose descendents ...
  5. The tag-processing reliability mode for process {0} cannot be modified. It can only be set the first time that a process ...
  6. The target namespace of a schema cannot have the value: http://www.w3.org/2001/XMLSchema-instance or http://www.w3.org/2001/XMLSchema. ...
  7. The target namespace of the following property schema(s) has been changed since they have been added into this schema. Delete ...
  8. The target namespace of this schema cannot be blank because this schema has a prefix associated with the target namespace. ...
  9. The target node '{0}' has more than one Nil-Value functoid connected to it, with at least one being conditional. Depending ...
  10. The target shape is in a Group shape, but the source shape is not. Both the source and target shapes must be members of the ...
  11. The TDDS service attempted to access the tracking database while partitioning data was being changed. Make sure that repartitioning ...
  12. The third and fourth parameters of the Database Lookup functoid, which represent the table name and column name, must be ...
  13. The throttling state of the message delivery. A non-zero value indicates that the message delivery is being throttled due ...
  14. The throttling state of the message publishing. A non-zero value indicates that the message publishing is being throttled ...
  15. The time interval, in seconds, between two consecutive queries performed by the adapter to see if any new messages are available ...
  16. The time to receive the message expired. The message was still in its local outgoing queue (generated locally by sender). ...
  17. The time window defined in one or more real-time aggregated alert instances is less than the time window for real-time aggregation ...
  18. The time window defined in the real-time aggregated alert '{0}' is greater than the time window for the real-time aggregation ...
  19. The timeout, in milliseconds, for the adapter runtime web service calls made to the Windows SharePoint Services adapter Web ...
  20. The top level element is missing. A valid parameter schema must contain a root element. Add a child record to the schema ...
  21. The Tracking database on SQL Server "{0}" / database "{1}" is incompatible with the expected schema version of this BizTalk ...
  22. The Tracking Profile Editor cannot start the activity from the location from which you have selected the ActivityID or ContinuationID ...
  23. The transactions option "Transactional" and the error handling option "Suspend request message on failure" should not both ...
  24. The transmit adapter "%1" is trying to do both synchronous and asynchronous transmission in the same transport batch. This ...
  25. The transport batch from adapter "%1" has been rejected by the messaging engine because the batch is empty. Contact the adapter ...
  26. The transport proxy method %1 failed for adapter %2: Reason: "Messaging engine has no record of delivering the message to ...
  27. The type does not contain any web methods. Type should contain at least one public method with attribute System.Web.Serv ...
  28. The type of the specified object is not a supported type. Only primitives, arrays of primitives, and DSPI types are supported. ...
  29. The type of value to search for in the store. For example, if this value is set to FindBySubjectDistinguishedName the find ...
  30. The type of WMI context property "%1" is invalid. Date is expected to be passed as string in DMTF time format. Use SWbemDateTime ...
  31. The Unregister method removes the action from the list of actions that actors can use. Possible return values: 0 - Success. ...
  32. The upgrade process could take a considerable amount of time if you have a large tracking (DTA) database. It is strongly ...
  33. The URL for sending the response message for this HWS installation has not been specified in the configuration database. ...
  34. The user 2 does not have enough privileges. Do you want to grant the user the required privileges and continue the installation? ...
  35. The user 2 is an invalid user, or the password entered is incorrect. System error = 3 (error = 4]). Please check the spelling ...
  36. The user account used for HWS Web Service must be the same as the account used for HWS Runtime unless the two features are ...
  37. The user can also select any aggregate amount (e.g. 400 invoices still in "evaluation") and see the underlying individual ...
  38. The user is an invalid user, or the password entered is incorrect. Please check the spelling of the user name and try again. ...
  39. The user must be part of the "EDI Subsystem Users" group and the BizTalk/EDI/HIPAA databases must be on-line to migrate EDI ...
  40. The user must be part of the "EDI Subsystem Users" group and the BizTalk/EDI/HIPAA databases must be on-line. Please make ...
  41. The user name was located, but on a different domain than the one specified. The user will not be added as a trusted account. ...
  42. The user you specified, %1, has admin privileges on this computer. To make your computer more secure, specify a user with ...
  43. The value of '{0}' is not valid. Leading spaces, trailing spaces, any group of 2 or more spaces, including tabs and paragraph ...
  44. The value of the name that has been supplied to the VendorEntityKey constructor is null or empty. Specify the name that corresponds ...
  45. The value of the property "%1" is different from the previous value for the property. This property cannot be updated and ...
  46. The value of the property "%1" is different from the previous value for the property. This property cannot be updated and ...
  47. The version of Microsoft BizTalk RFID that you are using is no longer valid. Use a newer version of Microsoft BizTalk RFID. ...
  48. The version of Microsoft SQL Server Analysis Services on server %1 must be the equivalent version as on the SQL server of ...
  49. The version of Microsoft SQL Server Analysis Services on server {0} must be the equivalent version as on the SQL server of ...
  50. The version of Microsoft SQL Server on server %1 must be the same version as on the server of the BAM Primary Import Database. ...
  51. The view creation cannot be launched because the workbook is read-only. Please use Save-As to save a writable copy of the ...
  52. The View name or Activity name are incorrect. The View or Activity may have been removed or you may not have access to them ...
  53. The View name, Activity name or Instance could not be found. It may have been removed or you may not have access to it anymore. ...
  54. The vocabulary cannot be renamed as there are one or more unsaved versions. Save the modified versions and then try again. ...
  55. The volume label '[2]' on the media you're running from doesn't match the label '[3]' given in the Media table. This is allowed ...
  56. The WCF service host at address {0} has faulted and as a result no more messages can be received on the corresponding receive ...
  57. The WCF service host at address {0} was successfully restarted, therefore the associated receive location can now receive ...
  58. The Web site selected is not configured with the expected ASP.NET version. The expected version is %1, the actual version ...
  59. The Web site specified for the BAS site is not configured with the expected ASP.NET version. The expected version is %1, ...
  60. The Windows group is used to control access of this host and the associated host instances to databases and other resources. ...
  61. The Windows Installer service cannot update one or more protected Windows files. SFP Error: 2]. List of protected files: ...
  62. The Windows Installer service cannot update one or more protected Windows files. {SFP Error: 2]. List of protected files: ...
  63. The Windows Installer service cannot update the protected Windows file 2]. {Package version: 3], OS Protected version: 4], ...
  64. The Windows Installer service cannot update the system file 2 because the file is protected by Windows. You may need to update ...
  65. The Windows Installer service cannot update the system file 2 because the file is protected by Windows. You may need to update ...
  66. The Windows Installer Service could not be accessed. Contact your support personnel to verify that it is properly registered ...
  67. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows ...
  68. The Windows SharePoint Services adapter failed to archive the SharePoint document "{0}" into the "{1}" document library. ...
  69. The Windows SharePoint Services adapter failed to delete the SharePoint document "{0}". The error described below has been ...
  70. The Windows SharePoint Services adapter failed to undo the check-out operation for the SharePoint document "{0}". The error ...
  71. The Windows SharePoint Services adapter found no Office documents matching the namespace "{0}". Both document libraries - ...
  72. The Windows SharePoint Services adapter has caught an unexpected exception. More details regarding this exception can be ...
  73. The Windows SharePoint Services adapter has encountered an error while saving the processing results into SharePoint. {0} ...
  74. The Windows SharePoint Services adapter has failed to update the message context for the outgoing message delivered to the ...
  75. The Windows SharePoint Services adapter runtime does not have permissions to invoke the adapter Web service. In order to ...