What you should check is whether View History for 'MessageBox_Message_Cleanup_BizTalkMsgBoxDb' is showing success every minute. The ManageRefCountLog log job internally calls the Message_Cleanup job, so if Job history for MessageBox_Message_Cleanup_BizTalkMsgBoxDb
is appearing every minute, the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb job is running fine as well. In this case, you can ignore the error you are seeing in history of ManageRefCountLog - it's an old entry and not failing at the moment.
Snippet from Microsoft for your understanding: https://docs.microsoft.com/en-us/troubleshoot/biztalk/sql-server-agent-jobs-biztalk
MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb job runs in an infinite loop and deletes the entries from the two individual message reference count logs. This job also calls the MessageBox_Message_Cleanup_BizTalkMsgBoxDb job.
Important At first, the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb job status icon displays a status of Success. However, there will be no corresponding success entry in the job history.
If one of the jobs in the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb
job fails, a failure entry appears in the job history and the status icon displays a status of Failure. The job will always display a status of Failure after the first failure. To verify that the other BizTalk Server SQL Server Agent jobs run correctly,
check the status of the other BizTalk Server SQL Server Agent jobs.
Rachit Sikroria (Microsoft Azure MVP)
