Closed Bug 618634 Opened 15 years ago Closed 13 years ago

Receive failure code 0x80004005 and 0x80004003 on start

Categories

(Thunderbird :: OS Integration, defect)

x86_64
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: trappmanrhett, Unassigned)

References

Details

(Whiteboard: [CLOSEME 2012-03-15])

User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:2.0b8pre) Gecko/20101119 Firefox/4.0b8pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 Error: [Exception... "'Failure' when calling method: [nsICommandLineHandler::handle]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "<unknown>" data: no] Error: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBHdr.messageId]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: file:///C:/Program%20Files/Mozilla%20Thunderbird/modules/WinSearchIntegration.js :: search_get_support_file :: line 787" data: no] Source File: file:///C:/Program%20Files/Mozilla%20Thunderbird/modules/WinSearchIntegration.js Line: 787 Error: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBHdr.messageId]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: file:///C:/Program%20Files/Mozilla%20Thunderbird/modules/WinSearchIntegration.js :: search_get_support_file :: line 787" data: no] Source File: file:///C:/Program%20Files/Mozilla%20Thunderbird/modules/WinSearchIntegration.js Line: 787 Reproducible: Always
Version: unspecified → 3.1
Summary: non-fatal errors on start → Receive failure code 0x80004005 and 0x80004003 on start
Sid0 any idea what could be wrong here ?
Component: General → OS Integration
QA Contact: general → os-integration
Does this still happen in TB 7?
See Also: → 640970
See Also: → 618640
See Also: 640970
NS_ERROR_FAILURE is just a generic catch all error code. It could mean almost anything.
See Also: 618640
Yes, but there could be concrete IF() conditions that produce it. It should be possible to look at them and tell what failed and so what could be wrong. The NS_ERROR_INVALID_POINTER probably means there was a NULL pointer passed to some function. I am not yet sure which. The search_get_support_file is nowadays located in the file searchCommon.js, not WinSearchIntegration.js . So I need to know if this still happens in recent versions. But I do not use Windows and that Search integration so anything I could do is to produce hints to the reported on what he could test. But he seems gone now. And there seem to be two problems, maybe unrelated.
The WinSearchIntegration one seems to be bug 529180. We'd need the original reporter to comment on the 'nsICommandLineHandler::handle' part, whether it still appears.
Depends on: 529180
Whiteboard: [CLOSEME 2010-01-01]
rhett? (In reply to :aceman from comment #5) > The WinSearchIntegration one seems to be bug 529180. > > We'd need the original reporter to comment on the > 'nsICommandLineHandler::handle' part, whether it still appears. Error: [Exception... "'Failure' when calling method: [nsICommandLineHandler::handle]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "<unknown>" data: no]
Whiteboard: [CLOSEME 2010-01-01] → [CLOSEME 2012-03-15]
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.