190817 - Installation of 2003012508 Win32 build results in "Entry point not found" error.

Status: RESOLVED DUPLICATE of bug 190144

(SeaMonkey :: General, defect)

Description

[tom.williams]

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021212

The last few WIN32 nightly builds I've been trying to install have been
resulting in "Entry point not found" errors.  I DO realize the nightly builds
are NOT stable, so I'm submitting this bug report as an "FYI".

After the installation of the 2003102508 Win32 nightly build, Mozilla tries to
start and this error is received:

OleMainThreadWndName: Mozilla.exe  Entry point not found

?NS_NewPipe@@YAIPAPAVnsIInputStream@@PAPAVnsOutputStream@@IIHHPAVnsIMemory@@@Z
could not be found in xpcom.dll

Reproducible: Always

Steps to Reproduce:
1.Download the latest Win32 nightly Mozilla build
2.Try to install it
3.

Actual Results:  
Entry point not found error occurs

Expected Results:  
Entry point should be found.

Comment 1

[Benedikt Kantus]

I installed this very build today without any problems. I used the
mozilla-win32-installer-sea.exe from the FTP site.

Comment 2

[tom.williams]

I used the "Windows" link from the main Mozilla page (http://www.mozilla.org/)
and got the reported error.  In fact, the last 3 nightly builds I've downloaded
have exhibited this behavior and I've been reverting back to the "official"
Mozilla 1.3a alpha release in order to get a "working" Mozilla again.

I'm open to the possibility that this problem is environmental, but at this
point I can't use any of the Mozilla nightly builds.  If this problem persists
when the future "stable" releases are published, then I'll be screwed.... :)

Peace....

Comment 3

[Chris Lyon]

This is probably caused by installing over an old Mozilla directory without
completely uninstalling it.  Try deleting Mozilla and profiles, then reinstall.

See bug 168517

Comment 4

[tom.williams]

Thanks for the tip. It looks like bug #19014 is the problem I'm encountering:

http://bugzilla.mozilla.org/show_bug.cgi?id=190144

I'm satisfied that this can be closed out and referencd to bug #190144.

Peace....

Comment 5

[Chris Lyon]

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