BizTalk Server 2006 R2

  1. The provider for the device %1 has encountered a fault that could result in unpredictable behavior of this device. If this ...
  2. The Provider Manager startup has failed to start up completely within the specified time. Try restarting the Microsoft BizTalk ...
  3. The provider metadata retrieved from assembly {0} was unexpectedly null. For further assistance, contact your provider vendor. ...
  4. The provider {0} has either not been started or has encountered an error. Restart the provider in the service. If that does ...
  5. The public address of this location. This address is used to describe a specific server and database to an external partner. ...
  6. The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration ...
  7. The query cannot be opened. Check the file name and try again. Contact your System Administrator if the problem persists. ...
  8. The query cannot be opened. The file does not exists or you do not have the required permissions to access it. Correct the ...
  9. The Query Service Timeout value is invalid or out of range. It must be a strictly positive integer and cannot exceed 1 hour. ...
  10. The real-time aggreagation connection did not refresh successfully. There may not exist any data in the real-time aggregation ...
  11. The Receive Adapter "%1" threw an exception while receiving the handler configuration from the Messaging Engine. Exception ...
  12. The receive adapter on this receive location is not supported on 64-bit host instances. Please make sure that the receive ...
  13. The receive handler configuration for the Windows SharePoint Services adapter is invalid. The following error has been raised: ...
  14. The receive location encountered an error receiving messages. As per configuration to stop on failure, this receive location ...
  15. The receive pipeline: "%1" for receive location: "%2" is trying to explicitly suspend a message that has a non-seekable stream. ...
  16. The receive pipeline:"%1" is trying to suspend a message received on Receive Location:"%2". The Adapter/Receive Location ...
  17. The Register method registers the XLANG schedule as an action that other actors can use. Possible return values: 0 - Success. ...
  18. The reported device identifier {0} and the reported connection information {1} in the physical device information affect ...
  19. The reported device identifier {0} and the reported name {1} in the physical device information affect more than one device. ...
  20. The reported device name {0} and the reported connection information {1} in the physical device information affect more than ...
  21. The reported name {0} for the physical device and the corresponding name {1} for the device maintained by BizTalk RFID do ...
  22. The reported physical device name %1 and the corresponding logical device name %2 do not match. Rename the device using BizTalk ...
  23. The requested operation cannot be completed because of a previous WMI failure. The WMI object path is empty in this case. ...
  24. The requested operation is not allowed when the BizTalk orchestration is in the bound state. The only allowed operation is ...
  25. The requested operation is not allowed when the BizTalk orchestration is in the started state. The only allowed operation ...
  26. The requested operation is not allowed when the BizTalk orchestration is in the stopped state. The allowed operations are ...
  27. The resource could not be found in the application "{0}". Please verify that you provided the correct application name. If ...
  28. The revocation status is unknown for the certificate used to encrypt the message. This might be because the Certificate authority ...
  29. The revocation status is unknown for the certificate used to sign the message. This might be because the certificate authority ...
  30. The RFID Business process brings together powerful concepts to create an Event Processing topology. In a RFID business process, ...
  31. The RFID Print Label Wizard cannot be started because the selected printer does not have any print templates. Add one or ...
  32. The RFID process engine %1 encountered an error of type %2. The service will attempt to restart this process engine automatically, ...
  33. The RFID SDK feature contains product samples, a sample device simulator and a sample device provider along with source code. ...
  34. The Rfid Services feature contains components for Rfid Service Engine, Business Rule Engine, Rfid Store and Rule Engine Database, ...
  35. The RFID Tools and Client Connector feature contains components for the Client Console administration tool, Rfid Connector ...
  36. The role link type {0} does not exist in the project. Update role link types associated with this BAS parameter schema by ...
  37. The RTA timeslice value cannot be greater than the RTA window value. For best results the RTA window should be a multiple ...
  38. The Rules Engine database currently configured on this machine (server = '{0}', database = '{1}') does not match the database ...
  39. The Rules Engine is configured but the database (server = %1, database = %2) can not be found. Please uncofigure the Business ...
  40. The Rules Engine is configured but the database (server = '{0}', database = '{1}') can not be found. Please unconfigure the ...
  41. The rules policy "{0}" with version {1} is not published. Only published policies can be associated with an application. ...
  42. The runtime configuration of Microsoft BizTalk RFID service is not in a valid format. Reason: {0}. Verify that the data in ...
  43. The runtime configuration of the Microsoft BizTalk RFID service does not conform to the schema due to {0}. Verify that the ...
  44. The Schema Annotations: Default Child Delimiter, Default Repeating Delimiter, Default Wrap Character, and Default Escape ...
  45. The Schema Annotations: Default Child Delimiter, Default Repeating Delimiter, Default Wrap Character, and Default Pad Character ...
  46. The schema does not have the structure of a property schema. A property schema can only have element field(s) directly under ...
  47. The Schema node's Default Repeating Delimiter and Default Repeating Delimiter Type properties must be set if a record's repeating ...
  48. The schema of the returned table differs in the following way: {0}. Delete the SQL Server Sink database, and then create ...
  49. The schema to be imported has a blank target namespace. Only schemas that have a target namespace can be imported, and that ...
  50. The schema version of the registered Management database on server "%1" / database name "%2" is incompatible with the expected ...
  51. The schema you are trying to open is an XDR schema (BizTalk 2000 or BizTalk 2002 format). Do you want to convert this schema ...
  52. The Schema: "{0}" has custom promoted properties. Migration Wizard is unable to automatically promote them. Please promote ...
  53. The schema_type attribute has the value "xml". Only non-XML document specifications are allowed for this format. Verify the ...
  54. The search condition(s) contain a Numeric Range Dimension with an empty value. When used as search conditions for alerts, ...
  55. The search condition(s) contain a Progress Dimension with an incorrect value. Progress Dimension values must be either all ...
  56. The selected assembly has more than one provider. Choose the provider that you want to register from the list of available ...
  57. The selected Excel file either does not exist or has no sheets in it. Specify an existing Excel file containing one or more ...
  58. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  59. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  60. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  61. The selected help topic is not available. This message typically appears when BizTalk Server documentation was not installed. ...
  62. The selected item does not exist. It may have been deleted or modified by another user. Click "Home" at the top of the page ...
  63. The selector (XPath) that identifies the element or attribute field. The default is the field XPath obtained from the schema. ...
  64. The selector (XPath) that identifies the portion of interest in the XML document. The default is the instance XPath obtained ...
  65. The self profile '{0}' for the agreement '{1}' does not exist on the target BAS site yet. Please create this profile before ...
  66. The send adapter for this send port is not supported on 64-bit host instances. Please make sure that the send adapter is ...
  67. The send handler configuration for the Windows SharePoint Services adapter is invalid. The following error has been raised: ...
  68. The send port's transport types cannot be changed to or from MSMQT unless the send port is unenlisted. Please unenlist the ...
  69. The SendPort :"{0}" is migrated with information from the channel("{1}"). The channel has filter expression:"{2}". Migration ...
  70. The SendPortGroup :"{0}" is migrated with information from the channel("{1}"). The channel has filter expression:"{2}". Migration ...
  71. The sequence starting with '\' is invalid. Use '\', '\{' or '\}' if you want to specify one of the symbols '\', '{' and '}' ...
  72. The serializer component cannot find a control number for %1 %2 in the BizTalk Management database. This document will be ...
  73. The serializer component failed to build the custom envelope ID:"%1". This was because of errors in the XML Schema supplied. ...
  74. The serializer component has encountered an invalid character, "%1". An entry specified in the InvalidCharacterMap tag of ...
  75. The serializer failed to create the custom envelope because the XML specification did not specify a Document Container Node ...