Closed Bug 32588 Opened 25 years ago Closed 24 years ago

Installing gives an error "Entry Point Not Found:"

Categories

(SeaMonkey :: Installer, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: baffoni, Assigned: ssu0262)

Details

(Keywords: helpwanted, relnote, Whiteboard: [nsbeta3-])

Installing gives an error "Entry Point Not Found: Procedure entry point NLS_PropertyResourceBundleDeleteChar couldn't be found in NSRES3231.dll" Installed build ID: 2000032011 with installer, onto NT 4.0SP5, 128MB RAM, AMDK6-2-333.
baffoni@aerovironment.com, Can you try with a more recent build? These type errors have not been seen in awhile (see also bug 28931,29111) thanks
from baffoni@aerovironment.com: ------------------------------------------------------------------------I'm still getting a "The procedure entry point NLS_PropertyResrouceBundleDeleteChar could not be located in the dynamic link library nsres3231.dll" error when I launch the application. It seems to install just fine however. ------------------------------------------------------------------------ This is not an installer issue. Changing component to Browser-General.
Assignee: ssu → asadotzler
Component: Installer → Browser-General
QA Contact: gbush → jelwell
Sean, This error seems to come up during installation- not after. I will search out an SP5 machine. from baffoni@aerovironment.com I get the stated error when launching the installer application, although after clicking "ok" it continues to install just fine. It _IS_ an installer bug.
Assignee: asadotzler → ssu
Component: Browser-General → Installer
Have you tried a talkback archive? I don't use the installer and my error messages usually go away after I rerun mozilla. windows2000: I have 2 nsres3231.dll files 12416.0.0.9755 D:\Program Files\Netscape\Mozilla\daily\bin\psm 12416.0.0.9880 E:\winnt\system32 I'm guessing this file comes from the PSM, so when did you get the psm? [you might try installing it again, or at least temporarily recycling all copies of this file]
Michael Baffoni wrote: First let me say that I normally use the talkback versions (which work normally, no install errors), but I occaisionally grab the install versions to convert my 4.72 prefs to Moz. I did a search through my system and found two versions of the nsres3231.dll; One was in one of my Mozilla installs (one with crypto), and it was the .9755 version, the other (also 9755) was in my system32 directory. I had a couple of the 9880 versions in my netscape/server4 directory so I moved the .9755 out and replaced it with the 9880 version. Doing so fixes the error. -- Sounds like the install application needs to do a check on the version of nsres3231.dll installed in the system32 directory and make sure it is the 9880 version.
Confirming. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
Sorry for the spam. New QA Contact for Browser General. Thanks for your help Joseph (good luck with the new job) and welcome aboard Doron Rosenberg
QA Contact: jelwell → doronr
Expect a minus, If so please add this to the relnote3. Adding helpwanted per nsbeta3- Marking relnote because I'm sure windows users would like to know why mozilla's installer crashes. Hi Michael, i'm running through installer bugs... can you still reproduce this?
Severity: minor → major
giving nsbeta3- unless evidence surfaces that this is a more common problem. Strange that this is seen as coming up during the install, nothing in the install should be referencing PSM in any way.
Whiteboard: [nsbeta3-]
I don't have this problem in the current build (but I also don't have the old 7550 dll around to see if it is checking for the old version). I tried by renaming the current file to .old but it didn't seem to need it because it didn't recreate the file or throw up an error. <shrug> (why is this status set to new? I thought it was "resolved" a while ago....) Changing to Worksforme.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
verified
Status: RESOLVED → VERIFIED
QA Contact: doronr → gbush
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.