Select the product you need help with
FIX: Error message when you run the DTA Purge and Archive job on a computer that has BizTalk Server 2006 R2 SP1 installed: "Invalid object name 'EdiMessageContent'. [SQLSTATE 42S02] (Error 208). The step failed."Article ID: 2499834 - View products that this article applies to. On This PageSYMPTOMSConsider the following scenario:
Date Date Log Job History (DTA Purge and Archive (BizTalkDTADb)) Step ID 1 Server LABSRV Job Name DTA Purge and Archive (BizTalkDTADb) Step Name Archive and Purge Duration 00:00:00 Sql Severity 16 Sql Message ID 208 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0 Message Executed as user: user. Invalid object name 'EdiMessageContent'. [SQLSTATE 42S02] (Error 208). The step failed. CAUSEThe issue occurs because the EDIMessageContent table is not created in the DTA database if you configure BizTalk Server 2006 R2 for the first time only after you install BizTalk Server 2006 R2 SP1. RESOLUTIONCumulative update informationThe 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
(http://support.microsoft.com/kb/2682056/
)
Cumulative update package 4 for BizTalk Server 2006 R2 SP1 Hotfix informationA 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.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, contact 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 website: 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesThe following list contains prerequisites for the hotfix package:
Restart requirementsYou do not have to restart the computer after you apply this hotfix.Replacement informationThis hotfix does not replace a previously released hotfix.File informationThe global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.For Microsoft BizTalk Server 2006 R2Collapse this table
WORKAROUNDTo work around this problem, use either of the following methods:
STATUSMicrosoft 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 BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: 2003907
(http://support.microsoft.com/kb/2003907/
)
Information about BizTalk Server hotfixes PropertiesArticle ID: 2499834 - Last Review: April 12, 2012 - Revision: 2.0 APPLIES TO
|
Back to the top
