Discussion Locked

starting winnt server 4.0 sp6a

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I like to reboot my NT servers once a month, on one particular server which is used as a BDC and a file server i decided to reboot this particular server before i left for the day, at the logon screen i got the folowing errors:
1. THE PROCEDURE ENTRY POINT SmapLS COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY KERNEL32.DLL
2. THE PROCEDURE ENTRY POINT ReinitializeCriticalSection COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY KERNEL32.DLL
3. THE ORIGINAL 654 COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY SHELL32.DLL

HELP... the only thing i did differently was a couple of days ago i was using an evaulation copy of Sunbelts Domain Reporter and i loaded an agent on this server to capture data for NTFS reporting, i did not like the way the program was working so i deleted the agent from sunbelt's program which it did successfully from this particular server, that was the only change that was done to this server, any help would be greatly appreciated, I can't access any of the services on the server or it's files.

5 replies

by syscokid

My guess is that those 2 DLLs are damaged. Can you boot wuth your 3 NT startup disks and install new copies?

by aaron_wurthmann

Answer #1 is funny. "Those DLLs"... umm "KERNEL32.DLL" did anyone notice what the first part of that file name is? Okay man, you aren't going to like this but if you keep getting the BSOD (Blue Screen of Death) you don't really have a choice. I'd assume that you don't have a "Windows NT Emergency" disk handy either right? Try the following, first REinstall the lastest Service Pack, it just may solve the probelm. If not you will have to basically reinstall the OS, you can do this by booting fromthe boot floppies or the Windows NT server CD itself then selecting the "Repair" option. After you reinstall and add the server back as a BDC you should put the latests SP on again. It is going to be painful but by the sound of it you don't have a good back up of this server and you aren't really sure what caused the problem. A word to the wise, don't install test software on a mission critical server in the first place.

by tperachio

I actually do have an erd, which i tried but still get the same errors, the weird thing is my end users are still able to access their files. if i were able to copy the winnt\profiles folder to another drive i would not care about re-installing NT.

This discussion is closed to new replies.