sp3 won't install on win2000 Server

[dpopiz]

it installed fine on my 2000 professional machines, but when I install it on Server, it says procedure entry point could not be located in kernel32.dll

 

[spyordie007]

are you using the network install?

-Spy

 

[dpopiz]

uhh..I don't know what it's called, but it's the one where I dl'd the whole 124MB exe, instead of using windows update

 

[dpopiz]

that's funny, win2ksp3 even starts extracting when I run it on xp but not win2kserver

 

[spyordie007]

Originally posted by: dpopiz
that's funny, win2ksp3 even starts extracting when I run it on xp but not win2kserver

so it doesnt even begin the initial "extracting" dialog? If it's not extracting why not just use another app. (winzip, winrar, etc.) to extract it and than run it after you've extracted it.

-Spy

 

[dpopiz]

well, I was able to extract it using winrar just fine, but I can't find any file in the result that starts sp3 setup. they're all just for installing a specific update. also, I'd rather install it the normal way on the win2kserver machine, because it appears that the machine doesn't know how to extract cabs. maybe something went wrong in the windows installation

 

[spyordie007]

it appears that the machine doesn't know how to extract cabs.

That's certainly not normal behavior, if you cant find out what dll gives it the ability to view/extract cabs you can probably stick it in your system32 directory and register it. But of course with this one little "oddity" you always have to wonder if something else is not going to be working correctly...

Is this a "new" (clean) install or is this an existing install you are trying to update?

-Spy

 

[Thor86]

Try enabling your print spooler service and/or remote registry service and then try installing the service pack.

 

[Fencer128]

Hi,

Are there different versions of SP3 (now today SP4) for Pro and Server? Are you using them?

Cheers,

Andy

 

[spyordie007]

no, the "network installer" is for all versions of Windows 2000 except for Data Center.

-Spy

 

[Fencer128]

Originally posted by: spyordie007
no, the "network installer" is for all versions of Windows 2000 except for Data Center.

-Spy

You learn something new every day!

Cheers,

Andy

 

[dpopiz]

yeah, it's weird that it has trouble extracting cabs. I just installed it and installed drivers and then tried to run win2ksp3.exe and it gave me the message, could not find entry point in kernel32.dll. does anybody know what that message means?

 

[spyordie007]

out of curiosity what is the entry point it's trying for?
Generally the error would be:
Program.exe - Entry Point Not Found. The procedure entry point SomeProcedureName could not be located in the dynamic link library KERNEL32.dll.

-Spy

EDIT: empasis on the missing stuff

 

[dpopiz]

yeah, spy. that's exactly what it says

 

[spyordie007]

so what is the procedure and what is the executable (the parts in bold and italic)

-Spy

 

[dpopiz]

hmm well the exe is win2ksp3.exe, but in the place where it should say a procedure name, it just has an extra space character.

 

[mikecel79]

A quick search of the MS KB turned up this.
An "Entry Point Not Found" Error Message Is Displayed When the Kernel32.dll File Is Accessed

What is the version of Kernel32.dll that you are running on that machine?

As an FYI for everyone with any Microsoft product I first always go to the Microsoft Knowledge Base when looking for a solution to a problem. They have hands down the best KB I've ever seen. Novell probably has the 2nd best one.

 

[dpopiz]

ah, I forgot about ms kb. you're right, they do have a fantastic kb. that particular entry doesn't concern my problem though. it's talking about the "SetHandleContext" entry point related to running out of date software on 2k. I searched the kb myself and couldn't find anything about my problem. well, I'm going to try reinstalling win2kserver now, even though I'm already working on a fresh install, but this time I won't install drivers before I install sp3. perhaps the drivers messed something up.

 

[mikecel79]

What is the version of the Kernel32.dll you are running? Perhaps you just need to replace that file and you'll be all set.