Frequently Asked Questions
Q. What happens if the archive filename exceeds the maximum number of characters for a filename?
If the filename exceeds the maximum number of characters for a filename (as specificed by the Windows Operating System - currently 260), the archiving component will attempt to change the filename portion of the archive filename, by replacing everything before the extension with a GUID, and then archive the message to the archive directory. For example, if the filename is 'InventoryMessage1016-Customer9844526-20090607124400.xml', the component will change the filename to 'BB3465FB-03F6-4102-9D20-4FCD4E087CD4.xml' and save it to the directory specified in the Archive Directory property.
When the component makes this change, you will receive a warning message in the Windows Application Event Log with the following 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].
where [ARCHIVE FILE PATH] is the new filename that was created by the component in order to successfully archive the message. Further information regarding this warning message can be found at [LINK: Archive File Path Exceeded the Maximum Number of Characters].
Q. Can the Message Archiving Component archive a message with a 'body part' that is empty?
No, the component will not archive the message if the message body part is null or is empty. If the body part is null or empty, the component will pass the message straight to the next component in the pipeline without performing any processing on the message.
If the component detects a null or empty body part, you will receive an error message in the Windows Application Event Log with the following text:
Could not archive message (Message Id: [MESSAGE ID]) - the body part is null.
where [MESSAGE ID] is the BizTalk Message Id of the message that contained the null body part. The Message Id can be used to identify the message in the BizTalk Admin Console.
Q. How will the Message Archiving Component handle a missing Context Property?
If a macro is used in either the component's Archive Filename or Archive Directory properties that refers to a Context Property that does not exist in the message, the macro will be replaced with a GUID.
If the component cannot find the correct Context Property in the message, you will receive an error message in the Windows Application Event Log with the following 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]'.
where [MACRO NAME] refers to the macro name that could not be replaced; [GUID] refers to the new GUID that is used instead of the Context Property value.
If you encounter this problem, review the macros that you are using and ensure that the messages you are passing through that instance of the Message Archiving component contain the expected Content Properties - a full list of the available macros can be found at [LINK: Using Macros].
Q. What happens if an unsupported macro is used?
If an unsupported macro is used in either the component's Archive Filename or Archive Directory properties, the component will replace the macro with a GUID and archive the message with the new, GUID-based filename.
If the component cannot find the macro, you will receive an error message in the Windows Application Event Log with the following 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]'.
where [MACRO NAME] refers to the macro name that could not be found; [GUID] refers to the new GUID that is used to replace the unknown macro.
If you encounter this problem, review the macros that you are using and check spelling where appropriate - a full list of the available macros can be found at [LINK: Using Macros].
Q. Can the Message Archiving Component archive different parts of a message, other than the message body?
No, this is not possible in the current release of the Message Archiving Component, however this feature is planned for the next release. Please ensure that you content you wish to archive is contained within the message body part.
Q. I am receiving the error message "Failure to validate the component licence. Please contact the Support Team quoting error code 'LE128'.", what does this mean?
The licence installed on your system failed to validate. Please contact the Support Team at support@atomic-scope.com for more information.
Q. I am receiving the error message "Failure to validate the component licence. Please contact the Support Team quoting error code 'LE2048'.", what does this mean?
Please see above.