Where’s adm_OtherBackupDatabases then ?

Here’s an interesting BizTalk 2004 bug we came across today. Essentially, if you try to keep your BizTalk installation lean and choose not to install certain features, then the packaged backup jobs fail because of a missing table in the database. The actual error message in the event log reads:

Description: SQL Server Scheduled Job ‘Backup BizTalk Server’ (0x2CA1BE52A58C7045893DEC5F25FAAA6B) – Status: Failed – Invoked on: 2004-03-25 11:43:48 – Message: The job failed. The Job was invoked by User SA. The last step to run was step 1 (BackupFull). The job was requested to start at step 1 (BackupFull).

Which tells you that the job failed .. but finding out WHY is another matter. We started tracing through the code and figured out it was failing with an Invalid object name ‘adm_OtherBackupDatabases’ error message. Not finding a stored procedure or table with that name in BizTalkMgmtDb, I popped adm_OtherBackupDatabases term in Google and lo and behold, the first entry was an MSDN article about a known bug in BizTalk Server 2004.

Read more about it here: BUG: The “Backup BizTalk Server” SQL job fails with an error because the adm_OtherBackupDatabases table is not created

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.