error 0x800ccc0f

Manni · Guest

does anyone have the fix for error 800ccc0f when trying to retrieve email with Outlook in XP pro

Thanks in advance for any help or hints

rusticdog · Posted: Tue Sep 09, 2003 4:22 am Post subject:

Sorry to ask..

Benign is defintely running in the system tray ?

Manni · Cadet Joined: Sep 07, 2003 Posts: 1 Location: USA

rusticdog · Posted: Tue Sep 09, 2003 9:41 pm Post subject:

And do you get this error immediately after you push Send/Receive in Outlook ?
Or does it appear to take a few minutes ?

Be sure that in Outlook you have .b9 appended to the end of your POP3 server address, and then in B9 be sure you have your true POP3 server address listed as an account.

Also what anti-virus software do you run

Thanks

Mariner · Posted: Mon Sep 15, 2003 7:53 pm Post subject:

Hi MANNI,

I had this same error message immediately after upgrading to current Ver of b9.

I e-mailed tech-support for help and was advised that this was firewall problem.

Basically, l had to configure my firewall to allow b9 to make a connection.

I've XP Home.

I later found that this error is covered in Firetrust FAQ's.

Hope this helps Very Happy

[email protected] · Guest

Hello. This problem appeared on my XP Pro pc after C-Net installed their "download manager" onto my pc. I removed that but the error continued. A Google search for "Outlook Error 0x800ccc0f" led to the Symantic site and the suggestion to turn off NAV email scanning, which made the problem go away. When I turned the email scanning back on, I also checked the "protect against timeouts" checkbox. Problem cured...Dave

Iggy · Guest

I am having the same problem.
I have stopped using Benign and haven't had a problem.
I have ZoneAlarm cofigured for b9, still no luck.
Would only occur when I had more than 5 emails to download.
Double and triple checked my settings.
Haven't installed anything new except the new b9 upgrade. I am using version 1.41. The strange thing is this problem didnt start right after the upgrade but has become more and more frequent. Now it happens everytime I check mail. Crying or Very sad

I would like to use b9 since I paid for it. It is a good program. Had to wait quite awhile after the ZoneAlarm upgrade for the b9 upgrade. Looks like I will be waiting again.
Goodbye b9
Buyer beware

Mariner · Posted: Sun Dec 07, 2003 7:01 pm Post subject:

For what it's worth, this problem does appear to be firewall related and, from personal experience, specific to Symantec, though it may well apply to other firewalls.

Any chance you had a Symantec firewall prior to installing ZoneAlarm? If you did, there may be remnants of it that were not removed that require rooting out.

Take it the error message you got was 0800ccc0f?

Ivan Fraser · Guest

here we are again.

In the past few days, I too have been receiving the same error.

Send/receive works okay in Outlook XP, but flags up the error on completion.

It's an annoyance.

I do wonder if it has anything to do with the ZA upgrade a while ago.

I'm again stumped as to why it should suddenly start in the past few days, when it never happened before and when the settings haven't been altered.

Used to run AVG, B9 and ZA fine, with ZA's email scanning off.

Take away B9 and everything's okay. Switch off ZA with B9 running, and the error message recurrs.

It's a pain, but not a passion-killer, so I'll stick with B9 because it's a fine prog.

Mariner - you say it's covered in the Firetrust FAQ - can you tell me where, coz I can't see it.

Cheers.

Ivan

Iggy · Guest

Thanks for the reply Mariner.
Yes that is the error number I get.
No I never had Symantec firewall. Just ZoneAlarm Pro.
I am running XP Pro SP1. Outlook Express and Mailwasher Pro.
Without B9 everything is fine. Like with Ivan, I disable the firewall with B9 and get the error. I have configured the firewall to accept connections with B9 including server connections. This problem just started about two weeks ago, no new installs, and kept getting worse. I contacted my ISP about it and they couldn't find any problem on their end. I hope Firetrust will find a solution. Till then, I am not going to use B9.
Thanks
Iggy

Wayward · Posted: Mon Dec 08, 2003 11:50 pm Post subject:

Very interesting discussion. I have a similar configuration to what has been mentioned ... and don't see the error.

I'm currently using the latest versions of Windows XP Home, AVG Antivirus with E-Mail Scanner running, Zone Alarm Pro, Pegasus Mail, and Benign. The obvious difference in my configuration is Pegasus Mail rather than an Outlook version.

Neither Zone Alarm Pro nor AVG Antivirus seem to create a problem for my configuration with Benign.

Ivan Fraser · Guest

Seems the gremlins have moved on.

The only difference today is that I had uninstalled AVG yesterday for diagnostic purposes and reinstalled.

But I hadn't yet run the setup for OE. I did this this morning and the error message when using Outlook has stopped altogether.

Seems like it could be something to do with the settings for OE impacting somehow on Outlook.

I suggest possibly a recent update from AVG may have altered something in the settings that may have affected the OE scan, which in turn impacted on Outlook. Or could it be the recent ZA update?

Outlook is automatically set up by AVG but OE isn't. And it wasn't till I set it up this am that the error stopped.

Stab in the dark I know, but it's all I'm left with as a possibility if this error is coming to the fore only recently with users of AVG.

I don't know about NAV, but AVG Pro needs to be configured for OE using a setup wizard in the control panel, whereas there's a plugin that's automatically set up for Outlook on install.

B9's configuration has to be set up first before running the wizard, or else the result is an inoperable send/receive. It imports the pop.B9 and replaces it in the acc settings with 127.0.0.1, and it changes the port settings. Whereas in Outlook the pop remains as before, and so do the port settings.

So I'm now running AVG Pro with email scan set separately for both Outlook and OE, B9, and ZAPro firewall with the email scan in that switched off.

Now works fine, just like before.

I hope this helps.

Cheers

Ivan

Magi · Guest

This error is common if Internet traffic causes the connection to drop. Try again. Try dropping V90 protocol

Perry · Lieutenant Joined: Oct 19, 2003 Posts: 291 Location: USA

Fran Spain · Guest

Solution: I found out that you have to decrease the MTU in ALL computers behind the firewall. Use a program (tcpoptimizer from speedguide for example) to calculate what is the maximum packet size not fragmented, for me 1454, then use this MTU to change all the net adapters in ALL THE COMPUTERS in the local Lan. Fixed it.


	Home ˇ Topics ˇ Submit News ˇ Top 10 This entire site, Cops Themes, and Computer Cops are Š 2002 - 2004 Computer Cops, LLC. All rights reserved. You can syndicate our news using the file RSS 0.91, ultramode.txt, or RSS 1.0. Acceptable Use Policy. Use signifies your agreement. Engine Copyright Š 2002 by PHP-Nuke, GNU/GPL Licensed. ICRA Member. Paul Laudanski, Member of Computer Cops, LLC Server Load: 752 pages served in previous 5 minutes. Page Rendered: 0.473 seconds.