BizTalk Server 2010

  1. The selected entity is part of a bigger entity that has already been signed. Deleting this digital signature will likely ...
  2. The selected entity is part of a bigger entity that has already been signed. Signing this entity will invalidate the signature ...
  3. The selected Excel file either does not exist or has no sheets in it. Specify an existing Excel file containing one or more ...
  4. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  5. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  6. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  7. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  8. The selected help topic is not available. This message typically appears when a custom installation of the product was performed ...
  9. The selected help topic is not available. This message typically appears when BizTalk Server documentation was not installed. ...
  10. The selected network adapter is not valid. Refer to the documentation for information about how to select a valid network ...
  11. The selector (XPath) that identifies the element or attribute field. The default is the field XPath obtained from the schema. ...
  12. The selector (XPath) that identifies the portion of interest in the XML document. The default is the instance XPath obtained ...
  13. The send adapter for this send port is not supported on 64-bit host instances. Please make sure that the send adapter is ...
  14. The send handler configuration for the Windows SharePoint Services adapter is invalid. The following error has been raised: ...
  15. The send port's transport types cannot be changed to or from MSMQT unless the send port is unenlisted. Please unenlist the ...
  16. The sequence number length for {0} should not exceed {1}. The specified values can lead to sequence numbers of length {2} ...
  17. The sequence starting with '\' is invalid. Use '\', '\{' or '\}' if you want to specify one of the symbols '\', '{' and '}' ...
  18. The serializer component cannot find a control number for %1 %2 in the BizTalk Management database. This document will be ...
  19. The serializer component failed to build the custom envelope ID:"%1". This was because of errors in the XML Schema supplied. ...
  20. The serializer component has encountered an invalid character, "%1". An entry specified in the InvalidCharacterMap tag of ...
  21. The serializer failed to create the custom envelope because the XML specification did not specify a Document Container Node ...
  22. The server "%1" is not a MSCS cluster node. In order to cluster a Host, all its BizTalk Host instances should be installed ...
  23. The Server and Client Tools feature contains Rfid Service, Client Console, Client Connector, Management Tools along with ...
  24. The server did not accept the current data protection level of the FTP connection. Verify the SSL settings on the FTPS server ...
  25. The server encountered a critical failure while trying to access the list of Views. The Business Management Web Service requires ...
  26. The server has not been configured. To configure the server, run the BizTalk Server Configuration wizard and configure the ...
  27. The server is unable to communicate with the UDDI Services database. Please contact your UDDI Services administrator to resolve ...
  28. The server name in the server certificate does not match with the name of the physical server. Make sure you provide the ...
  29. The server name or the database name was not specified. This could happen if default values are being used for these parameters ...
  30. The service could not automatically apply the nonpersistent properties from the version store for device %1 because of error ...
  31. The service could not automatically create a checkpoint version for device %1. Details: %2. If a checkpoint version is required, ...
  32. The service could not create a new device with name %1 and information %2 because of error %3 during device discovery. If ...
  33. The service could not decrypt the password for the device %1]. The device has been added in Unconfigured state. To enable ...
  34. The service could not validate the device information %1 reported by a provider for discovered device %2. The discovery event ...
  35. The service failed to save the state of device %1 to the RFID store. Details: %2. The service will retry saving the device ...
  36. The service instance was suspended because the corresponding service (orchestration, send port, .) was in the stopped state. ...
  37. The service received a discovery event with invalid arguments. This could be because the supplied event argument was null, ...
  38. The serviceKey associated with a service projection cannot be referenced in a subsequent serviceDetail that is not itself ...
  39. The set of business identities and additional identifiers derived from both sender and receiver parties that identify the ...
  40. The set of business identities and additional identifiers derived from both sender and receiver parties that identify the ...
  41. The Show method can be called only once on an ExceptionMessageBox object. To display a new message, you must create a new ...
  42. The size of the serialized event exceeded the maximum allowed limit of {0} bytes. The index of the event that caused this ...
  43. The SMTP send adapter could not authenticate with the SMTP server. Please check the SMTPHost and authentication information. ...
  44. The SMTP server rejected the "From" field value. If integrated Windows authentication is used, the "From" field should be ...
  45. The source identifier's "%1" qualifier is too long for the outbound document header. Please update the channel with a shorter ...
  46. The source information could not be retrieved. Verify whether the device is online. Sources that are present in the binding ...
  47. The source name for each TagReadEvent in a TagListEvent should either be null or should be the same as the source of the ...
  48. The specification referenced in the "%1" document is not compatible with the "%2" format. Select a specification that is ...
  49. The specified account is the Database Owner. The Database Owner always has access to the view and cannot be added to or removed ...
  50. The specified assembly name {0} of the component handler is not valid because it is either null or empty. Specify a valid ...
  51. The specified backup index is invalid. Specify a number that is greater than zero and less than the number of log files. ...
  52. The specified baud rate is different from the baud rate used by the device. Ensure that they are the same. You can change ...
  53. The specified Bluetooth address is not valid. Specify a valid address. A typical 48-bit Bluetooth address is in colon-delimited, ...
  54. The specified class name {0} of the component handler is not valid because it is either null or empty. Specify a valid name. ...
  55. The specified destination queue "%1" is non-transactional, and the message is being sent is transactional. Please check the ...
  56. The specified destination queue "%1" is transactional, and the message is being sent is non-transaction. Please check the ...
  57. The specified device group operation failed because it is not allowed on the root device group "{0}". Specify a valid device ...
  58. The specified device operation failed as the current number of configured devices in the RFID store is equal to or greater ...
  59. The specified device version is corrupted in the RFID store. Try deleting and re-adding the device, and then retry the operation. ...
  60. The specified device with handle {0} was not found in the hosted process. Restart the provider corresponding to this device, ...
  61. The specified domain does not exist or cannot be contacted. Please check your network connection or specify a domain that ...
  62. The specified encryption algorithm value is invalid. The following are valid values: 1) 0 for None 2) 26114 for Rc2 3) 26625 ...
  63. The specified event handler {0} does not derive from RfidEventHandlerBase. Event handler classes have to derive from RfidEventHandlerBase. ...
  64. The specified format is not supported for reading the messages from the journal queue of a private queue. Use the syntax: ...
  65. The specified format is not supported for reading the messages from the journal queue of a public queue. Use the syntax: ...
  66. The specified Government Managed Identifier is not valid because it contains one or more invalid characters. Specify a five ...
  67. The specified logical device {0} is not present in the RFID process. Specify a logical device that is present in the RFID ...
  68. The specified Management database already exists, and its database version is compatible with this installation. To re-use ...
  69. The specified Migration database is already initialized, do you want to delete all the existing data in the Migration database ...
  70. The specified name "{0}" is not valid because it is either empty or contains only whitespace characters. Specify a valid ...
  71. The specified name {0} is not valid because it contains the following invalid characters {1}. Names cannot contain \ / : ...
  72. The specified operation cannot be performed on process {0} because the process has not been started. Verify the latest state ...
  73. The specified operation could not be performed on device {0} as there is an open connection to this device from a client ...
  74. The specified operation could not be performed on device {0} because there is an open connection to this device. Close the ...
  75. The specified provider assembly {0} could not be loaded. Verify that the file exists, has read permissions, and is a valid ...