Printable View
anybody see this error?
when you start up, you get a message
"Isass.exe enter point not found and saying something about its not in the advapl32.dll location"
and when clicked ok, it say shutdown in 1 minute and reboots. So i basically cant get into my system through windows.
Is the drive in FAT32? Any way of checking whether these files even exist?
If it's in FAT32, you can boot up to a DOS prompt, and look for the files in DOS. lsass.exe would be in c:\winnt\system32\ and advapi32.dll would also be in there.
Did you try the repair utility on the Win2k CD?
Sounds like a messed up windows install, like your hard disk messed up a couple of files...happened once when i shut off my computer without using the proper method, screwed up some files...had to reinstall the whole system.
no way into the system. it is a NTFS partition and the system has had 2000 on it for at least 4 months with no problems. no cd as it has been ghosted.
Yeah i've seen this b4 actually asked quite a lot!
Hold on i'll check me database:
tick tock
tick tock
tick tock
Run repair from your 2000 cd! If ghosted re-ghost it.
As you need to have had windows 2000 sp2 installed to stop this error.
Once ghosted i would download sp2!!
later
b :)
the ghost image had sp2 in it. I know if I re-ghost it it will work, but I was curious as to why it had this error.
i can probably blame it on the disk. Sometimes certain files just get screwed up esp when you don't shut down properly.
(If it's an IBM 75GXP, all of them will eventually get screwed up :D)
Also what i did was boot from diskette. The diskette had lsass.exe from another machine on it i copied and replaced it!
Worked perfectly!
:)
You sure? Coz it's a fix in sp2!!!
Nope justin it aint the disk for from it.
Blame MS windows 2000!!!
Ok after reading more of my notes lsass.exe causes a few errors the one fixed in sp2 was different to yours.
Pointing it down to one would perhaps need the error number!
later
b :)
Happened to me once, was the disk. because i shut it off when it was working...****ed up some sectors :eek:Quote:
Originally posted by Beacon
Also what i did was boot from diskette. The diskette had lsass.exe from another machine on it i copied and replaced it!
Worked perfectly!
:)
You sure? Coz it's a fix in sp2!!!
Nope justin it aint the disk for from it.
Blame MS windows 2000!!!
Trust me a lot of times it's a disk error...if it screws up the lsass file how can it run?
Windows isn't the ONLY OS with problems...
Dont recall saying it was!
Yeah. I was talking about DOS...of course! ;)Quote:
Originally posted by Beacon
Dont recall saying it was!
positive as all our ghost images are win2k sp2. no choice in the matter.Quote:
Originally posted by Beacon
Also what i did was boot from diskette. The diskette had lsass.exe from another machine on it i copied and replaced it!
Worked perfectly!
:)
You sure? Coz it's a fix in sp2!!!
Nope justin it aint the disk for from it.
Blame MS windows 2000!!!
thanks guys for the insight.
Beaker - download site for sp2, if only have it on MSDN disks...
there is a probaly easily avalible called NTFSdps which will allow you to access NTFS drive tables, i have a copy if you want to borrow it ever ;)Quote:
Originally posted by scoutt
no way into the system. it is a NTFS partition and the system has had 2000 on it for at least 4 months with no problems. no cd as it has been ghosted.
sure simon, how big is it? drop me a link or I can drop you my email.
Zipped up its 800KBQuote:
Originally posted by scoutt
sure simon, how big is it? drop me a link or I can drop you my email.
email me at work [email protected] or give me your email addy here, and i will email it to you (unless you want it sent another way)
"NTFSdps"
opps
i meant, NTFSdos ;)
in my experience, cloned OS are marginally less stable than installed ones. Normally won't make any difference day-to-day, but might explain odd occurrences like this...
that might just be true Behemoth. but we don't ahve a choice. beats running around installing win2k on 1000 pc's ;)
also we are running Novell server so it doesn't make since why this file even exist.
sure we just re-ghost it. that is the only choice we have. so far we have had 2 pc's that had this error in the past week. very strange as we can't figure out why. easy fix jsut 10 minutes of our time, but curious as to why it all of a sudden happens.
Are your machines on a NT Domain? Do you use the MS tools for this kind of stuff, or just a direct clone? Because if you have duplicate SIDs on your network, I'd suspect it would introduce major security or stability problems.
Doesn't this occur when you create an image without removing the PC from the domain beforehand?Quote:
Originally posted by JoshT
Because if you have duplicate SIDs on your network, I'd suspect it would introduce major security or stability problems.
lordsty
no Josh, we are on a Novel server and domain. and we still can get the SID duplicate problem. but this is not becasue of that.
lordsty : each machine has it's own ID number. we use the serial number. so each S/N is on the case (cover part that comes off) and the back of the computer. also in the BIOS. if those covers get switched at anyone time and we redo a computer and enter the wrong SID then we can get conflict errors.
so if the machine just gets replaced it has a new S/N we just add to our DB. if we just re-ghost a machine then since the S/N is already on the network then it doesn't matter since it is the only one. as long as you only have one machine with one SID then you're ok.
Scoutt, thanks for clarifying, I remember someone having this issue once, but forgot why it was occuring.
lordsty