Microsoft Excel cannot open or save any more documents because there is not enough Memory or disk sp

  • Thread starter Thread starter BMS
  • Start date Start date
B

BMS

This error appears on a dual 2.4, 1gig RAM 64 gigs HD, machine when
the user load gets around 50 users. CPU practically idle, registry
size way under, swapfile way under, memory @ 25%. No power users mind
you, just Plain old Office apps and Outlook. At the same time this
occurs , Word is also only able to open files"Read-Only" . This
happens on all four servers in the farm each loaded from scratch, no
images.

Particulars:
Windows 2k Term Serv SP3
Office XP SP

Any help is greatly appreciated
 
Mmm, this is a rather common error and there are a large number of KB
article about this issue.
Are you running an antivirus program on these servers? Does turning
it of helps?

291178 - WD: Error Messages When You Attempt to Save a File, or Word
Stops Responding
http://support.microsoft.com/?kbid=291178
 
First thing I did was disable the Antivirus. Frustrated, I deinstalled
it, no change. I looked at KB291178, but that does not seem to be what
we're experiencing. Disk space is not the issue (10's of gigabytes are
available to the user) I must not be searching on it properly, because
I cannot seem to find but the tinyest bit of info on these errors.
Care to point me in the right direction?
Thanks
 
Do you have Office XP SP2 installed?

-M
-----Original Message-----
First thing I did was disable the Antivirus. Frustrated, I deinstalled
it, no change. I looked at KB291178, but that does not seem to be what
we're experiencing. Disk space is not the issue (10's of gigabytes are
available to the user) I must not be searching on it properly, because
I cannot seem to find but the tinyest bit of info on these errors.
Care to point me in the right direction?
Thanks



.
 
If you paste this URL into IE. you'll get 33 KB articles.

http://support.microsoft.com/search/default.aspx?
InCC_hdn=true&Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%
3DON&Product=offxp&Query=not+enough+memory&KeywordType=ALL&maxResu
lts=50

Most interesting ones seem to be:

214073 - XL: Error Message When You Try to Save a File
http://support.microsoft.com/?kbid=214073

286153 - Error Message: There Isn't Enough Disk Space or Memory
http://support.microsoft.com/?kbid=286153

297892 - OFFXP: Office Programs Require Virtual Memory
http://support.microsoft.com/?kbid=297892

But I would also consider this one, although it only mentions
Office 2000:

830065 - You Receive a “Microsoft Excel Cannot Open or Save Any
More Documents" Error Message When You Open or Save an Excel File
Through a Terminal Services Session
http://support.microsoft.com/?kbid=830065

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
 
I have the same problem and will be rebuilding the server over the christmas
holidays to fix it.

We seem to experience the issue when 18 sometimes 20 people are logged into
the server. And i have found 2 other programs besides Office that act
wierdly when that issue appears. (two of out accounting packages
crashes/wont load or say there is tyhe max number of users).

There is no reason it should complain there is ample memory and hdd space.
And i was told by somone that has similar issues and has MS PSS support that
MS has no idea whats going on.

Tim
 
I rebuilt the server over the christmas/new year holidays and had the same
issue so i tried the MaxMpxCt and MaxWorkItems settings but it still didnt
fix it, so i doubled the figures again leaving me with

MaxMpxCt: 0x33170
MaxWorkItems: 0x8192

After that i stress tested the server to 40 users with no major issues.

Those two keys are in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

that should be done on your domain controller only not the terminal server,
unless the TS is the DC as well, both keys are REG_DWORD. I cant remember
the MS KB article that shows that, but if the server is Pre windows 2000 sp2
(including nt4) there are issues with Win 9x machines.

I would advise you to find the KB article before doing anything anyway.

Tim
 
Back
Top