BizTalk Server 2010

  1. Error encountered during parsing. The X12 functional group with id '{0}', in interchange with id '{1}', with sender id '{2}', ...
  2. Error encountered during parsing. The X12 interchange with id '{0}', with sender id '{1}', receiver id '{2}' had the following ...
  3. Error encountered during parsing. The X12 transaction set with id '{0}' contained in functional group with id '{1}', in interchange ...
  4. Error encountered during serialization. The Edifact functional group with id '{0}', in interchange with id '{1}', with sender ...
  5. Error encountered during serialization. The Edifact interchange which did not contain a group, with interchange id '{0}', ...
  6. Error encountered during serialization. The Edifact interchange with id '{0}', with sender id '{1}', receiver id '{2}' had ...
  7. Error encountered during serialization. The Edifact transaction set with id '{0}' contained in functional group with id '{1}', ...
  8. Error encountered during serialization. The Edifact transaction set with id '{0}' contained in interchange (without group) ...
  9. Error encountered during serialization. The X12 functional group with id '{0}', in interchange with id '{1}', with sender ...
  10. Error encountered during serialization. The X12 interchange with id '{0}', with sender id '{1}', receiver id '{2}' had the ...
  11. Error encountered during serialization. The X12 transaction set with id '{0}' contained in functional group with id '{1}', ...
  12. Error encountered during Upgrade: Failed to uninstall %1. HRESULT: %2!x!. %1 Databases have been upgraded. %1 Uninstall has ...
  13. Error encountered while querying virtual server state for URL: %1. Make sure the site is extended by Windows SharePoint Services. ...
  14. Error encountered while upgrading Database: %1 on SQL Server: %2. Following databases have been modified: %3 You must manually ...
  15. Error encountered with setting Accounting Token. The Acounting Token must be a hexadecimal representation of binary data ...
  16. Error encountered with setting Correlation ID. The Correlation ID must be a hexadecimal representation of binary data of ...
  17. Error encountered with setting Facility Token in CICS Bridge header. The Facility Token must be a hexadecimal representation ...
  18. Error encountered with setting Group ID. The Group ID must be a hexadecimal representation of binary data of length MQ_GROUP_ID_LENGTH. ...
  19. Error encountered with setting Message ID. The Message ID must be a hexadecimal representation of binary data of length MQ_MSG_ID_LENGTH. ...
  20. Error encountered with setting Transaction Id in IMS Bridge header. The Transaction Id must be a hexadecimal representation ...
  21. Error generating BAM configuration xml with the BAM Primary Import Table Database {1} on server {0}, address {2}, and account ...
  22. Error loading assembly from "{0}". Possible causes: 1. The location may not be fully trusted if it is on a network share. ...
  23. Error loading assembly from "{0}". The file may not be a .NET assembly. If the file is a .dll or .exe, it may be unmanaged ...
  24. Error occurred while attempting to track the message. It is possible that service instances referencing the message has already ...
  25. Error occurred while enumerating inbound adapters required for configuring receive locations used by the orchestration. %1 ...
  26. Error reading database server information. Please verify that the target computer hosts UDDI Services database components. ...
  27. Error registering COM+ application. Please ensure that DTC is enabled. Contact your support personnel for more information. ...
  28. Error trying to open log file. The file may be write-protected, blocked by another application or there is no enough space ...
  29. Error validating whether Microsoft SQL Server Client Tools with Data Transformation Services (DTS) for Archive is installed ...
  30. Error verifying signature of the redistributable component CAB file. Re-run Setup and download the CAB file from the correct ...
  31. Error while retrieving exported event types in assembly. Details: {0}. Resolve the issue that is causing the exception, and ...
  32. ERROR: Found {1} arguments for the command, whereas the expected number of arguments is {0}. Specify the correct number of ...
  33. ERROR: Found {2} arguments for the command, whereas the expected number of arguments is {0}-{1}. Specify the correct number ...
  34. Error: The dependency '%1' in project '%2' cannot be copied to the run directory because it would conflict with dependency ...
  35. Errors are encountered during the migration of individual entities. They are recorded to uddi.migration.report.xml. Please ...
  36. Errors were encountered while undeploying the process. For information about the event handlers with exceptions, look at ...
  37. Event handler method {1} in event handler {0} has an input parameter of type {2} which is not supported. Specify a parameter ...
  38. Event handler method {1} in event handler {0} has return type {2}, which is not supported. Specify a return type that is ...
  39. Event handler methods have overlapping input parameters. In event handler {0}, the type of input parameter {2} for method ...
  40. Event handler {0} has no methods that have the custom attribute RfidEventHandlerMethodAttribute. Specify at least one method ...
  41. Event handler {0} took too long to initialize. Consider increasing the Maximum Component Initialization Time parameter in ...
  42. Event source '{0}' with different definition already deployed in Primary Import Database. Please backup interceptor configurations ...
  43. Exception occurred in applying per instance configuration on component "{0}" . The exception message is: {1} The possible ...
  44. Exception while returning metadata for provider {0}. Details: {1}. Resolve the issue that is causing the exception, and then ...
  45. Executes the command specified in the XML file and prints the results to the console. For details of commands, refer to the ...
  46. Expected number of event are not present in the database to be deleted. Expected: {0}, Found: {1}. Specify a count less than ...
  47. Exporting application "{0}" bindings from BizTalk configuration database (server="{1}", database="{2}") into binding file ...
  48. Exporting assembly bindings from BizTalk configuration database (assembly="{0}", server="{1}", database="{2}") into binding ...
  49. Exports bindings for the specified process to the XML file. This method exports both the device bindings and the component ...
  50. Express This is the fastest mode where the messages are stored in memory of the MSMQ process. Reliable (recovery) In this ...
  51. Extra data in the document instance was not parsed. Verify the document instance you want to validate contains only one document. ...
  52. Failed in IPropertyPage::GetPageInfo() while creating adapter property pages. Contact owner of the adapter impelementation ...
  53. Failed to add a discovered device with name {0} and device information {1}. For detailed information, look at the RFID service ...
  54. Failed to add device {0} because the supplied transport type {1} is not supported by provider {2}. Specify a different transport ...
  55. Failed to add device {0} because the transport {1} with name {2} is not supported by provider {3}. Specify a valid transport ...
  56. Failed to bring the cluster resource online. This can be due to the following: 1) The Host Instance is not properly configured ...
  57. Failed to cleanup SQL role associating with BizTalk Host "%1" from MessageBox database server "%2" / database name "%3". ...
  58. Failed to construct the internal parse tables from the BizTalk assembly. Re-compile and deploy your project. Error Message: ...
  59. Failed to create a cluster resource. This can be due to the following: 1) You do not have the required privileges on the ...
  60. Failed to create an XPath for the XLANG/s distinguished field '{0}'. This could happen if the distinguished field is marked ...
  61. Failed to create COM object implementing adapter property page. Contact owner of the adapter impelementation for more details. ...
  62. Failed to create instance of COM component managing the property pages for the adapter. Verify that component is registered. ...
  63. Failed to create SQL login and grant SQL privilege configurations on BAM database server "%1" / database name "%2" while ...
  64. Failed to create SQL login and grant SQL privilege configurations on Rule Engine database server "%1" / database name "%2" ...
  65. Failed to create SQL login and grant SQL privilege configurations on the Management database server "%1" / database name ...
  66. Failed to create SQL login and grant SQL privilege configurations on Tracking database server "%1" / database name "%2" while ...
  67. Failed to create X509CertificateIdentity from certificate reference. (StoreName={0}, StoreLocation={1}, X509FindType={2}, ...
  68. Failed to delete database objects associated with BizTalk Host "%1" from MessageBox database server "%2" / database name ...
  69. Failed to deploy BAM activity definitions. Please make sure that all BAM related Data Transformation Services (DTS) packages ...
  70. Failed to detect Enterprise Single Sign-On service on this machine. Please make sure Enterprise Single Sign-On service is ...
  71. Failed to disambiguate the grammar with a lookahead depth of {0}. The following is a list of ambiguous rules and their definitions: ...
  72. Failed to drop role membership with Windows group "%1" from SQL role BTS_HOST_USERS on database server "%2" / database name ...
  73. Failed to execute commands on device {0} because the supplied connection GUID does not match an existing connection. Verify ...
  74. Failed to execute the specified command because another command with the same command identifier {0} is currently in progress. ...
  75. Failed to get network resource information. Error 2], network path 3]. Extended error: network provider 5], error code 4], ...