BUG: The "Backup BizTalk Server" SQL job fails with an error because the adm_OtherBackupDatabases table is not created (839626)
The information in this article applies to:
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
SYMPTOMSWhen you try to run the Backup BizTalk
Server SQL job, the SQL job fails and you receive an error message that
is similar to the following in the application log of the Microsoft SQL
Server-based computer that houses your Microsoft BizTalk Server 2004
databases: Event Type: Warning Event Source:
SQLSERVERAGENT Event Category: Job Engine Event ID: 208 Date:
3/25/2004 Time: 11:43:48 AM User: N/A Computer:
SQLServer 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). For more information, see Help and Support
Center at http://support.microsoft.com. Note SQLServer is a placeholder for the name
of the SQL Server-based computer that houses your BizTalk Server 2004
databases. Additionally, when this error occurs, another error message
that is similar to the following error may appear in the job history for the Backup BizTalk Server job: Executed as user:
Domain\User. Invalid object name
'adm_OtherBackupDatabases'. [SQLSTATE 42S02] (Error 208) Warning: The table
'#catalogs' has been created but its maximum row size (8281) exceeds the
maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table
will fail if the resulting row length exceeds 8060 bytes. [SQLSTATE 01000]
(Error 1708) Associated statement is not prepared [SQLSTATE HY007] (Error 0)
Failed running sp_BackupAllFull [SQLSTATE 42000] (Error 50000). The step
failed. Note The Backup BizTalk Server job was executed under the context of an account.
Domain\User is a placeholder for the domain name and
the user name of this account. CAUSEThe Backup BizTalk Server SQL job fails if you elect not to install all the following
components when you install BizTalk Server 2004:
- Engine\Human Workflow Services Runtime Component
- Engine\Base EDI Adapter
- Rules Engine
- Administration Tools\Human Workflow Service Administration
Tools
- Information Worker Applications/Portal\Business Activity
Services
- Information Worker Applications/Portal\Human Workflow Web
Services
If you did not install any of these components, the
adm_OtherBackupDatabases table is not created in your BizTalk Management
database. This table must exist for the Backup BizTalk Server SQL job to run. RESOLUTIONTo resolve this problem, create the adm_OtherBackupDatabases
table on the SQL Server-based computer that houses your BizTalk Server 2004
databases. To do this, follow these steps:
- Start SQL Query Analyzer. To do this, click
Start, point to Programs, point to
Microsoft SQL Server, and then click Query
Analyzer.
- In the Connect to SQL Server dialog box,
type the name of the SQL Server-based computer that houses the BizTalk Server
databases, type the authentication information, and then click
OK.
- In the Databases list, click the BizTalk
Management database. By default, this database is named
BizTalkMgmtDb.
- Paste the SQL query that is listed below in the
Query window.
CREATE TABLE [dbo].[adm_OtherBackupDatabases] (
[DefaultDatabaseName] [nvarchar] (128) NOT NULL ,
[DatabaseName] [nvarchar] (128) NOT NULL ,
[ServerName] [nvarchar] (80) NOT NULL ,
[BTSServerName] [nvarchar] (80) NOT NULL
)
GO
ALTER TABLE [adm_OtherBackupDatabases] ADD CONSTRAINT
[adm_OtherBackupDatabases_PK] PRIMARY KEY ([DefaultDatabaseName], [BTSServerName])
GO - Run the query by pressing F5 or by clicking Execute
Query.
- Close the SQL Query Analyzer.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbBug kbfix KB839626 kbAudDeveloper |
---|
|