154243 - entry point not found ToNewUTF8String@nsString@@QBEPADXZ

Status: RESOLVED WORKSFORME

(SeaMonkey :: Installer, defect)

Description

[K'Trina Medina]

I upgraded from 6.0 to current trunk build (2002-06-25-04-trunk) and got this 
error upon launch of 7.0:

Error:
XPCOM:EventReceiver:Netscp.exe - Entry Point Not Found
The procedure entry point ?ToNewUTF8String@nsString@@QBEPADXZ could not be 
located in the dynamic link library xpcom.dll.

I'll attach a screen shot

Comment 1

[K'Trina Medina]

Attachment: Error received when upgrading 6.0-7.0

Comment 2

[K'Trina Medina]

I upgraded from 6.0 to current trunk build (2002-06-25-04-trunk) and got this 
error upon launch of 7.0:

Error:
XPCOM:EventReceiver:Netscp.exe - Entry Point Not Found
The procedure entry point ??1nsXPIDLCString@@QAE@XZ could not be located in the
dynamic link library xpcom.dll.

I'll attach a screen shot

Comment 3

[K'Trina Medina]

Sorry I meant 6.1 to current trunk build on my last comment

Comment 4

[K'Trina Medina]

Attachment: Error received when upgrading 6.1-7.0

Comment 5

[Daniel Veditz [:dveditz]]

These are two different errors, both caused by old components left over during
the upgrade. Better than a screen shot (we see these errors a lot) would be a
list of all the .dll's in your components directory that are older than the
trunk build you just installed. These form the list of possible culprits (old is
not necessarily wrong, but it narrows the list so we can try to figure out which
ones are obsolete).

The 6.0->trunk and 6.1->trunk lists are probably different (since you got
different errors), please check them both.

Comment 6

[Henrik Gemal]

any progress on this bug?

Comment 7

[Joshua Gao]

It seems to be a problem with XPCOM.DLL. I created a fresh install (new hd) and
it still had the problem. I am using Mozilla 1.2b

Comment 8

[Todd]

Hi All,

  I get this bug reported to me a lot by my customers. (The first time they
see it, they get a little scared thinking they did something to their 
machines.  I tell them to just ignore it.)

   And, I just got this bug myself when I upgraded to 1.3.0.2002112108.
It usually pops up only once, always after an upgrade.  Then randomly
once or twice a month, but I have not figured out how to reproduce it,
except after an upgrade.

   I am adding myself to the cc list.

--Tony

Comment 9

[Josh]

mozilla.exe - Entry Point Not Found

The procedure entry point ??1nsAVLTree@@QAE@XZ could not be located in the
dynamic link library xpcom.dll

I managed to get this error after upgrading from Moz1.1 to Moz1.2 Final.  Before
I upgraded I did go thru the uninstall process before installing 1.2 to try to
clear 1.1 out.  I can now reproduce the error screen by going to: Help -> About
Plug-ins  I previous builds (and on an earlier OS install) I got it a lot more
often after upgrading my Mozilla.

Currently using Win2K SP3.  I can try it on W98, WMe if needed.

Directory listing of the components directory is available at:
http://www.datainsites.com/mozilla.txt

Screenshot of error is available at:
http://www.datainsites.com/mozilla.jpg

Comment 10

[Al]

I get the exact same error as Josh with the exact same Win2K SP3

Comment 11

[James Landay]

I get the same error as Josh on Windows XP SP1.  I first saw it when moving to 
Mozilla 1.2 and also get it in 1.2.1

James

Comment 12

[Justin Churchey]

It installs appropriately, but that error message comes along everytime I start
the browser; however, thus far, no performance issues have been noticed.

Comment 13

[Chris Hobbs]

I'm hoping this is the same bug, so I'm not starting a new one. I'm running
"Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030206". I get
this Entry Point Not Found error in one particular, repeatable instance. On
www.ebay.com a user can add auction items to a watch list. When I submit a new
item for this watch list, I get the following error. It then continues normally
with no discernable problems. I have never received the error submitting any
other form.

The procedure entry point
?NS_NewPipe@@YAIPAPAVnsIInputStream@@PAPAVnsIOutputStream~~IIHHPAVnsIMemory@@@Z
could not be located in the dynamic link library xpcom.dll.

Comment 14

[Daniel Veditz [:dveditz]]

I suspect the original bug is WFM.

The quite separate problem in comment 9 is due to an old spellchecker (search
closed bugs for nsAVLTree for the dupe).

comment 13 describes yet another bug, please file it separately and put the
invalid entry point in the summary--it's the only way we can track these. Since
you've only seen it on one site put "ebay" in the summary too. ("entry point not
found on ebay
?NS_NewPipe@@YAIPAPAVnsIInputStream@@PAPAVnsIOutputStream~~IIHHPAVnsIMemory@@@Z"
-- put the entry point last.) Meanwhile do a directory listing of
components\*.dll sorted by date and attach it to the new bug. The fact this one
happens on form submission is especially curious and very different MO from the
usual entry point errors. I still suspect an out-of-date add-on, though, so
think about what else you've installed that didn't come with the standard
Mozilla install.

Comment 15

[Chris Hobbs]

Thanks for the hint - listing the components directory did reveal one old .dll
from the Enigma plugin which I knew wasn't working with this beta. Removing it
solved my ebay problem. I'm removing myself from the cc's.

Comment 16

[Josh]

Well, as comment #14 says, what I sumbitted was due to old .dll files left in
the directory from spellchecker.  I got rid of them in between removing 1.21 and
installing 1.3.  Therefore I'm removing my e-mail from the CC list.

Comment 17

[Dan]

Attachment: "Entry Point Not Found" Error

Hi,  Received the following error when upgrading Mozilla 1.1 to 1.3
(mozilla-win32-1.3-installer.exe): "The procedure entry point
???InsALVTree@@QAE@XZ could not be located in the dynamic link library
xpcom.dll."  I now get this error each time I attempt to initiate the Mozilla
session. See attached Screen Shot.  Thanks, -Dan

Comment 18

[Henrik Gemal]

did you install any extension, like spellchecker, linky, etc?

Comment 19

[Daniel Veditz [:dveditz]]

WFM on newer builds, unless the user installs into a previous directory and
elects to skip the "cleanup" step. Then it's on them if they have obsolete add-ons.