Knowledge Base: Warning Messages
The following Warning Event Log messages can be raised by the BizTalk Message Archiving Pipeline Component in the Windows Application Event Log:
Component Operations
1. Macro Not Found - Warning Message (Event Log Category Id: 3020)
Message text: Please check that you are using the correct macro name in the pipeline component properties. The message will still be archived, however the macro '[MACRO NAME]' will be evaluated to '[GUID]'.
This warning message is raised if the macro [MACRO NAME] cannot be resolved. Where this is the case, the component will replace the macro with a GUID and archive the message.
Resolution: Review the macro you are using and ensure that it is a supported macro. A list of supported macros can be found in the online documentation at NEED-TO-CHANGE.
2. Context Property Not Found - Warning Message (Event Log Category Id: 5010)
Message text: The macro '[MACRO NAME]' evaluates to a Context Property that does not exist in the supplied message. Please check that you are using the correct macro name in the pipeline component properties. The message will still be archived, however the macro '[MACRO NAME]' will be evaluated to '[GUID]'.
This warning message is raised if the BizTalk message Context Property that the macro '[MACRO NAME]' refers to cannot be found in the message. For example, you are receiving a message over an FTP adapter, but you are using a macro which references a FILE adapter Context Property. Where this is the case, the component will replace the macro with a GUID and archive the message.
Resolution: Review the macro you are using and ensure that the messages passing through this instance of the Message Archiving Component contains the Context Property refered to in the macro. A list of supported macros and their corresponding Content Properties can be found in the online documentation at NEED-TO-CHANGE.
3. Empty Context Property - Warning Message (Event Log Category Id: 5020)
Message text: The macro '[MACRO NAME]' evaluates to a Context Property which does not contain any data. Please check that you are using the correct macro name in the pipeline component properties and that the message you are trying to archive contains the correct Context Property value. The message will still be archived, however the macro '[MACRO NAME]' will be evaluated to '[GUID]'.
This warning message is raised if the BizTalk message Context Property that the macro '[MACRO NAME]' refers to is present, but has not been populated (i.e. is NULL or an empty string). Where this is the case, the component will replace the macro with a GUID and archive the message.
Resolution: Review the macro you are using and ensure that the messages passing through this instance of the Message Archiving Component contains a Context Property that is populated. A list of supported macros and their corresponding Content Properties can be found in the online documentation at NEED-TO-CHANGE.
4. Archive File Path Exceeded the Maximum Number of Characters - Warning Message (Event Log Category Id: 6010)
Message text: After macro replacement, the full file path exceeded the operating system maximum length of 260 characters. The file has been saved to [ARCHIVE FILE PATH].
This warning message is raised if the archive file path exceeds the maximum number of characters for a filename (260 characters, as defined by the Windows operating system) after macro replacement had been completed. Where this is the case, the component will replace the filename with the BizTalk Message Id and append the original extention in an attempt to bring the filename under the maximum characters limit; the directory configured on the component will also be retained. [ARCHIVE FILE PATH] in the message text indicates the new filename that has been created.
Resolution: Review the macros you are using in the Archive Filename component property to reduce the filename of the archive message after macro replacement has been completed. For more information on the macros available, please see: NEED-TO-CHANGE.