When you try to back up the Microsoft Internet Security and Acceleration (ISA) Server configuration, or when you try to export the ISA Server configuration to a file, you experience the following symptoms:

•	The Exporting definitions progress bar in the Exporting ServerName to path.xml dialog box reaches approximately two-thirds of the way across the dialog box. Then, the export operation stops responding (hangs).
•	If you start Windows Task Manager, and then you click the Processes tab, you notice that Mmc.exe uses 50 percent or more of the CPU resources.
•	You receive the following message in the notification area: Windows - Virtual Memory Minimum Too Low Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.
•	You receive the following error message: ISA Server Error ISA Server cannot load the property page. There is not enough memory to complete the operation, close other programs, and then try again.

You experience these symptoms if you have a firewall rule that is linked to many large domain sets or to many large URL sets.

Back to the top

This problem occurs because of a memory management problem in the Microsoft XML Core Services 3.0 (MSXML 3.0) component. ISA Server 2004 and ISA Server 2006 use Microsoft XML Core Services 3.0 to translate the ISA Server data to an .xml file during an export operation. If you have a rule that is linked to many large domain sets or to many large URL sets, Microsoft XML Core Services 3.0 does not successfully translate the ISA Server configuration.

Back to the top

To resolve this problem, install an updated version of Microsoft XML Core Services 3.0. To obtain an updated version of Microsoft XML Core Services 3.0, visit the following Microsoft Web site:Note Microsoft Windows Server 2003 Service Pack 1(SP1) is not required to install this update. However, if you are running ISA Server 2004 on a Windows Server 2003-based computer, you must have Windows Server 2003 SP1 installed together with this update to resolve the problem that is mentioned in the "Symptoms" section.

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top