Closed Bug 28372 Opened 25 years ago Closed 25 years ago

Javascript error on Mail startup

Categories

(MailNews Core :: Backend, defect, P1)

x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rzach, Assigned: alecf)

Details

(Whiteboard: [PDT+])

When starting mailnews I get the following JS error in the console: error verifying accounts [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIMsgAccount.incomingServer]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://messenger/content/accountUtils.js :: getFirstInvalidAccount :: line 31" data: no] Linux build 2000.02.17.15
Can you continue on?
Reassign to alecf
Assignee: phil → alecf
Severity: normal → major
Keywords: beta1
Priority: P3 → P1
Yes, I can start up fine. Just thought I'd log it.
Esther says she isn't seeing this.
Today(2000.02.18.08),no-JS-error-but-this: error verifying accounts TypeError: account.incomingServer has no properties (sorry-about-hyphens-space-is-broken)
this only happens if you have an account in your "mail.accountmanager.accounts" preference that doesn't have an incoming server associated with it. I've gotten in this state, as has rhp. I fixed some bugs associated with this situation yesterday actually, can you try today's build?
This is today's build (2000.02.18.08). No JS error, but the "error verifying accounts" is still there. I do have a server in accountmanager.accounts which doesn't exist (server12), and I have a server (server13) which isn't in the list. The things you fixed were regarding the problem of screwing up the prefs, or the error message when starting up? If the latter, then I should just edit the prefs, right, and watch if I see it happen again? (I had deleted some accounts...)
right. I wish I knew how the prefs get stuck in this state (and if you figure it out, let me know, and we'll open another bug) but at least now we're ready for it. the verifying account error is ok, I've looked at the code. we'll clean this up after beta.. since I fixed that yesterday as part of another checkin, I'll just mark this fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Verified-fixed.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.