BizTalk Server 2006 R2

  1. Microsoft BizTalk RFID has encountered an internal error. The state of the process {0} is in a corrupted state in the RFID ...
  2. Microsoft BizTalk RFID has encountered an internal error: cannot post a null event to the SQL Server Sink. If this situation ...
  3. Microsoft BizTalk RFID has encountered an internal error: the response to the command was unexpectedly null. Contact Microsoft ...
  4. Microsoft BizTalk RFID has encountered an internal error: there is no security token in the Web services request. If this ...
  5. Microsoft BizTalk RFID has encountered an internal server error: attempting to remove a nonexistent application domain {0}. ...
  6. Microsoft BizTalk RFID has encountered an internal server error: cannot obtain WindowsIdentity from principal. If this situation ...
  7. Microsoft BizTalk RFID has encountered an internal server error: some application domains are still loaded; therefore, the ...
  8. Microsoft BizTalk RFID service could not find any information on this provider. Specify the name of an existing provider. ...
  9. Microsoft BizTalk Server 2006 Administration. Copyright 2006 Microsoft Corporation. . Warning: This computer program is protected ...
  10. Microsoft collects information about errors in the runtime components of {0}. This information is used solely to improve ...
  11. Microsoft Office 2003 Web Components are not installed on this computer. BizTalk Server Health and Activity Tracking (HAT) ...
  12. Microsoft Sql Notification Services 2000 is not installed with Database Components or an incompatible version is installed ...
  13. Microsoft Sql Notification Services 2000 is not installed with Engine Components or an incompatible version is installed ...
  14. Microsoft Sql Notification Services 2005 is not installed with Engine Components or an incompatible version is installed ...
  15. Microsoft Sql Notification Services is not installed with Client or Engine Components or an incompatible version is installed ...
  16. Microsoft SQL Server 2000 Analysis Services with SP4 or 2005 is not installed or an incompatible version is installed on: ...
  17. Microsoft SQL Server 2000 Data Transformation Services (DTS) for BAM Analysis is not installed on the local machine. Please ...
  18. Microsoft SQL Server 2000 Data Transformation Services (DTS) for BAM Archiving is not installed on the local machine. Please ...
  19. Microsoft SQL Server 2005 Analysis Management Objects (AMO) is not installed on the local machine. Please install Microsoft ...
  20. Microsoft SQL Server 2005 Data Transformation Services (DTS) for BAM Analysis is not installed on the local machine. Please ...
  21. Microsoft SQL Server 2005 Data Transformation Services (DTS) for BAM Archiving is not installed on the local machine. Please ...
  22. Microsoft Update offers security and important updates for Windows and other Microsoft products, including ProductName]. ...
  23. Microsoft Update offers security and important updates for Windows and other Microsoft software, including Microsoft BizTalk ...
  24. Microsoft.RuleEngine.TypedXmlDocument' indicates an XML document binding. To specify a field binding, select a .NET type ...
  25. Migrates the BAM infrastructure from Microsoft SQL Server 2000 to Microsoft SQL Server 2005. Use this command after you upgrade ...
  26. Minimum Occurrences of the underlying group content of this Node. Its value should always be less than or equal to Group ...
  27. Minimum occurrences of this node. Its value should always be less than or equal to MaxOccurs for this node. Default value ...
  28. Missing parameters; specify parameter ASSEMBLY="pathname" or parameters NAME="assembly-name", VERSION="assembly-version", ...
  29. Missing parameters; specify parameter ASSEMBLY="pathname" or parameters NAME="assembly-name", VERSION="assembly-version", ...
  30. More than one source-info is specified for non-partitioned data-source '%0'. A non-partitioned data source may only have ...
  31. Most likely your URL got corrupted. Please navigate to the Tracking Options View using Navigation Control at the top of this ...
  32. MSMQT failed to accept an incoming authenticated message into the queue %1, because Active Directory integration ia not installed. ...
  33. Name of the BizTalk application in which to create receive locations. If not specified, the default BizTalk application is ...
  34. Name of the BizTalk assembly for which to export the binding file. If you specify inputs for Name, Version, Culture, and ...
  35. Name of the master subscription SQL database. This property is required for instance creation. Max length for this property ...
  36. Name of the MessageBox database. This property is required for instance creation. Max length for this property is 100 characters. ...
  37. Name of the SQL database where the tracked message is stored (either MessageBox or Archived DB). Max length for this property ...
  38. Name of the SQL server where the master subscription database is located. This property is required for instance creation. ...
  39. Name of the SQL server where the MessageBox database is located. This property is required for instance creation. Max length ...
  40. Name of the SQL server where the tracked message is stored (either MessageBox or Archived DB). Max length for this property ...
  41. Name of the SQL server where the tracking database is located. This property is required for instance creation. Max length ...
  42. Name of the tracking SQL database. This property is required for instance creation. Max length for this property is 123 characters. ...
  43. No auto start of send ports and send port groups of this orchestration. If there exists any send port or send port group ...
  44. No BAM activity found. You might have a corrupted installation on this machine. Please go to Add or Remove Programs to repair ...
  45. No BizTalk Host instances were found. In order to cluster a Host, it should have Host instances that are all installed on ...
  46. No information was found for this service instance in the Tracking database. This can occur when orchestration tracking is ...
  47. No instance was found with the specified key. This could be the result of the instance being deleted by another BizTalk Admin ...
  48. No operation is allowed when the BizTalk orchestration is in the stopping state (meaning that there are still running instances ...
  49. No operation is allowed when the BizTalk orchestration is in the unbound state. You must first finish the port binding configuration ...
  50. No parameters have been specified for starting an orchestration, but the orchestration being started requires parameters. ...
  51. No printers are installed, or default printer cannot be located. To install a printer, point to Settings on the Windows Start ...
  52. No product was specified. Please use the '/Product' switch on the command line followed by the name of the product to install. ...
  53. No Profiles resource is available for the site. Either use the site packager to add a Profiles resource to the site or remove ...
  54. No property schema found. Add a property schema to this list to be able to promote property fields. A property schema is ...
  55. No queries were found in the search path for saved queries. Use the Tools/Preferences menu item to configure the list of ...
  56. No Rules Engine database was registered for the BizTalk Server group. If you specified "Yes" as the answer to the question ...
  57. No subscriber owned the required decryption certificate to receive this message. Please verify the host that the intended ...
  58. No symbolic information was found for this orchestration. In the Visual Studio project containing the orchestration, set ...
  59. No views are accessible for the activity and Web page URI that you have entered. Check to make sure the activity has been ...
  60. No WSDL/BPEL files were created. This happens if none of the files selected for export have the orchestration property 'Module ...
  61. Node "{0}" - Data type of this field or simple content record ({1}) and the promoted property '{2}' ({3}) should be the same ...
  62. Node "{0}" - Property schemas should contain only element fields under schema node and should not have blank target namespace. ...
  63. Node "{0}" - Specify a valid .NET type name for this root node. The current .NET type name of this root node is a duplicate. ...
  64. Node "{0}" - Specify a valid .NET type name for this root node. The current .NET type name of this root node is invalid (it ...
  65. Node "{0}" - The field data type for the property is invalid. Only the following XSD data types are allowed to be promoted ...
  66. Node "{0}" - The following property '{1}' of type xs:{2} will cause run-time failures if the solution is deployed in a Windows ...
  67. Node "{0}" - The promoted property field or one of its parents has Max Occurs greater than 1. Only nodes that are guaranteed ...
  68. Node "{0}" - This schema file has a .NET type name that collides with the .NET namespace of the property schema used in property ...
  69. Node "{0}" - This schema file has a TypeName that collides with the RootNode TypeName of one of its root nodes. Make sure ...
  70. Node "{0}" - This schema file has an invalid type name (it is a reserved BizTalk keyword or is an invalid C# identifier). ...
  71. None of the importers implemented supports this file extension. The offending document is "{0}". This error is generated ...
  72. Not view specific. This is the welcome screen (includes this content) which first greets users coming to the site. The content ...
  73. Note that any assembly that you choose a script from below must also be in the GAC (Global Assembly Cache) for TestMap to ...
  74. Note, a published policy or vocabulary version can be deleted. To change a published policy or vocabulary version, copy that ...
  75. Note: All RFID Service settings are stored in an RFID configuration database. Choosing to overwrite the database contents ...