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