Problem
When you try to download a message from the Tracked Message Events screen in BizTalk360, you may sometimes encounter the following error:
The Operations artifact corresponding to the input parameters was not found.
This error generally occurs when the required tracking data for the selected message instance is no longer available in the BizTalk Tracking Database.
You can also verify the issue from the BizTalk Server Administration Console. When you attempt to perform the same operation, you may see the following message:
The message was not found in the Message Box or the Tracking database. This may be caused by the following conditions:
(1) message tracking is not enabled;
(2) the message(s) is no longer referenced by a running or suspended service instance;
(3) the Message Box tracking tables have been automatically purged; or
(4) the SQL Server agent is not running on the Message Box servers."
Resolution
Follow the steps below to identify and resolve the issue.
1. Verify That Message Tracking Is Enabled
First, make sure that message body tracking and message property tracking are enabled for the required BizTalk artifacts.
You can enable or verify these settings using either:
BizTalk360 Tracking Manager
BizTalk Server Administration Console
2. Verify That SQL Server Agent Is Running
Make sure the SQL Server Agent service is running on the SQL Server instance that hosts the BizTalk databases.
The SQL Server Agent is required for various BizTalk Server database maintenance activities, including the scheduled purging of tracking data.
3. Verify That the Tracking Data Has Not Been Purged
Check whether the tracking data for the selected message is still available in the BizTalk Tracking Database.
BizTalk Server automatically purges tracking data based on the configured tracking and database maintenance settings. If the required tracking records have already been purged, the message cannot be downloaded from BizTalk360.
4. Verify the Message Instance Status
The message must still be referenced by a running or suspended service instance for it to be available for download.
If the message is no longer associated with a running or suspended service instance, BizTalk Server may not be able to retrieve the message from the Message Box or Tracking Database.
In such cases, the message cannot be saved or downloaded from the Tracked Message Events screen.
Another Possible Cause
BizTalk Server does not track messages that do not successfully pass through one of the configured tracking points.
For example, a message may be suspended because it is invalid, or because no host instance is configured to receive or process the message. In such scenarios, the message may be placed in the Suspended queue without being tracked.
If such a message is subsequently terminated, there may be no corresponding tracking record available in the Tracking Database.
As a result, BizTalk360 will not be able to retrieve or download the message from the Tracked Message Events screen.
Recommended Action
To ensure that messages can be retrieved when required, verify that the appropriate message body and message property tracking options are enabled.
You can configure these settings using either:
BizTalk360 → Administration → BizTalk Services → Tracking Manager
BizTalk Server Administration Console → Group Settings / Application Tracking
Also ensure that the SQL Server Agent is running and that tracking data is retained for the required period.
Note: If the message was never tracked or the corresponding tracking data has already been purged, enabling tracking afterward will not recover the historical message. Tracking must be enabled before the message is processed for the required tracking information to be available.