BizTalk Server 2010

  1. Microsoft SQL Server Data Transformation Services (DTS) 2008 with SP1 or higher for BAM Analysis is not installed on the ...
  2. Microsoft SQL Server Data Transformation Services (DTS) 2008 with SP1 or higher for BAM Archiving is not installed on the ...
  3. Microsoft UDDI Services is not supported on Windows XP or Windows Vista. Please install Microsoft UDDI Services on Windows ...
  4. Microsoft Update helps keep your computer secure and up-to-date for Windows and other Microsoft products. Updates will be ...
  5. Microsoft Update offers security and important updates for Windows and other Microsoft products, including ProductName]. ...
  6. Microsoft Update offers security and important updates for Windows and other Microsoft software, including Microsoft BizTalk ...
  7. Microsoft.RuleEngine.TypedXmlDocument' indicates an XML document binding. To specify a field binding, select a .NET type ...
  8. Migrate the tables */ DECLARE @tableChangeSql NVARCHAR(4000) - 1. Migrate Active instance table - Drop the trigger DROP TRIGGER ...
  9. Migrates the BAM infrastructure between different versions of Microsoft SQL Server. Use this command after you upgrade your ...
  10. Minimum Occurrences of the underlying group content of this Node. Its value should always be less than or equal to Group ...
  11. Minimum occurrences of this node. Its value should always be less than or equal to MaxOccurs for this node. Default value ...
  12. Most likely your URL got corrupted. Please navigate to the Tracking Options View using Navigation Control at the top of this ...
  13. MSMQT failed to accept an incoming authenticated message into the queue %1, because Active Directory integration ia not installed. ...
  14. MSMQT has been removed from this version of BizTalk Server. Please remove your MSMQT send ports and receive ports, and purge ...
  15. Multiple configurations already exist for TagName '{0}'. Please verify your config file or dictionary provided to EpcisBehavior. ...
  16. My UDDI displays only the entities - Web services, providers, and tModels - you publish. Any information you enter is immediately ...
  17. My UDDI displays only the entities - Web services, providers, and tModels - you publish. Any information you enter is immediately ...
  18. My UDDI enables you to publish and modify your Web service information. To publish a service, you must first publish a provider. ...
  19. Name and briefly describe the interface (or other data) that this tModel represents. The tModel key is unique and is intended ...
  20. Name and briefly describe this provider in one or more languages. The provider key is unique and is generated for use in ...
  21. Name and briefly describe this service in one or more languages. The service key is unique and is intended for use in programmatic ...
  22. Name of the BizTalk application in which to create receive locations. If not specified, the default BizTalk application is ...
  23. Name of the BizTalk assembly for which to export the binding file. If you specify inputs for Name, Version, Culture, and ...
  24. Name of the master subscription SQL database. This property is required for instance creation. Max length for this property ...
  25. Name of the MessageBox database. This property is required for instance creation. Max length for this property is 100 characters. ...
  26. Name of the SQL database where the tracked message is stored (either MessageBox or Archived DB). Max length for this property ...
  27. Name of the SQL server where the master subscription database is located. This property is required for instance creation. ...
  28. Name of the SQL server where the MessageBox database is located. This property is required for instance creation. Max length ...
  29. Name of the SQL server where the tracked message is stored (either MessageBox or Archived DB). Max length for this property ...
  30. Name of the SQL server where the tracking database is located. This property is required for instance creation. Max length ...
  31. Name of the tracking SQL database. This property is required for instance creation. Max length for this property is 123 characters. ...
  32. Name, describe, and categorize each Web service, making it easy to locate. Publish one or more access points for a service ...
  33. No auto start of send ports and send port groups of this orchestration. If there exists any send port or send port group ...
  34. No BAM activity found. You might have a corrupted installation on this machine. Please go to Add or Remove Programs to repair ...
  35. No BizTalk Host instances were found. In order to cluster a Host, it should have Host instances that are all installed on ...
  36. No Client Certificate matching the provided client certificate hash was found. Verify if the certificate is present in the ...
  37. No further selections exist. To continue, click an appropriate category in the list above, or click Cancel and try again. ...
  38. No information was found for this service instance in the Tracking database. This can occur when orchestration tracking is ...
  39. No instance was found with the specified key. This could be the result of the instance being deleted by another BizTalk Admin ...
  40. No links or functoids found in the clipboard that can be pasted on this map page. This may be due to already linked nodes ...
  41. No operation is allowed when the BizTalk orchestration is in the stopping state (meaning that there are still running instances ...
  42. No operation is allowed when the BizTalk orchestration is in the unbound state. You must first finish the port binding configuration ...
  43. No parameters have been specified for starting an orchestration, but the orchestration being started requires parameters. ...
  44. No printers are installed, or default printer cannot be located. To install a printer, point to Settings on the Windows Start ...
  45. No product was specified. Please use the '/Product' switch on the command line followed by the name of the product to install. ...
  46. No property schema found. Add a property schema to this list to be able to promote property fields. A property schema is ...
  47. No queries were found in the search path for saved queries. Use the Tools/Preferences menu item to configure the list of ...
  48. No subscriber owned the required decryption certificate to receive this message. Please verify the host that the intended ...
  49. No symbolic information was found for this orchestration. In the Visual Studio project containing the orchestration, set ...
  50. No WSDL/BPEL files were created. This happens if none of the files selected for export have the orchestration property 'Module ...
  51. Node "{0}" - Data type of this field or simple content record ({1}) and the promoted property '{2}' ({3}) should be the same ...
  52. Node "{0}" - Property schemas should contain only element fields under schema node and should not have blank target namespace. ...
  53. Node "{0}" - Specify a valid .NET type name for this root node. The current .NET type name of this root node is a duplicate. ...
  54. Node "{0}" - Specify a valid .NET type name for this root node. The current .NET type name of this root node is invalid (it ...
  55. Node "{0}" - The field data type for the property is invalid. Only the following XSD data types are allowed to be promoted ...
  56. Node "{0}" - The following property '{1}' of type xs:{2} will cause run-time failures if the solution is deployed in a Windows ...
  57. Node "{0}" - The promoted property field or one of its parents has Max Occurs greater than 1. Only nodes that are guaranteed ...
  58. Node "{0}" - This schema file has a .NET type name that collides with the .NET namespace of the property schema used in property ...
  59. Node "{0}" - This schema file has a TypeName that collides with the RootNode TypeName of one of its root nodes. Make sure ...
  60. Node "{0}" - This schema file has an invalid type name (it is a reserved BizTalk keyword or is an invalid C# identifier). ...
  61. None of the importers implemented supports this file extension. The offending document is "{0}". This error is generated ...
  62. None of the time stamp is present. Device has no time stamp information. If the problem persists contact your hardware vendor. ...
  63. Not view specific. This is the welcome screen (includes this content) which first greets users coming to the site. The content ...
  64. Note that any assembly that you choose a script from below must also be in the GAC (Global Assembly Cache) for TestMap to ...
  65. Note that this will not delete the sendport but only association of this port with the partner. Please confirm runtime will ...
  66. Note, a published policy or vocabulary version can be deleted. To change a published policy or vocabulary version, copy that ...
  67. Note: All RFID Service settings are stored in an RFID configuration database. Choosing to overwrite the database contents ...
  68. Note: All RFID Service settings are stored in an RFID configuration database. Choosing to overwrite the database contents ...
  69. NOTE: Setting the queue number will allow you to access the queue using the private format name: PRIVATE=machine guid\queue ...
  70. Note: The target URI can be assigned to a dynamic port using the Expression shape. For example: myPort(Microsoft.XLANGs.BaseTypes.Address) ...
  71. Notes: It is not necessary to specify the fully qualified name of a type. Abbreviate a type name by not specifying the prefix ...
  72. Notification will be sent to the address specified in the "From:" property that is configured on the SMTP send handler or ...
  73. Number of batches received by the Messaging Engine that have not completed processing. These include batches that have been ...
  74. Number of batches that have been blocked on receive by the Messaging Engine due to high service load. These batches contain ...
  75. Number of bytes received by adapter per second. The counter applies only to messages that have been completely read by the ...