FIX: "Error: fail to regenerate views" error when you run a BAM_DM_<activity_name> BAM SSIS package in BizTalk Server

Symptoms

Consider the following scenario:

You have a computer that is running Microsoft BizTalk Server 2006 R2, Microsoft BizTalk Server 2009 or Microsoft BizTalk Server 2010.
You create and deploy a Business Activity Monitoring (BAM) activity that has a name longer than 29 characters.

For example, the BAM activity name is longer than 36 characters.
You create and apply a tracking profile to link the BAM activity definition.
You run BizTalk Server so that the BAM data is written to the BAM activity.
You run the BAM_DM_<activity_name>Microsoft SQL Server Integration Services (SSIS) package that archives the data from the BAMPrimaryImport database to the BAMArchive database.

In this scenario, the SSIS package does not run, and you receive the following error message:

Error: fail to regenerate views.
Msg 50000, Level 16, State 1, Procedure bam_Metadata_SpawnPartition, Line 206
SpawnPartition_FailToRegenerateViews

Cause

This issue occurs because of an error in the bam_Metadata_SpawnPartition stored procedure.

When you try to run the SSIS package to achieve the data, the stored procedure does not run if a BAM activity has a name that is 48 or more characters long. However, the bam_Metadata_SpawnPartition stored procedure has an error. Therefore, the stored procedure might not run even if the name is within the limit.

Note For more information about BAM infrastructure limits, visit the following MSDN website:

General information about BAM infrastructure limits

Resolution

Cumulative update information

BizTalk Server 2006 R2

The hotfix that resolves this issue is included in cumulative update package 4 for BizTalk Server 2006 R2 SP1.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2682056 Cumulative update package 4 for BizTalk Server 2006 R2 SP1

BizTalk Server 2009

The hotfix that resolves this issue is included in cumulative update package 5 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2649852Cumulative update package 5 for BizTalk Server 2009

BizTalk Server 2010

The hotfix that resolves this issue is included in cumulative update package 1 for BizTalk Server 2010.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2497789 Cumulative update package 1 for BizTalk Server 2010
Note To resolve this issue in BizTalk Server 2010, apply cumulative update package 1 for BizTalk Server 2010. A hotfix package is currently not available for BizTalk Server 2006 R2. To work around this issue in BizTalk Server 2006 R2, see the "Workaround" section.

Workaround

To work around this issue, shorten the length of the BAM activity name to 29 or less characters, and then redeploy the BAM activity.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

For more information about how to manage BAM, visit the following MSDN website:

How to manage BAMFor more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk Server hotfixes