Article ID: 933396 - Last Review: October 25, 2007 - Revision: 1.2 FIX: You may receive a NullReferenceException error message when a long-running XLANG orchestration is rehydrated in BizTalk Server 2004
On This PageSYMPTOMSIn Microsoft BizTalk Server 2004, when a long-running XLANG orchestration is rehydrated, you may receive a NullReferenceException error message. Additionally, the following error message may be logged in the event log: An error has occurred that requires the BizTalk service to terminate. The most common causes are an unexpected out of memory error and an inability to connect or a loss of connectivity to one of the BizTalk databases. The service will shutdown and auto-restart in 1 minute. If the problematic database remains unavailable, this cycle will repeat. Error message: Object reference not set to an instance of an object. Error source: Microsoft.XLANGs.BizTalk.Engine BizTalk host name: BizTalkServerApplication Windows service name: BTSSvc{12345678-9012-420F-BA54-67FDC55A63E1} CAUSEThis problem occurs because changes to internal objects in serialized orchestrations occur after you install hotfix 918758 or BizTalk Server 2004 Service Pack 2 (SP2). When an orchestration is serialized before you install these updates, and then the orchestration is deserialized, the orchestration fails, and a NullReferenceException failure occurs in XLANG. RESOLUTIONHotfix 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 this specific problem. 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 Web site: http://support.microsoft.com/contactus/?ws=support
(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.PrerequisitesYou must have Microsoft BizTalk server 2004 with SP 2 installed to apply this hotfix.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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 table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates REFERENCES
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
918758
(http://support.microsoft.com/kb/918758/
)
FIX: An orchestration may stop responding and the message status is "Delivered Not Consumed" in BizTalk Server 2004
924007
(http://support.microsoft.com/kb/924007/
)
FIX: A SQL Server transaction log may unexpectedly grow very large after you install BizTalk Server 2004 Service Pack 1
| Article Translations
|

Back to the top
