RE: Please! Confirm or deny.....

From: toadlilly (toadlilly_at_discussions.microsoft.com)
Date: 10/25/04 

Date: Mon, 25 Oct 2004 11:51:07 -0700

 /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

"David H. Lipman" wrote:

> 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
>
>
>
>
>
> "toadlilly" wrote:
>
> > 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
> > --
> > ~ toadlilly

Relevant Pages

  • Re: SAMR Interface Calls and Active Directory
    ... SAM is not the storage medium, it is the management code for handling security principals in Windows. ... It is fully active in Active Directory, many LDAP calls that have to do with SAM objects route through the SAM code. ... The difference between a Windows 2000 member machine and a Windows 2000 domain controller is simply that the SAM stores its info in different places. ... activity showed a number of SAMR calls. ...
    (microsoft.public.windows.server.security)
  • Re: SAMR Interface Calls and Active Directory
    ... SAM has been referred to as SAM DB. ... generate SAMR calls on windows 2000 and above machines. ... Author of O'Reilly Active Directory Third Edition ...
    (microsoft.public.windows.server.security)
  • RE: Please! Confirm or deny.....
    ... Maybe hardware or software corruption. ... Run a complete Check Disk and/or use hrad disk manufacturer diagnostics and ... This problem may occur if the Active Directory directory service contains ... Windows Server 2003 cannot initialize the Security Accounts Manager ...
    (microsoft.public.windowsxp.general)
  • SAMR Interface Calls and Active Directory
    ... I have a slight confusion regarding SAM and Active Directory. ... Active Directory (Windows 2000/Windows 2003). ... SAMR are the interfaces used to access SAM ...
    (microsoft.public.win2000.security)
  • SAMR Interface Calls and Active Directory
    ... Manager (SAM). ... Everything was fine until when i setup a Windows 2000 domain controller ... activity showed a number of SAMR calls. ... I have a slight confusion regarding SAM and Active Directory. ...
    (microsoft.public.windows.server.general)