Help - FrontPage Bug: Ran out of memory while trying to allocate 0 bytes.

[Stewart Berman]

Windows XP Pro SP2
FrontPage 2000 SP3

Trying to publish web site to my machine. Most of the web site was copied down. Then I got:

 

[Rob Giordano \(Crash\)]

Probably a corrupt .web file, or cmdui.prf.

Search your hd for *.web and cmdui.prf and delete them.
or you can download the free FPCleaner utility by Steve Easton and run
that...
http://www.95isalive.com/fixes/fpclean.htm




| Windows XP Pro SP2
| FrontPage 2000 SP3
|
| Trying to publish web site to my machine. Most of the web site was copied
down. Then I got:
|
| ---------------------------
| Microsoft FrontPage
| ---------------------------
| Ran out of memory while trying to allocate 0 bytes.
| ---------------------------
| OK
| ---------------------------
|
| There isn't anything in the Microsoft Knowledge base (at least that I
could find) about this.
|
| Any work around would be appreciated.

 

[Ronx]

Download FP Cleaner from www.95isalive.com/fixes and run the "Clear
FrontPAge Web Cache Files" routine. This will delete any corrupt cache
files, which normally cause the error.
At the same time, also use the "Clear FrontPage Temporary Files" button.
These steps should be followed regularly.

 

[Kathleen Anderson [MVP - FrontPage]]

I agree. According to this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;278019 This
behavior is caused by a damaged Web server extensions cache file, which
causes all available hard disk space to be consumed by the swap file. The
article recommends deleting the .web files, which FPCleaner will do for you.

 

[Stewart Berman]

There appears to be some confusion. The hard drive I am downloading the web site to has 1.79 GB
free. It is not filling up. The C: drive on my machine has 18.69 GB free and is not filling up.

The error message is being issued by FrontPage and I suspect it is a bug in its memory handling
code. It seems to be trying to allocate 0 bytes of memory.

Just in case I downloaded FPCleaner and ran it and the problem still occurs.

 

[Stewart Berman]

There appears to be some confusion. The hard drive I am downloading the web site to has 1.79 GB
free. It is not filling up. The C: drive on my machine has 18.69 GB free and is not filling up.

The error message is being issued by FrontPage and I suspect it is a bug in its memory handling
code. It seems to be trying to allocate 0 bytes of memory.

Just in case I downloaded FPCleaner and ran it and the problem still occurs.

 

[Stewart Berman]

There appears to be some confusion. The hard drive I am downloading the web site to has 1.79 GB
free. It is not filling up. The C: drive on my machine has 18.69 GB free and is not filling up.

The error message is being issued by FrontPage and I suspect it is a bug in its memory handling
code. It seems to be trying to allocate 0 bytes of memory.

Just in case I downloaded FPCleaner and ran it and the problem still occurs.

 

[Stefan B Rusynko]

Try making sure you have cleaned up your hard drive (delete all IE TIF files, Temp files and your recycle bin, etc) before
publishing
Does the error occur also occur if you open your local (PC) site in FP and publish (Remote to Local)
- does it occur on a specific file?




| There appears to be some confusion. The hard drive I am downloading the web site to has 1.79 GB
| free. It is not filling up. The C: drive on my machine has 18.69 GB free and is not filling up.
|
| The error message is being issued by FrontPage and I suspect it is a bug in its memory handling
| code. It seems to be trying to allocate 0 bytes of memory.
|
| Just in case I downloaded FPCleaner and ran it and the problem still occurs.
|
|
|
| >Download FP Cleaner from www.95isalive.com/fixes and run the "Clear
| >FrontPAge Web Cache Files" routine. This will delete any corrupt cache
| >files, which normally cause the error.
| >At the same time, also use the "Clear FrontPage Temporary Files" button.
| >These steps should be followed regularly.
|

 

[Ronx]

There is no confusion. Memory has nothing to do with available disc space,
except when dealing with Virtual memory and the Windows Paging File which
could be filled as a result of this error. The paging file is normally
fixed in size in Windows XP, and can be filled.

In 99 out of a 100 cases the error you see is a result of a corrupted Web
Cache File, and deleting the cache files normally cures the problem.

 

[Stewart Berman]

I tracked it down to a 470 MB file. I deleted that from the web site I was downloading and
FrontPage downloaded the rest.

I have a recollection that when I originally uploaded that file to the web site I had to use FTP
instead of FrontPage as it could not handle it.

 

[Stewart Berman]

I tracked it down to a 470 MB file. I deleted that from the web site I was downloading and
FrontPage downloaded the rest.

I have a recollection that when I originally uploaded that file to the web site I had to use FTP
instead of FrontPage as it could not handle it.

 

[Stewart Berman]

I agree. According to this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;278019 This
behavior is caused by a damaged Web server extensions cache file, which
causes all available hard disk space to be consumed by the swap file. The
article recommends deleting the .web files, which FPCleaner will do for you.

 

[Stewart Berman]

I tracked it down to a 470 MB file. I deleted that from the web site I was downloading and
FrontPage downloaded the rest.

I have a recollection that when I originally uploaded that file to the web site I had to use FTP
instead of FrontPage as it could not handle it.

 

[Stefan B Rusynko]

Yes
- most servers have a 1MB limit set
If your host supports subwebs create a subweb (say media) in your rootweb and move all your media files over 1 MB into it
Then Publish your site again (w/o including subwebs)
Use a 3rd party FTP to transfer your large media files to that folder only and never open that subweb in FP

PS
Glad I am not going to your site
- a 470MB media file is a heck of a download even for broadband




|I tracked it down to a 470 MB file. I deleted that from the web site I was downloading and
| FrontPage downloaded the rest.
|
| I have a recollection that when I originally uploaded that file to the web site I had to use FTP
| instead of FrontPage as it could not handle it.
|
|
|
| >There is no confusion. Memory has nothing to do with available disc space,
| >except when dealing with Virtual memory and the Windows Paging File which
| >could be filled as a result of this error. The paging file is normally
| >fixed in size in Windows XP, and can be filled.
| >
| >In 99 out of a 100 cases the error you see is a result of a corrupted Web
| >Cache File, and deleting the cache files normally cures the problem.
|

 

[Stewart Berman]

I don't think this was a server limit. For one thing I was downloading to my local machine not
uploading to the server. For another, server limits usually result in a limit message or a
disconnect. This was a FrontPage error during memory allocation. It wasn't designed to handle
large files.

I think FrontPage has a number of limits due to its design and I wish someone would post a list of
them. I wasted a bit of time before I realized that it was a FrontPage bug.

Stu