Please! Confirm or deny.....

[Guest]

reformat of hard drive, reinstallation of xp and sp2. firewall on, cleaned
system with updated norton definitions, ran adaware and spybot and
cwshredder. system ran ok for 4 days then....

diaglog on boot up says:

Security Accounts manager initialization failed because of following error =
handle is invaled error 0x0000008. Click ok to reboot.

rinse and repeats et nauseum.

I cannot get into safe mode. I can get into recovery console with os cd.

this error does not include a countdown and inside windows. I cannot boot
into windows and/or safe mode at all. therefore I am unclear if this is
sasser or not. COuld someone please comfirm or deny <if possible> so I know
to investigate devices or figure out how to work sasser out via recovery
console.

thanks

 

[Guest]

Not Sasser not Blaster.

Maybe hardware or software corruption.

Run a complete Check Disk and/or use hrad disk manufacturer diagnostics and
make sure there is no corruption based upon a hard disk problem.

Based upon a MS TechNet CD lookup on - "Security Accounts manager
initialization failed" I got...

This problem may occur if the Active Directory directory service contains
duplicate cross-reference objects, and these objects represent domains that
are in the Partitions container. If there are duplicate cross-reference
objects, Windows Server 2003 cannot initialize the Security Accounts Manager
(SAM) and Active Directory cannot start. Examples of how you might create a
duplicate cross-reference object include the following: You seize the domain
naming operations master role while Active Directory is broken for a long
period. You seize the domain naming operations master role. Next, you perform
an authoritative restore of Active Directory from a backup that was made
before you seized the domain naming master role. Note Microsoft Windows 2000
domain controllers do not verify all the cross-references. Therefore, Windows
2000 domain controllers do not experience this problem.

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS


When you start your Windows XP Home Edition or Windows XP Professional-based
computer...
CAUSE
This issue may occur if the Security Accounts Manager file (SAM) is
corrupted or missing.
RESOLUTION
To resolve this issue, either restore or replace the SAM file.

However, I could NOT get anything cross referenced to "error code 0x0000008"

Dave

 

[Guest]

/nod

agreed after more research..... I will also try to get a repair copy of SAM
out in system32/config... maybe it got corrupted.. /shrug but since this is
plain ole XP and not windows seerver.... I am now suspecting the hard drive
is just plain so dirty a reformat didnt 'fix' it.

thanks s o much for answerring!!!!!!!!!! <hands David a cookie>

~ toadlilly

Not Sasser not Blaster.

Maybe hardware or software corruption.

Run a complete Check Disk and/or use hrad disk manufacturer diagnostics and
make sure there is no corruption based upon a hard disk problem.

Based upon a MS TechNet CD lookup on - "Security Accounts manager
initialization failed" I got...

This problem may occur if the Active Directory directory service contains
duplicate cross-reference objects, and these objects represent domains that
are in the Partitions container. If there are duplicate cross-reference
objects, Windows Server 2003 cannot initialize the Security Accounts Manager
(SAM) and Active Directory cannot start. Examples of how you might create a
duplicate cross-reference object include the following: You seize the domain
naming operations master role while Active Directory is broken for a long
period. You seize the domain naming operations master role. Next, you perform
an authoritative restore of Active Directory from a backup that was made
before you seized the domain naming master role. Note Microsoft Windows 2000
domain controllers do not verify all the cross-references. Therefore, Windows
2000 domain controllers do not experience this problem.

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS


When you start your Windows XP Home Edition or Windows XP Professional-based
computer...
CAUSE
This issue may occur if the Security Accounts Manager file (SAM) is
corrupted or missing.
RESOLUTION
To resolve this issue, either restore or replace the SAM file.

However, I could NOT get anything cross referenced to "error code 0x0000008"

Dave

reformat of hard drive, reinstallation of xp and sp2. firewall on, cleaned
system with updated norton definitions, ran adaware and spybot and
cwshredder. system ran ok for 4 days then....

diaglog on boot up says:

Security Accounts manager initialization failed because of following error =
handle is invaled error 0x0000008. Click ok to reboot.

rinse and repeats et nauseum.

I cannot get into safe mode. I can get into recovery console with os cd.

this error does not include a countdown and inside windows. I cannot boot
into windows and/or safe mode at all. therefore I am unclear if this is
sasser or not. COuld someone please comfirm or deny <if possible> so I know
to investigate devices or figure out how to work sasser out via recovery
console.

thanks

 

[Guest]

ended up being a hard drive issue.....of the narstiest kind. thought
before it was just a de-frag corrupt problem when i reformatted and
reinstalled everything before... but when i ran chkdsk this time and tried to
repair.... it would get to 72-72%, drop back to 50%... gear back up to 74%
then back to 50% where it then stalled. lololol! I cannot believe i was still
able to boot it up after replacing windows/system32/config/sam, but it did.
but no doubt it wont be up for long.

told customers not to shut it down before backing up criticals again... and
order new hard drive and cable immediately.

Now I am looking for a better hard drive problem detection tool that can
maybe prevent me from having to waste so many hours as I did last week on a
rebuild.

aint we got fun

~ toadlilly