Recently I have not been able to open an asp.net page in MDE's web from
designer. I recieve the following error:
"The file failed to load in the web from designer. Please correct the
following error, then load again: Not enough storage is available to
complete this operation".
I have found several articles regarding remote debugging when I search for "Not Enough Storage". I have no issues with compiling and running this app in debug mode. I only get this message when trying to open the aspx page with the web from designer. After the error message it gives me the HTML instead of the drag drop interface.
I have 54Gigs of free space and a gig of ram. Rebooting has not helped.
This is the GUI portion of a web project that is spilt into a DAL, BLL and
GUI that is in source safe.
I am runnint Micrsoft Development Environment 2002 Verison 7.0.9466
Micrsoft .NET framework 1.0 Version 1.0.3705
SysInfo With Visual Studio and the project open:
Total Physical Memory 1,024.00 MB
Available Physical Memory 543.21 MB
Total Virtual Memory 4.90 GB
Available Virtual Memory 3.97 GB
Page File Space 3.90 GB
Sys Info After trying to open Web Form Designer:
Total Physical Memory 1,024.00 MB
Available Physical Memory 89.13 MB
Total Virtual Memory 4.90 GB
Available Virtual Memory 2.97 GB
Page File Space 3.90 GB
Any suggestions would be appricated.
Thanks for your time,
MarkA Microsoft Support Enginner covered this error message. Here's her response:
According to this error, you may be running out of virtual memory though I
don't know how this option is set on your server. You can use Performance
Monitor to determine what resources are being used. For more information on
how to set Max Server Memory option affecting MSSearch, you can refer to
Microsoft SQL Server Books Online with the keyword 'Server Memory Options'
as the search topic.
If you have installed and are running the Full-Text Search support, then
you must set the max server memory option manually to leave enough memory
for the MSSearch service to run. Ideally, you want to allocate as much
memory as possible to SQL Server without causing the system to swap pages
to disk. As you increase the amount of SQL Server memory, ensure that there
is sufficient disk space to grow the operating system's virtual memory
support file (Pagefile.sys) to accommodate additional memory. For
information about the virtual memory support file, see your Windows NT
documentation. The amount of memory specified must be sufficient for the
SQL Server static memory needs (kernel overhead, open objects, locks, and
so on), as well as for the data cache (also called buffer cache). Use
statistics from Windows NT Performance Monitor to help you adjust the
memory value if necessary. Change this value only when you add or remove
memory, or when you change how you use your system.
Please download the Component Checker under
http://www.microsoft.com/data
to check MDAC version. You can apply the latest MDAC version on your server
and try again.
Which makes sense, since even though you have a Gig of RAM, your available RAM is only 89MB!! Something is hogging the memory.
Thanks for the quick response. The SQL server is running on a different box, but I think I might have lead you astray with something I might have written.
The error does not happen when I compile or run the app. The app and the compiler process runs like a champ.
I receive this error when I open up an ASPX page to edit it in Visual Stuido.Net web form designer. The physical memory usage goes though the roof and I receive the above error. Anyone know how opening the page in design mode would gobble up memory?
Mark
MS has some info on this. See if this helps:
If you see the below error messages while you are connecting to remote machine with ?Processes? dialog.
Error while trying to run project: Unable to start debugging on the web
server. Not enough storage is available to complete this operation.
Or, you see the below, during ASP.NET debugging.
Error while trying to run project: Unable to start debugging on the web
server. Unable to map the debug start page URL to a machine name.
Please make sure that RPC is working properly between your machine and the remote machine. the reason of RPC issue can be from
1. Debugging through a firewall. Microsoft does not recommend or support remote
ASP.Net debugging through a firewall. The best way to do overcome this is use
Terminal Services to log into the remote server and debug locally.
2. One common failure for RPC is the inability to resolve the remote machine
name. RPC relies on name resolution for communication between machines. If
you are unable to resolve the remote servers machine name to the correct IP
address errors may occur.
3. RPC Traffic can flow in one direction but not the other. RPC traffic must be
able to go from the machine used to do the debugging to the remote server and
from the remote server back to the machine used to do the debugging in order
to successfully debug remotely. Make sure that RPC communication is enabled
in both directions.
To analyze your RPC, you can use ?RPCPing? tool.
This doesn't happen when debugging and I'm not connected to a remote machine. This happens when in design mode I double click on an ASPX page to edit it in Visual Stuido.Net web form designer.
I found a couple of KB articles that sounded closer.
http://support.microsoft.com/default.aspx?scid=kb;en-us;317624
http://support.microsoft.com/default.aspx?scid=kb;en-us;324181
I contacted MS and received the hot fix but it would not install. The rep that sent the hotfix stated that we needed framework 1.0 SP2 installed first. DLed that and installed it, but get the same "Could not install Microsoft .NET Framework Hotfix (Q324181) message that we got before SP2.
One other bit of info that I discovered… We have 4 programmers in shop. The 2 that are having this issue as of Tuesday (4/6/2004) both have framework 1.0 and 1.1 installed. The other two programmers only have 1.0 and have no issues. We tried uninstalling 1.1 but it did not change the error message.
Thanks for your time,
Mark
No comments:
Post a Comment