Knowledge Base: Error Messages
The following Error Event Log messages can be raised by the BizTalk Message Archiving Pipeline Component in the Windows Application Event Log:
Licence Key Validation
1. Failed to Read Licence Keys from the Registry - Error Message (Event Log Category Id: 1040)
Message text: Failed to read licence keys from the Registry - the component licence cannot be validated. The message been passed to the next stage in the pipeline and not archived. Error: [ERROR MESSAGE].
This error message is raised if the component cannot retrieve either the Validation Code or Licence Key from the Registry. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Repair the installation via Add/Remove Programs. If you are using an Enterprise Licence on a production system, you will need to re-activate the Enterprise Licence Key; Repairing the installation will revert the licence key held in the Registry back to the default Developer Licence Key which is not valid for production systems. If you still encounter this problem, e-mail full details of the Event Log message, including the text conatined within [ERROR MESSAGE] to support@atomic-scope.com.
2. Unable to Validate the Component Licence - Error Message (Event Log Category Id: 1050)
Message text: Unable to validate the component licence. Please contact the Support Team quoting error code '[LICENCING ERROR CODE]'.
This error message is raised if the component fails to validate the Licence Key. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Repair the installation via Add/Remove Programs. If you are using an Enterprise Licence on a production system, you will need to re-activate the Enterprise Licence Key; Repairing the installationwill revert the licence key held in the Registry back to the default Developer Licence Key which is not valid for production systems. If you are still experiencing the same issue, please contact Support at support@atomic-scope.com quoting the licencing error code.
3. General Failure Validating the Component Licence - Error Message (Event Log Category Id: 1060)
Message text: General failure validating component licence. Please contact the Support Team for assistance in resolving this issue. Error: [ERROR MESSAGE]..
This error message is raised if a general error is encountered validating the Licence Key. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Repair the installation via Add/Remove Programs. If you are using an Enterprise Licence on a production system, you will need to re-activate the Enterprise Licence Key; Repairing the installationwill revert the licence key held in the Registry back to the default Developer Licence Key which is not valid for production systems. If you still encounter this problem, e-mail full details of the Event Log message, including the text conatined within [ERROR MESSAGE] to support@atomic-scope.com.
Component Property Validation
4. Archive Directory Component Property not Configured - Error Message (Event Log Category Id: 2010)
Message text: The Archive Directory component property was not configured. As a result, the message has not been archived but has been passed to the next stage in the pipeline. Please provide a valid Archive Directory for the component.
This error message is raised when the component validates the property configuration you have provided. If the Archive Directory property is null or an empty string, the component cannot archive messages. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Review the component's Archive Directory property and provide a valid directory, including macros where necessary. Further information on configuring macros for this property can be found in the online documentation at NEED-TO-CHANGE.
5. Archive Filename Component Property not Configured - Error Message (Event Log Category Id: 2020)
Message text: The Archive Filename component property was not configured. As a result, the message has not been archived but has been passed to the next stage in the pipeline. Please provide a valid Archive Filename for the component.
This error message is raised when the component validates the property configuration you have provided. If the Archive Filename property is null or an empty string, the component cannot archive messages. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Review the component's Archive Filename property and provide a valid filename, including macros where necessary. Further information on configuring macros for this property can be found in the online documentation at NEED-TO-CHANGE.
6. Macro Identifier Count Mismatch - Error Message (Event Log Category Id: 3010)
Message text: The Archive Directory/Filename component property contain an incorrect number of macro identification characters ('%'). The message has not been archived, but has been passed to the next stage in the pipeline. Please update this property on the component configuration.
This error message is raised if the number of macro identification characters (the percentage symbol) is incorrect in either of the component's Archive Directory or Archive Filename properties. When evaluating the macros specified in the configuration, the component validates the number of macro identification characters specified, where there is an un-even number, this error message is raised. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Review the component properties Archive Directory and Archive Filename to ensure that you are using the correct number of macro identification characters. Further information on configuring macros in these two properties can be found in the online documentation at NEED-TO-CHANGE.
Component Operations
7. Could Not Archive Message, Body Part is Null - Error Message (Event Log Category Id: 4010)
Message text: Could not archive message (Message Id: [MESSAGE ID]) - the body part is null.
This error message is raised if the component detects that the BizTalk message passing through the pipeline has a null body part; the component will not attempt to archive a null message body as there is no data to archive. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: Ensure that the messages you are passing into BizTalk that move through a pipeline configured with the Message Archiving component have content in their message body. [MESSAGE ID] is the BizTalk Message Id that can be used to identify the message in the BizTalk Administration Console to resolve the issue.
8. Failed to Write Archive File - Error Message (Event Log Category Id: 7010)
Message text: Failed to write the archive message to disk. [ERROR MESSAGE].
This error message is raised if the component is unable to write the archive file to disk. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: [ERROR MESSAGE] will detail the full name of the archive file that the component is trying to write. Review the directory permissions and ensure that the BizTalk Host Instance user has suficient permissions to write a file at that location.
9. Failed to Create Archive Directory - Error Message (Event Log Category Id: 8010)
Message text: The archive directory could not be created - the message has not been archived. [ERROR MESSAGE].
This error message is raised if the component is unable to create the archive directory. As a result, the message is passed straight to the next component in the pipline and the BizTalk message is not archived.
Resolution: [ERROR MESSAGE] will detail the full name of the directory that the component is trying to create. Review the directory permissions and ensure that the BizTalk Host Instance user has suficient permissions to write a file at that location.