Re: OE Error # 0x800CCCOF
- From: "Kuay Tim" <TimJohn@xxxxxxx>
- Date: Sat, 21 May 2005 16:28:33 -0700
This is the very good news, indeed, Harry! I'm sure your time spent on the
issue will be rewarded in the future.
--
Tim K.
aka Kuay Tim
MS-MVP - (IE/OE)
Lynnwood, WA
*
"webster72n" <hbethke@xxxxxxxxxx> wrote in message
news:%23IkE$GkXFHA.3860@xxxxxxxxxxxxxxxxxxxxxxx
PA Bear, Jim and everyone:
As embarrassing as this may be, but I may not have to change my identity
after all for the simple reason, the fault was in my configuration, without
me realizing. Under User Information I had entered a different name for my
mail and news. Once I synchronized those two, the error message stopped
appearing. Hope it stays this way.
If it shouldn't, I'll let you know.
Thank you all.
Harry.
"PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
news:ucptj5bXFHA.1384@xxxxxxxxxxxxxxxxxxxxxxx
> What Jim said.
>
> You can use any name you want.
>
> Do not delete the "pseudo identity" until you've gotten all of its folders
> imported into the new Named Identity and you confirm that none are
missing.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE/OE) & Security
>
> webster72n wrote:
> > PA Bear:
> >
> > Before I go ahead and change my identity, I have a question:
> > My default identity was not my name, but a pseudo identity.
> > Must I use my real name for the new identity, or can I choose any?
> > Thanks for your patience.
> >
> > Harry.
> >
> >
> > "PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
> > news:OiyHGS%23WFHA.2740@xxxxxxxxxxxxxxxxxxxxxxx
> >> Creating and testing you account(s) in a new Named Identity is no big
> >> deal,
> >> Harry. I *do* think your current identity has been damaged, especially
> >> if
> >> it's the default one named 'Main Identity'.
> >>
> >> The only way to determine if the current identity is corrupt is to try
> >> the
> >> account(s) in a new Named Identity as I explained. NB: Do not rename
the
> >> 'Main Identity' and do not give the new identity the name 'Main
> >> Identity'.
> >>
> >> With email scanning disabled from the get-go, if the problem doesn't
> >> persist in the new Named Identity, just import your folders* from the
old
> >> 'Main Identity' (http://www.insideoe.com/faqs/how.htm#importOE5) and
then
> >> delete 'Main Identity' (File>Identities>Manage identities).
> >>
> >> Just do it. I promise it won't hurt. <w>
> >>
> >> * Two suggestions before importing folders into the new Named Identity:
> >>
> >> 1a. Move as many messages as possible out of Inbox and Sent Items and
> >> into
> >> other Local folders.
> >>
> >> 1b. Delete the contents of Deleted Items folder.
> >>
> >> 1c. Compact all Main Identity folders
> >> http://www.insideoe.com/files/maintain.htm#compact
> >>
> >> 2. You don't really need to import empty Inbox, Deleted Items, Outbox
or
> >> Sent Items folders.
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-Windows (IE/OE) & Security
> >>
> >>
> >> webster72n wrote:
> >>> I don't have the courage to mess with my identity, PA Bear.
> >>> And don't think that that may be the case.
> >>> How can I determine if the identity change would be at fault?
> >>>
> >>> Harry.
> >>>
> >>>
> >>> "PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
> >>> news:%23LF8aP9WFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
> >>>> <sigh> Jeez, it's my day for OE and AV problems, it seems. (See
thread
> >>>> 'Can't send/rec e-mail - ?reinstall?')
> >>>>
> >>>> Your current Identity may have been damaged by Avast's previous
> >>>> settings
> >>>> (especially if its the default Main Identity).
> >>>>
> >>>> 1. Try one or more of your mail accounts in a new Named Identity
> >>>> (File>Identities>Add new identity).
> >>>>
> >>>> NB: Make absolutely certain that Avast is not configured to scan
> >>>> incoming/outgoing mail before running your first Send/Receive.
> >>>>
> >>>> 2. Assuming all is well, import messages from the old Identity before
> >>>> deleting it (File>Identities>Manage Identities).
> >>>> --
> >>>> ~Robear Dyer (PA Bear)
> >>>> MS MVP-Windows (IE/OE) & Security
> >>>>
> >>>>
> >>>> webster72n wrote:
> >>>>> One of us didn't have their fingwers crossed, PA Bear.
> >>>>> That dreaded message is still there.
> >>>>> I'm just glad to be able to fix it, even though only temporarily.
> >>>>> Now we'll have to look into and explore the remaining possibilities
> >>>>> in the link from microsoft you provided.
> >>>>> Keep you posted.
> >>>>>
> >>>>> Harry.
> >>>>>
> >>>>>
> >>>>> "webster72n" <hbethke@xxxxxxxxxx> wrote in message
> >>>>> news:O0RbFT8WFHA.2128@xxxxxxxxxxxxxxxxxxxxxxx
> >>>>>>
> >>>>>> Thanks, PA Bear.
> >>>>>> Let's keep our fingers crossed.
> >>>>>>
> >>>>>> Harry.
> >>>>>>
> >>>>>>
> >>>>>> "PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
> >>>>>> news:%23QQ0L91WFHA.1384@xxxxxxxxxxxxxxxxxxxxxxx
> >>>>>>> Uh...YW.
> >>>>>>>
> >>>>>>>>>> ...Avast has specifically OE mail and others.
> >>>>>>>>>> Since I don't have a problem with my other emails, it should
> >>>>>>>>>> suffice to just disable OE, shouldn't it?
> >>>>>>>
> >>>>>>> If you meant that using Avast you can choose to disable scanning
> >>>>>>> in several Mail Clients and that OE's one of them, yes, disabling
> >>>>>>> only the OE option should do it.
> >>>>>>> --
> >>>>>>> ~PA Bear
> >>>>>>>
> >>>>>>>
> >>>>>>> webster72n wrote:
> >>>>>>>> So far, so good, PA Bear.
> >>>>>>>> You've been a big help.
> >>>>>>>> Thank you.
> >>>>>>>>
> >>>>>>>> Harry.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> "PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
> >>>>>>>> news:e6brdo1WFHA.1508@xxxxxxxxxxxxxxxxxxxxxxx
> >>>>>>>>> <wildly shakes head back and forth> Huh? Come again?
> >>>>>>>>> --
> >>>>>>>>> ~PA Bear
> >>>>>>>>>
> >>>>>>>>> webster72n wrote:
> >>>>>>>>>> PA Bear:
> >>>>>>>>>>
> >>>>>>>>>> That's simple enough, but Avast has specifically OE mail and
> >>>>>>>>>> others. Since I don't have a problem with my other emails,
> >>>>>>>>>> it should suffice to just disable OE, shouldn't it?
> >>>>>>>>>> I thought I'd try this for a while and see what happens.
> >>>>>>>>>> Thanks for your assistance.
> >>>>>>>>>>
> >>>>>>>>>> Harry.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> "PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
> >>>>>>>>>> news:%23NIihRxWFHA.2984@xxxxxxxxxxxxxxxxxxxxxxx
> >>>>>>>>>>> Troubleshooting error messages that you receive when you
> >>>>>>>>>>> are using OL and OE
> >>>>>>>>>>> http://support.microsoft.com/?kbid=813514
> >>>>>>>>>>>
> >>>>>>>>>>> Disable email scanning by your anti-virus application. It
> >>>>>>>>>>> provides no additional protection and even Symantec says
> >>>>>>>>>>> it's not necessary:
> >>>>>>>>>>>
> >>>>>>>>>>> <paste>
> >>>>>>>>>>> Disabling Email Scanning does not leave you unprotected
> >>>>>>>>>>> against viruses that are distributed as email attachments.
> >>>>>>>>>>> Norton AntiVirus Auto-Protect scans incoming files as they
> >>>>>>>>>>> are saved to your hard drive, including email and email
> >>>>>>>>>>> attachments. Email Scanning is just another layer on top
> >>>>>>>>>>> of this. To make sure that Auto-Protect is providing the
> >>>>>>>>>>> maximum protection, keep Auto-Protect enabled and run
> >>>>>>>>>>> LiveUpdate regularly to ensure that you have the most
> >>>>>>>>>>> recent virus definitions. </paste>
> >>>>>>>>>>>
> >>>>>>
> > http://service1.symantec.com/SUPPORT/nav.nsf/docid/2002111812533106
> >>>>>>>>>>> --
> >>>>>>>>>>> ~Robear Dyer (PA Bear)
> >>>>>>>>>>> MS MVP-Windows (IE/OE) & Security
> >>>>>>>>>>>
> >>>>>>>>>>> webster72n wrote:
> >>>>>>>>>>>> I am receiving the following error message, which I can
> >>>>>>>>>>>> temporarily remove by doing maintenance scan and defrag,
> >>>>>>>>>>>> but only for a few days: "Your server has unexpectedly
> >>>>>>>>>>>> terminated the connection. Possible causes for this
> >>>>>>>>>>>> include server problems, network problems, or a long
> >>>>>>>>>>>> period of inactivity.
> >>>>>>>>>>>> Account: (my account), Protocol: POP3, Port: 110,
> >>>>>>>>>>>> Secure(SSL): No Socket error: 10054, Error Number:
> >>>>>>>>>>>> 0x800CCCOF."
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have checked with the ISP and they supposedly are not
> >>>>>>>>>>>> at fault. What specifically might be causing this
> >>>>>>>>>>>> behavior?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Harry.
>
.
- Follow-Ups:
- Re: OE Error # 0x800CCCOF
- From: ²§§Î
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- References:
- OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: PA Bear
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: PA Bear
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: PA Bear
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: PA Bear
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: PA Bear
- Re: OE Error # 0x800CCCOF
- From: webster72n
- Re: OE Error # 0x800CCCOF
- From: PA Bear
- Re: OE Error # 0x800CCCOF
- From: webster72n
- OE Error # 0x800CCCOF
- Prev by Date: Re: Text Size
- Next by Date: Re: OE Error # 0x800CCCOF
- Previous by thread: Re: OE Error # 0x800CCCOF
- Next by thread: Re: OE Error # 0x800CCCOF
- Index(es):
Relevant Pages
|