Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

There is not enough memory or disk space to complete the operation

2,760 views
Skip to first unread message

Bron...@officeformac.com

unread,
Jan 17, 2008, 9:41:03 AM1/17/08
to
I'm getting this error message when I try to open Word documents, when certain email messages try to load, and I'll probably get it for other functions as well.

I have over 20 gigs of free hard drive space, and 2gb of RAM.

Any ideas?

CyberTaz

unread,
Jan 17, 2008, 12:43:28 PM1/17/08
to
It would help to know which version of Word - especially now that 2008 has
started shipping - as well as which version of OS X... Specific levels on
each. Also, does it matter whether you double-click a file icon as opposed
to using File> Open from within Word?
--
Regards |:>)
Bob Jones
[MVP] Office:Mac

<Bron...@officeformac.com> wrote in message
news:ee88f...@webcrossing.caR9absDaxw...

Bron...@officeformac.com

unread,
Jan 17, 2008, 12:53:32 PM1/17/08
to
Sorry about that!

I'm referring to Office 2008.

I'm running OSX 10.5.1

Tried opening the doc using File>Open, with same results (not enough memory).

It does open some pre-2008 documents, but it's inconsistent for some reason. Also, I get the same error message with some emails, but not all.

Beth Rosengard

unread,
Jan 17, 2008, 3:06:08 PM1/17/08
to
Hi Bronx,

You need to reply to your *original* post and then enter the information below.  DO NOT CHANGE THE TITLE OF THE POST!  We have no easy way of telling what your problem was with a title like “More Info”.  Sorry.

--
***Please always reply to the newsgroup!***

Beth Rosengard
Mac MVP

Mac Word FAQ:  <http://word.mvps.org/Mac/WordMacHome.html>
My Site:  <http://www.bethrosengard.com>

John McGhie

unread,
Jan 18, 2008, 6:15:31 AM1/18/08
to
That's a very old error message. It actually means "Something I expected to
be in memory is not there". The error message dates back to the days when
the most likely cause of this error was that the user had run out of memory
or disk space.

These days, it normally means "something went wrong and caused a read or
write to disk or memory to fail".

Usually the thing that went wrong is that the document is corrupted, so Word
can't understand the code it has found, and thinks that either the disk or
memory read or write has failed.

When Word opens a file, it interprets the code inside it, then attempts to
sort the content into boxes in memory and lay the items out in tables in
memory. If the document is corrupted, it finds that something it is trying
to read or write won't fit in the table, and you get that message.

In your case, the cure is to open the file in the version of the application
that created it (if you can...) and de-corrupt it. To de-corrupt it, copy
all but the last paragraph mark, and paste it into a clean new document.

If you want to be really brave, you can start Word 2004, open the document,
copy all but the last paragraph mark, open Word 2008, create a blank
document, and paste. Just don't tell anyone I said you can do that, and if
you get a nasty hang of one or other programs, don't come crying to me :-)
You will get away with it most of the time :-)

WARNING: Don't allow two versions of Entourage to run side-by-side. All
hell will break loose, and you may be unable to read any of your mail
afterwards. Were you listening? DON'T run two versions of Entourage, you
WILL break your mailbox!!!

Hope this helps


On 18/01/08 12:11 AM, in article ee88f...@webcrossing.caR9absDaxw,
"Bron...@officeformac.com" <Bron...@officeformac.com> wrote:

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia
+61 4 1209 1410, mailto:jo...@mcghie.name

hasitha.go...@gmail.com

unread,
Oct 17, 2013, 8:24:28 PM10/17/13
to
http://support.microsoft.com/kb/980616

This was my fix.
Bastian
0 new messages