BizTalk Server 2006 R2

  1. is not a valid value for the parameter field '{1}'. Select one of the available valid values for the field in the Addendums ...
  2. is too long for a Continuation or ContinuationId. Continuation or ContinuationId names cannot be longer than {1} characters. ...
  3. It is not recommended that you use the actual local computer name for Message Queuing. If you register the name with DNS ...
  4. It may be necessary to stop one or more system services during installation. For information on the affected services, click ...
  5. item(s) displayed. To view more details on an entry, right-click the cell and select Orchestration Debugger or Message Flow ...
  6. Items on this list require content approval. Your submission will not appear in public views until approved by someone with ...
  7. Jurisdiction Identification Number Plus 4 as assigned by the International Association of Industrial Accident Boards and ...
  8. Like the Activity Search page, the Alert Manager is broken into three sections in the Content frame: 1) Alert Summary - this ...
  9. Lists all activities for the given view on the current database. Lists all activities in the current database if no view ...
  10. Lists all alerts for the given view on the current database. Lists all alerts in the database if no view name is specified. ...
  11. Lists BizTalk assemblies in BizTalk Configuration database. LIST SERVER=server DATABASE=database SERVER Optional name of ...
  12. Lists the directories to search when the project is loaded for assemblies referenced by the project. This setting is specific ...
  13. literal of type '%1!s!' cannot be implicitly converted to type '%2!s!'; use an '%3!s!' suffix to create a literal of this ...
  14. Loading InfoPath templates to BAS SharePoint site failed. Check that the Windows SharePoint Services configuration and content ...
  15. Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed ...
  16. Loads the server configuration from the specified XML file and sets it at the server. The format of the file should be the ...
  17. Logical device {0} is being bound to device {1}. Device {1} is either in an unconfigured state or is not present in the RFID ...
  18. Make sure that variable and parameter types match. No information will be displayed in the grid if called orchestration has ...
  19. Make sure the document has the correct standard, and a valid standard_version. The CodeList database table name is constructed ...
  20. Mandatory entities cannot have a default value. A mandatory property is one which necessarily requires the user to provide ...
  21. Map the BizTalk server to the BizTalk Host. You must establish this mapping before an instance of this BizTalk host can be ...
  22. Max limit of acceptable Edifact functional group control number has reached for Guest settings. Reset counter by navigating ...
  23. Max limit of acceptable Edifact functional group control number has reached for party {0}. Reset counter by navigating to ...
  24. Max limit of acceptable Edifact interchange control number has reached for Guest settings. Reset counter by navigating to ...
  25. Max limit of acceptable Edifact interchange control number has reached for party {0}. Reset counter by navigating to Party ...
  26. Max limit of acceptable Edifact transaction set control number has reached for Guest settings. Reset counter by navigating ...
  27. Max limit of acceptable Edifact transaction set control number has reached for Guest settings. Reset counter by navigating ...
  28. Max limit of acceptable Edifact transaction set control number has reached for party {0}. Reset counter by navigating to ...
  29. Max limit of acceptable X12 functional group control number has reached for Guest settings. Reset counter by navigating to ...
  30. Max limit of acceptable X12 functional group control number has reached for party {0}. Reset counter by navigating to Party ...
  31. Max limit of acceptable X12 interchange control number has reached for Guest settings. Reset counter by navigating to Global ...
  32. Max limit of acceptable X12 interchnage control number has reached for party {0}. Reset counter by navigating to Party in ...
  33. Max limit of acceptable X12 transaction set control number has reached for Guest settings. Reset counter by navigating to ...
  34. Max limit of acceptable X12 transaction set control number has reached for party {0}. Reset counter by navigating to Party ...
  35. Maximum Delay (in milliseconds) imposed for Message Delivery Throttling. Zero indicates disable Message Delivery Throttling. ...
  36. Maximum Delay (in milliseconds) imposed for Message Publishing Throttling. Zero indicates disable Message Publishing Throttling. ...
  37. Maximum Occurrences of the underlying group content of this Node. Its value should always be greater than or equal to Group ...
  38. Maximum Occurrences of this node. Its value should always be greater than or equal to minOccurs of this node. Use 'unbounded' ...
  39. Maximum possible length for the target environment name is 128. Provide a shorter target environment name for resource (Luid ...
  40. Medicaid Provider and Supplier Identification Number as assigned by individual State Medicaid Agencies in conjunction with ...
  41. Memory usage values from 1 to 100 will be treated as percentages, and values greater than 100 will be in megabytes. Please ...
  42. Message can not be serialized as the schema {0} could not be located. Either the schema is not deployed or multiple copies ...
  43. Message context information cannot be loaded. This usually happens when user doesn't have privileges to view message context. ...
  44. Message flow information for this instance can only be accessed via the MessageRoutingDetails for a specific message associated ...
  45. Message has been marked for tracking. Message gets tracked by the BizTalk server when it is no longer in use by the runtime. ...
  46. Message parts using native XSD types are not supported. Correct service description "{0}" message type "{1}" part "{2}" and ...
  47. Message processing throttling values determine how and when this BizTalk Server host will throttle message processing. Use ...
  48. Message publishing throttling values determines how and when this BizTalk Server host will throttle message publishing. Use ...
  49. Message types without parts are not supported. Correct service description "{0}" message type "{1}" and rerun the wizard. ...
  50. MessageBox creation failed and some of the changes could not be rolled back. Refer to BizTalk documentation regarding manual ...
  51. Messagebox host-specific performance counters will not be created if the combined lengths of the host name, message box name, ...
  52. Messagebox host-specific performance counters will not be created if the combined lengths of the host name, message box name, ...
  53. Messages larger than 4095 KB (approximately 4 MB) can only be sent to transactional queues. Please verify the queue is transactional, ...
  54. MessageType" property specifies the type of the BizTalk message. The message type is defined as a concatenation of document ...
  55. MessageType" property specifies the type of the BizTalk message. The message type is defined as a concatenation of document ...
  56. Messaging consists of the connection points used by this application. This includes Receive Ports, Receive Locations, Send ...
  57. Method invocation to deploy or undeploy failed. Details: {0}. Resolve the issue that is causing the exception, and then retry ...
  58. Method invocation to retrieve metadata failed. Details: {0}. Resolve the issue that is causing the exception, and then retry ...
  59. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the U.S. and/or other countries. ...
  60. Microsoft BizTalk RFID could not find a version for the specified device. Try deleting and re-adding the device, and then ...
  61. Microsoft BizTalk RFID failed to set {0} as the current directory. Verify if the directory containing the service executable ...
  62. Microsoft BizTalk RFID filtered an event log message with category identifier %1 and instance identifier %2 because the number ...
  63. Microsoft BizTalk RFID has encountered an internal error because AppGlobals has not been initialized in this current application ...
  64. Microsoft BizTalk RFID has encountered an internal error because the RfidApplicationUtilities has not been initialized with ...
  65. Microsoft BizTalk RFID has encountered an internal error while trying to perform the specified operation. For more information, ...
  66. Microsoft BizTalk RFID has encountered an internal error. An attempt was made to initialize an already initialized worker ...
  67. Microsoft BizTalk RFID has encountered an internal error. SendMessage was called for a provider which was hosted out of process. ...
  68. Microsoft BizTalk RFID has encountered an internal error. The binding for the process {0} could not be serialized to be saved ...
  69. Microsoft BizTalk RFID has encountered an internal error. The binding of the process {0} is in a corrupted state in the RFID ...
  70. Microsoft BizTalk RFID has encountered an internal error. The database factory type {0} is not implemented. Contact Microsoft ...
  71. Microsoft BizTalk RFID has encountered an internal error. The device or process {0} could not be serialized to be saved to ...
  72. Microsoft BizTalk RFID has encountered an internal error. The hosting configuration was not in the initialized state while ...
  73. Microsoft BizTalk RFID has encountered an internal error. The local device marshaller can have a remote identifier only when ...
  74. Microsoft BizTalk RFID has encountered an internal error. The provider marshaller was not in an initialized state during ...
  75. Microsoft BizTalk RFID has encountered an internal error. The proxy that has been passed for the physical device is not of ...