The '{0}' macro in '{1}' field is not supported in message context properties. For instance, an expression such as msg(WSS.Filename) = "MyLiteral-{0}" or msg(WSS.ConfigPropertiesXml) = "" will generate an error. This macro is only supported in expressions defined on physical send ports or receive locations. ColumnOne {0}
The %1 application in the %2 site contains %3 web servers. Commerce Server 2002 Standard Edition allows a maximum of 2 web ...
The %1 feature on this machine does not match to the configuration in the BizTalk Group that you are joining. You need to ...
The %1 site contains too many applications. Commerce Server 2002 Standard Edition allows a maximum of 1 Bizdesk and 1 non-Bizdesk ...
The %1 Windows NT Service facilitates integration of Microsoft Office and Microsoft WIndows SharePoint Services with BizTalk ...
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 ...