69324 - alert dialog: ?unknown error 804b0001?

Status: RESOLVED DUPLICATE of bug 81771

(MailNews Core :: Backend, defect)

Description

[John G. Myers]

Mozilla 0.8 on MacOS 8.6.

Mozilla periodically pops up alert dialogs with the text "unknown error
804b001".  The dialog boxes usually appear while I am reading a web page that
has already completed loading.  I have been unable to correlate the messages to
any particular activity.

Comment 1

[HJ]

Any specific site? Is this reproducable?

Comment 2

[John G. Myers]

This reproduces on my machine, but I have not discovered the sequence of steps 
necessary to reproduce it.  I have not been able to correlate it with any 
particular site.  It may correlate with having a background Messenger window 
displaying an NNTP newsgroup.

It would be helpful to me to know what the error code means.

Comment 3

[HJ]

So then something in nsNNTPProtocol.cpp goes wrong. Do you have a logfile?

Comment 4

[Stephan Niemz]

Looks like a duplicate of bug 67212.
See also bug 57591, bug 69351 and bug 57057.

Comment 5

[John G. Myers]

My profile has no POP server, so no duplicate of 67212.  It appears related to 
bug 57057, but as that bug mentions different error codes, it is not a dup.

My profile contains Local Mail, two IMAP servers and one NNTP server.  One of 
the IMAP servers is not reachable, behind a firewall.

Changing component to MAilNews.

Comment 6

[Stephen Moehle]

I am getting this error, 804b0001, on Win2000 trying to access news.mozilla.org
to download new article counts and headers.  news.mozilla.org seems to be down
at the moment.  In NN4, I get the error "There was no response. The server could
be down or not responding."

Here is the NNTP log file.   It is not very revealing:
0[2f6268]: InitializeNewsFolderFromUri(news://[e-mail]/)

Tested with Mozilla 2001022116 on Win2000.

Comment 7

[John G. Myers]

Instructions for enabling log files would be appreciated.

Comment 8

[[e-mail] (gone - use [e-mail] instead)]

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 9

[John G. Myers]

Attachment: contents of IMAP:5,NNTP:5 logfile. Doesn't appear helpful

Comment 10

[Mike Young]

I see this error too. It appears to occur for me when an NNTP connection times
out and closes. (When the new connection cache was put in for bug 65927 , I
started seing this alot.) Before, It would happen that I would get too many
connections to my news server and then once this "unknown error" message popped
up I could read another message (signalling the close of a connection) Now that
the cache is in, I get this while just reading messages, and then a few minutes
afterward (like 2 min) as my connections close. Like the log above, I also have
a supernews server.

Could this be related to the way Supernews drops you from its servers? I know
quite a few ISPs use Supernews, so this may appear at first to not be ISP
specific, but if everyone experiencing this error is somehow using Supernews,
then this might be a little easier to track down.

Comment 11

[Ken Harris]

It's not Mac-specific.  I just got "unknown error 804b0001" on Linux
2001052510.

Comment 12

[stefan livens]

!! see bug 81771 !! 
This bug is described there (but for the pc)

Comment 13

[mozbug1]

I get this when my mail window is open, even if I am not doing anything.  I'm
not using nntp when I get this.  I talk to my mail server over secure imap.

My browser is:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801

I think someone needs to change the OS to all.

Comment 14

[Morten Nilsen]

I get this error in my terminal if I open the site www.exploitationnow.com but
stop it (by clicking home) before it's loaded fully (slow server (for me))
after the message has been dumped, mozilla appears unable to load any sites at
all. restarting mozilla fixes it.
My System; linux 2.4.12 (Trustix)

Comment 15

[R.K.Aa.]

bug 81771 was resolved as WFM. Are anyone still seeing this bug on Mac?

Comment 16

[John G. Myers]

I no longer see it.

Comment 17

[Simon Paquet [:sipaq]]

Mac classic is dead. Marking this a dupe of bug 81771

*** This bug has been marked as a duplicate of 81771 ***