FIX: Error message when you view the EDI Batching Report in BizTalk Server 2006 R2: "This operation failed while accessing at least one of the Message Box databases"

Article translations Article translations
Article ID: 970292 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft BizTalk Server 2006 R2, you view a Batch Status report in the EDI Status Reports section on the Group Hub page of the BizTalk Server Administration console. However, when you do this, you receive an error that resembles the following:

This operation failed while accessing at least one of the Message Box databases. Some results might be omitted.

Additional information:
Specified cast is not valid. (Microsoft.BizTalk.Administration.StatusReports)

This problem usually occurs when the following conditions are true:
  • In the EDI Properties for the Party of Edifact Properties under Party as Interchange Receiver, you changed the Interchange Batch Creation Settings field from Schedule to another release criterion.
    Note For more information about how to configure these settings, see the More Information section.
  • The computer is set to a time zone that is ahead of GMT.

CAUSE

In BizTalk Server, Business Activity Monitoring (BAM) activities are created to track EDI messages for EDI status reporting. These activities are included as views in the BAMPrimaryImport database.

Note For more information about BAM activities, see the More Information section.

When the fields for these EDI BAM activities are populated, only the relevant fields for the event are populated. This occurs because the Interchange Batch Creation Settings setting is not set to Schedule when BizTalk Server populates the ScheduledReleaseTime field. To populate certain empty fields, BizTalk Server uses the SqlDateTime.MinValue, which has a value of 01/01/1753 00:00. Then, BizTalk Server converts this value to UTC time.

If the computer is set to a time zone that is ahead of in GMT, when the value is converted to UTC, it becomes a time earlier than 01/01/1753 00:00. However, this value is not accepted by Microsoft SQL Server and the EDI Batching report does not work as expected.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, you have to restart BizTalk Server service after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.biztalk.edi.batchinghelper.dll3.6.1521.287,93616-Apr-200911:01x86
Microsoft.biztalk.edi.reporting.dll3.6.1521.259,24816-Apr-200911:01x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.Note After you apply this hotfix, BizTalk populates null values for irrelevant datetime fields.

STATUS

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

MORE INFORMATION

For more information about how to monitor EDI and AS2 solutions, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd745656.aspx

For more information about how to configure EDIFACT interchange batch creation settings, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd760964.aspx

For more information about how to create BAM activities to track EDI/AS2 messages, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/dd745126.aspx For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 970292 - Last Review: June 18, 2009 - Revision: 1.1
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Branch Edition
Keywords: 
kbbiztalk2006r2sp1fix kbbtsadapters kbautohotfix kbexpertiseinter kbfix kbhotfixserver kbqfe KB970292

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com