Select the product you need help with

You experience an OutOfMemory exception in Visual Studio when you open or close maps

Article ID: 840831 - View products that this article applies to.

SYMPTOMS

When you use Microsoft Visual Studio with a Microsoft BizTalk Server 2004 project that contains large maps, you may receive the following exception:

The following exception has occurred:
OutOfMemoryException: Out of memory.

Back to the top | Give Feedback

To 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.

   Date        Time    Version     Size       File name
   ------------------------------------------------------------------------------------------
   22-Apr-2004  22:37  3.0.5287.0    676,864  Btsxmltools.dll
   22-Apr-2004  23:02  3.0.5287.0    221,184  Microsoft.biztalk.artifactbrowser.dll
   22-Apr-2004  23:02  3.0.5287.0    274,432  Microsoft.biztalk.basefunctoids.dll
   22-Apr-2004  23:02  3.0.5287.0     45,056  Microsoft.biztalk.crossreferencing.dll
   22-Apr-2004  23:02  3.0.5287.0     40,960  Microsoft.biztalk.crossreferencingfunctoids.dll
   22-Apr-2004  23:02  3.0.5287.0    249,856  Microsoft.biztalk.mapper.dll
   22-Apr-2004  23:02  3.0.5287.0  1,114,112  Microsoft.biztalk.tom.dll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in BizTalk Server 2004 Service Pack 1.

Back to the top | Give Feedback