I woke up before the birds this morning and decided to try and solve this Outlook error 0x800CCC0F once and for all.
I am running my own mailserver. Unfortunately I have experienced this error for *years* now.
I have read most of the posts in this forum and numerous links in Google and so far I have not seen anything I have not already tried - but so far none of the solutions have worked for me or others using my mailserver.
KEY: The one solution (not really a solution) that ABSOLUTELY ALWAYS works is to continue clicking Send/Receive until Outlook makes the connection and sends and receives email. Be aware that I change absolutely nothing on mailserver or client but just continue clicking Send/Receive and eventually it works.
I have experienced the problem when the server is under load and I have experienced the problem on multiple machines when the server is under no load.
I have also seen Outlook work fine when the server is under load.
I have experienced the problem on inhouse client computers behind the firewall. Other users of my mailserver have experienced same error from outside the firewall - multiple people using different ISPs.
I have experienced the error on several machines including Win98SE, Windows NT, Windows 2000, Windows XP running various versions of Outlook including Outlook 97, Outlook 2000, Outlook 2003 and various versions of Outlook Express. I have experienced the problem on machines running various versions of Norton Anti-Virus, Norton Firewall, Norton Internet Security.
At this point in my mind, the problem is with Outlook/Outlook Express. The reason I think this is because I can be experiencing the problem on a machine running Outlook/Outlook Express - and at the same time check mail against the same server using Mozilla Thunderbird email client from another machine and it works fine. In fact while Outlook is trying and dying slowly as it checks 4 mailboxes, I can click Mozilla Thunderbird's Get Mail button as fast as I can and it will not fail or even hiccup. In fact it checks against the server so fast without failing that I can not even read the status messages coming from Thunderbird as it polls the mailbox.
I have been using Outlook/Outlook Express for years. I have only been running Mozilla Thunderbird for a couple of months but so far I have not seen Thunderbird cough up this error - not even once.
At this moment, the mailserver is under load (refusing requests to connect from known spam senders) and machine running XP Home SP2 and Outlook 2003 is failing and at the same time, from a different machine running XP Pro SP2, Thunderbird, I am clicking the Get Mail button in Thunderbird as fast as I can and it is not failing at all (one time it was a little slow in checking the mailbox but completed without an error).
Also all of the machines I have are fully patched and I am running Ad-aware SE on all of them. Ad-aware has never refused to run on any of them but it almost always finds spyware - even on a freshly formatted machine that has done nothing but have Windows loaded and get updates from Microsoft and then load Ad-aware and run it.
I simply must conclude the problem is Outlook/Outlook Express and this is distressing because the software is so ubiquitous and while it will be relatively easy for me to disable Outlook/Outlook Express and install Mozilla Thunderbird on my own machines, it will not be so easy to convince other people using my mailserver to do that.
To everyone reading this, I would try running Mozilla Thunderbird which is freely available at www.mozilla.org or try some other mail client such as Eudora to see if it solves your problem once and for all.
By the way, I do *not* work for Mozilla nor am I affiliated with them in any way other than using their software.
If you can't switch away from Outlook/Outlook Express, then try not changing anything on your computer and just keep on clicking Send/Receive and see if eventually (may take 20 times over 10 minutes) it will successfully send and receive mail.
I am very curious to know if my experience correlates with other's experience in this error/solution.
Hope this information helps everyone.
Was this reply helpful? (0) (0)