Exchange/Outlook network problem

Its my experience that many of these unhelpful error messages come with an error code of some kind. Search for that error number in the KB.
Just a thought.

Just did a Usenet search at Google, and this error on Win98 machines was all over the place!
Unfortunately, no one had a solution.
It appears to happen when Win9x machines print to a network printer, run a DOS-based app, and get e-mail. I think I saw a dozen references to this error on Win9x machines.

The people posting this same error all said their NT/2000 clients do not get the error.
So, you can probably guess what I am gonna suggest: upgrade to WinNT/2K/XP. Whichever one.
It obviously is some kind of corruption of the IP stack. When it says "no space available on the server" it is not talking about the Exchange server; it is referrring to the Win9x client itself. But it is NOT a hard drive space issue.

Maybe if you upgradedto Win98 Second Edition. No one said 98SE did this (but then again, they didn't say it DIDN'T do it either!).

hope this gives you somewhere to start

Have seen this on some of our systems. Some users open resource hogging programs, open email, check something on the internet and are printing a word document at the same time. I believe its a RAM problem and the system has run out of resources with so many apps open at once. Solved my problem by adding RAM. Even if some of these programs are closed the problem persists because of memory leaks and the memory isn't released to be used so the system eventually chokes on what it is being askedto do. For some reason the system doesn't make sufficient use of virtual memory to relieve the problem. Easy way to check is to take memory from another system and temporarily add it's RAM to another system and set up same conditions under which the error occurrs and see what happens. Easy to do and doesn't cost anything to check it out.

I don?t see this error but personal I try to see if this is not a network access problem. Change patch cord or connect to other port/ HUB/ SWITCH the workstation with problems. Also maybe you need (if you don?t have) an UPS for network equipment?s or computers. Etc.

If you can narrow it down to just 95 clients that are exhibiting this behavior, try the Windows Sockets 2 update. Of course, if the 98 machines are doing the same, that won't be it.

How full is the drive on the exchange server that holds the priv.mdb file? That would be the first place to check. How much memory and space are in the machines? Outlook takes up a lot of virtual memory, MS recommeds setting page file at RAM + 100 just for outlook. You may want to manually control the page file on these machines. The Nic driver is also another possibility. When you said you thought it could be a corrupted stack, you said you saw no signs on the server, there wouldn't be anything on the server, the problem would be the machine with the error message, ie the client. So you might wasnt to try completley reinstalling the network setup on the client, ie the nic drivers and the tcp/ip stack. Is the OS up to date, if not download any patches from the windows update site.

What's your Service Pack/Service Release level on Exchange and Office 97? Don't know that SP4 or SR-2 would fix it, but the closest thing I've seen to the error you're getting is with NT4.0 networking and a "Not enough server storage is available to process this command" error when you do a post-install network setup, which is fixed by a service pack reapply to update srv.sys. If you're not already at the current level on Exchange Server and Office service packs, it might be worth a try.

This question was closed by the author