.NET Questions and Solutions

Symptoms
Memory leaks are a common issue. You may have to try several steps to find the specific cause of a memory leak or an out-of-memory (OOM) exception in Microsoft BizTalk Server. This article discusses important things to consider when you are evaluating memory usage and possible memory-related issues. These considerations include the following:
Physical RAM
Large message processing
Use of the /3GB switch
Use of custom components
Which version of the Microsoft .NET Framework the system is running
The number of processors
Resolution
This article describes how to troubleshoot a memory leak or an out-of-memory exception in the BizTalk Server process of Microsoft BizTalk Server.

Symptoms
In Microsoft BizTalk Server 2004, you may receive the following error message when you try to compile a large map:

Exception Caught: Object reference not set to an instance of an object.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751?(http://support.microsoft.com/kb/888751/) How to obtain the latest BizTalk Server 2004 service pack
Hotfix 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 tool in Control Panel.

DateTimeVersionSizeFile name——————————————————————————————01-Apr-200402:313.0.5267.0676,864Btsxmltools.dll01-Apr-200402:573.0.5267.0274,432Microsoft.biztalk.basefunctoids.dll01-Apr-200402:573.0.5267.045,056Microsoft.biztalk.crossreferencing.dll01-Apr-200402:573.0.5267.040,960Microsoft.biztalk.crossreferencingfunctoids.dll01-Apr-200402:573.0.5267.0249,856Microsoft.biztalk.mapper.dll01-Apr-200402:573.0.5267.01,114,112Microsoft.biztalk.tom.dll
NoteBecause of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Symptoms
Microsoft BizTalk Server 2004 may fail while it tries to persist the state of an running orchestration instance to the database and throws a PersistenceException exception. BizTalk Server ends the running orchestration instance and you may receive an error message that is similar to the following:

Uncaught exception terminated service MYAPP.MyOrchestration(f56f3586-8c07-f8c8-fedf-3ac47aef7816), instance 7f6901e9-da3d-4166-b3f8-0e57f5b579e6
Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
Help Link:
Additional error information:
A batch item failed persistence Item-ID de31a76d-8a6a-440e-8e00-422ba9602127 OperationType MAIO_CommitBatch Status -1061151992 ErrorInfo The operation could not be performed because the message on which it was acting was not found in the database. .
Exception type: PersistenceItem
ExceptionSource:
Target Site:
Help Link:
Additional error information:
A batch item failed persistence Item-ID 983fac93-bbe0-466a-bed9-e49e10ad6e57 OperationType MAIO_ReceiveCompleteMessage Status -1061151992 ErrorInfo The operation could not be performed because the message on which it was acting was not found in the database. .
Exception type: PersistenceItem
ExceptionSource:
Target Site:
Help Link:
Additional error information: Exception occurred when persisting state to the database.
Exception type: Persistence
ExceptionSource: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit(Microsoft.BizTalk.Agent.Interop.IBTMessageBatchEx[], Microsoft.XLANGs.Core.Segment, Microsoft.BizTalk.Agent.Interop.IBTOperationStatus ByRef)
Help Link:
Additional error information:
A batch item failed persistence Item-ID de31a76d-8a6a-440e-8e00-422ba9602127 OperationType MAIO_CommitBatch Status -1061151992 ErrorInfo The operation could not be performed because the message on which it was acting was not found in the database. .
Exception type: PersistenceItem
ExceptionSource:
Target Site:
Help Link:
Additional error information:
A batch item failed persistence Item-ID 983fac93-bbe0-466a-bed9-e49e10ad6e57 OperationType MAIO_ReceiveCompleteMessage Status -1061151992 ErrorInfo The operation could not be performed because the message on which it was acting was not found in the database. .
Exception type: PersistenceItem
ExceptionSource:
Target Site:
Help Link:
Additional error information
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751?(http://support.microsoft.com/kb/888751/) How to obtain the latest BizTalk Server 2004 service pack
Hotfix information
The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

DateTimeVersionSizeFile name—————————————————————————-14-Apr-200416:073.0.5278.0217,088Microsoft.xlangs.biztalk.engine.dll14-Apr-200415:563.0.5278.0114,688Microsoft.xlangs.runtimetypes.dllNoteBecause of file dependencies, the most recent hotfix that contains these files may also contain additional files.