BizTalk Server 2010

  1. String value indicating the configuration of the assembly, such as Development or Deployment. The runtime does not use this ...
  2. String value indicating the name of the file that contains either the public key (if using delay signing) or both the public ...
  3. String value specifying a default alias to be used by referencing assemblies. This value provides a friendly name when the ...
  4. Strong name of the BizTalk assembly for which to export the binding file. If this argument is supplied, you do not need to ...
  5. Structural error encountered during serialization of an Interchange Xml message. While looking for Xml StartElement {0} or ...
  6. Subscriptions can be used to track data changes in UDDI registry. The types of data that can be subscribed include providers, ...
  7. Summary of adapter handler configuration. Some adapter handlers (like SMTP) might not have a default configuration and need ...
  8. Suspend request could not be sent for one or more of the specified instances. The instances might not exist in any of the ...
  9. Suspend request could not be sent for the specified instance. The instance might not exist in any of the MessageBoxes, or ...
  10. Suspend request for the selected service instance(s) has been submitted successfully. Please refresh the query page to see ...
  11. System columns ActivityID NVARCHAR(128) PRIMARY KEY NOT NULL, IsVisible BIT DEFAULT(NULL), IsComplete BIT DEFAULT(NULL), ...
  12. Tags displayed here are obtained directly from the device. Only tags that have no pass code information are displayed here. ...
  13. Tags that processes receive are displayed here. To refresh the view manually, click Refresh. To automatically update the ...
  14. Terminate request could not be sent for one or more of the specified instances. The instances might not exist in any of the ...
  15. Terminate request could not be sent for the specified instance. The instance might not exist in any of the MessageBoxes, ...
  16. Terminate request for the selected service instance(s) has been submitted successfully. Please refresh the query page to ...
  17. TEXT_TAXONOMY_UNHOSTED_TMODELS=The following tModels have been classified as categorization schemes although UDDI Services ...
  18. Thank you for evaluating %1. The period for evaluating this product has ended. Please contact Microsoft for information about ...
  19. Thank you for evaluating %1. The period for evaluating this product will end in %2!d! day(s). Please contact Microsoft for ...
  20. The "%1" delimited record does not have a child. Records with no tag identifier must have at least one child, or else the ...
  21. The "%1" delimited record is marked to repeat but it does not have a tag identifier. Only the last record in a document specification ...
  22. The "%1" document contains a reference to a specification that does not contain a top-level"%2" element definition. Please ...
  23. The "%1" positional record has a record length of zero defined. This happens when there is no tag, and none of the record's ...
  24. The "%1" record contains an illegal cyclic path through the "%2" record. A record can have cyclic references only if it has ...
  25. The "GeneratorServerName","ProviderServerName", and "DistributorServerName" properties for deployment unit "Alerts" cannot ...
  26. The "{0}" Windows SharePoint Services column is also set by property {1}. Remove one of the duplicate names to address this ...
  27. The %1 feature on this machine does not match to the configuration in the BizTalk Group that you are joining. You need to ...
  28. The '{0}' macro in '{1}' field is not supported in message context properties. For instance, an expression such as msg(WSS.Filename) ...
  29. The '{0}' macro is not supported in message context properties. For instance, expressions such as msg(WSS.Filename) = "MyLiteral-{0}" ...
  30. The @nvcFolder parameter cannot be null. If you want to only purge the database, use the dtasp_PurgeTrackingDatabase stored ...
  31. The abbreviation is invalid. The valid values are: {CR} {LF} {TAB} {SPACE} {0xnnnn} - hexadecimal value of the character. ...
  32. The access codes that were provided do not match. Ensure that the values provided in Access Code and Confirm Access Code ...
  33. The account you specified has administrative privileges on this computer. This may pose a security risk. Are you sure you ...
  34. The account you specified has administrator privileges on this computer. To make your system more secure by limiting access ...
  35. The action could not be performed on the application because the application was not empty. Unregister all services associated ...
  36. The adapter cannot operate correctly if this COM+ application is not created. To complete the setup of the adapter, the COM+ ...
  37. The adapter configuration URI is %1 but the Adapter Framework contains %2. There is a possible corruption in the configuration. ...
  38. The adapter failed to send the message to the send port "%1". It will be resent after the retry interval specified for this ...
  39. The adapter failed to transmit message going to send port "%1" with URL "%2". It will be retransmitted after the retry interval ...
  40. The administrator requested an instance operation that could not be performed because the instance is locked by another process. ...
  41. The Advanced option allows you to select an existing Correlation Type for the Correlation Set you are configuring. A Correlation ...
  42. The annotation information for version {0}, track point {1} does not exist. Try re-deploying via Tracking Profile Editor. ...
  43. The application base for provider {0} could not be deleted because of {1}. Try removing this directory manually after unregistering. ...
  44. The application domain for the process engine is being unloaded without the process being stopped. Process name: {0}, sender: ...
  45. The application identity will be set to the following account. Components in the application will run under this account. ...
  46. The application name in the bindings file and group do not match. Do you want to import the bindings into this application? ...
  47. The application name specified in the binding file ({0}) does not match the name of the application ({1}) into which the ...
  48. The application root {0} is either not a directory or the service has insufficient permissions to access it. Verify if the ...
  49. The application specified in the bindings file does not exist. Please create the application first and then import bindings. ...
  50. The application was successfully imported to the group . Note that this application depends on the following applications ...
  51. The application {0} was successfully exported to the file {1}. To deploy this application to another environment, you must ...
  52. The AS2 Decoder encountered an exception during processing. Details of the message and exception are as follows: AS2-From:"{0}" ...
  53. The AS2 Decoder encountered an exception during processing. Details of the message and exception are as follows: AS2-From:"{0}" ...
  54. The AS2 Decoder failed processing when validating the MIC value returned in the MDN. Details of the MDN message are as follows: ...
  55. The AS2 Decoder failed processing when validating the MIC value returned in the MDN. Details of the MDN message are as follows: ...
  56. The AS2 Decoder failure processing because the MDN indicated the AS2 message failed processing. Details of the MDN message ...
  57. The AS2 Decoder failure processing because the MDN indicated the AS2 message failed processing. Details of the MDN message ...
  58. The AS2 Decoder failure processing because the MDN signing did not match our request. Details of the MDN message are as follows: ...
  59. The AS2 Decoder failure processing because the MDN signing did not match our request. Details of the MDN message are as follows: ...
  60. The AS2 Decoder was unable to locate the Disposition-Notification-Options HTTP header which is required for MDN generation. ...
  61. The assembly does not contain any web service proxy types. Assembly should contain at least one public type derived from ...
  62. The assembly name {0} could not be parsed. Reason: {1}. For details on resolving the issue, refer to the AssemblyName class ...
  63. The attempt to connect to device %1 failed continuously %2 time(s). The error message for the last failure is: %3. This device ...
  64. The attempt to initialize the SQL Server Sink event handler from the specified parameter list failed. Verify if the event ...
  65. The authentication information for the worker process account was not found in the RFID store. Try repairing your installation ...
  66. The BAM Interceptor detected the following error : In host process '{0}', connection string to BAM Primary Import Database ...
  67. The BAM Interceptor detected the following error : In host process '{0}', for EventSource '{1}' OnEvent '{2}' BAM activity ...
  68. The BAM Interceptor detected the following error : In host process '{0}', for EventSource '{1}' OnEvent '{2}' BAM activity ...
  69. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  70. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  71. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  72. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  73. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  74. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for EventSource '{1}' ...
  75. The BAM Interceptor detected the following error : In host process '{0}', interceptor configuration for technology '{1}' ...