Memory is not sufficient error on Public Folder access
We have a Windows 2003 SBS running Exchange 2003 SP2.
When we try to open the Public Folders node in the Exchange System Manager the error message "The available memory is not sufficient..." "ID no: c10306a7" occures.
Strangly enough this happened suddenly overnight without us changing anything.
The server has 2.5 GB memory and has more than 2 GB memory available.
Anybody has a clue what happened?
October 8th, 2008 12:34pm
What service pack on the OS itself? Are there any additional details in the Application or System event log? How big is the page file? Can you try this from another user profile?
Free Windows Admin Tool Kit Click here and download it now
October 8th, 2008 3:44pm
Issue description: Got error when you try to open public folders on the ESM
The available memory is not sufficient. Close some applications or windows, and try again. ID no: c10306a7
Known resolution:
1. Check the setting of virtual directorya. In Exadmin virtual directory under HHTP Headers, below the custom headers, search for all other headers except for X-Powered-By: ASP.NET
b. If theres any headers except X-Powered-By: ASP.NET, backup IIS configuration, and then those headers
c. Restart the default website
2. Has IIS lockdown been installed on server? It will cause same issue
a. Go to IIS->Properties of default web site->ISAPI filters tab
b. See if urlscan has added
c. Search Oblt-log.log file on the server, see if you can locate it on hard drive. If yes, try to uninstall IIS lockdown, and check the issue again
You shall try to reproduce the issue, and check the error info from application log for further analysis if the above wouldnt work
References:
The Available Memory Is Not Sufficient Error Message When You Use Exchange 2000 Exchange System Manager to Manage Exchange Server 2003
October 9th, 2008 1:16pm
Hi, Wervis. How's the issue currently?
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2008 1:27pm
Hi, Wervis, I assume your question has been answered, and I'd like to change the status to "Marked as answer", please feel free to post here if you have any update
October 15th, 2008 1:20pm
Sorry i didn't answer earlier. Todayi checked the http-headers. There was also a secondheader (?) which i removed. I restarted IIS default website and it solved the problem. Thank you very much for your assitance!
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2008 4:53pm
Glad you solved it
October 21st, 2008 4:14am