Windows 2003 immediately logs off upon login

Discussion in 'Active Directory' started by LincolnIT, Nov 4, 2006.

  1. LincolnIT

    LincolnIT Guest

    I have a Win2k3 DC server that would not boot up due to the missing
    ntoskrnl.exe error. So I reinstalled the OS using the repair option. Now it
    boots up but I can't login with the Administrator account.

    It accepts my password, says that the settings are being applied quickly
    followed by saving settings, logging off, right back to the login screen.

    Any ideas here would really help. I really have to get this server back to
    normal asap.
     
    LincolnIT, Nov 4, 2006
    #1
    1. Advertisements

  2. LincolnIT

    Jorge Silva Guest

    Hi
    By reinstalling or reparing doesn't mean that you have everything Ok.
    First you need to determine the cause of that error, could be hardware
    problems generally are...
    after you determine the real problem and fix that, you can repair or recover
    it fom last Bk.
    Troubleshooting Stop messages: general strategies
    http://technet2.microsoft.com/Windo...cf33-465d-b60e-baefc2f684761033.mspx?mfr=true
    Debugging Tools for Windows - Overview
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
    --
    I hope that the information above helps you
    Good Luck

    Jorge Silva
    MCSA
    Systems Administrator
     
    Jorge Silva, Nov 4, 2006
    #2
    1. Advertisements

  3. Jorge de Almeida Pinto [MVP - DS], Nov 4, 2006
    #3
  4. LincolnIT

    Jorge Silva Guest

    Many ways
    take off the disk plug it in in another server import the disk an look for
    the dump file analyse it, if you can access to that server from other
    network machine try to access to the C$ share and take the dump file to
    analyse, if you can't try to start in safe mode or DSRM...

    Note: when blue screens start to happen generally suggesting hardware
    problems this action can lead to some components curruption that can afect
    other servers in network if that server styarts to replicate currupt data,
    in my opinion the best to do is to take that server off the network, perfomr
    metadata clean on the existing ones, resolve the server problem and install
    it again, add it again to network.
    That's why I'm not using the options here to restore using asr or backu
    etc...
    also check
    STOP 0xC0000244 when security log full
    http://support.microsoft.com/kb/232564
    --
    I hope that the information above helps you
    Good Luck

    Jorge Silva
    MCSA
    Systems Administrator
     
    Jorge Silva, Nov 4, 2006
    #4
  5. LincolnIT

    LincolnIT Guest

    LincolnIT, Nov 4, 2006
    #5
  6. LincolnIT

    lforbes Guest

    Hi,

    Can you acess the server C$ from another machine? If so, delete the admins
    profile in docs and settings. Boot into safe mode and try again. How did it
    lose its ntoskrnl? That is a protected file. Did it get a virus?

    Cheers

    Lara
     
    lforbes, Nov 5, 2006
    #6
  7. LincolnIT

    LincolnIT Guest

    Problem solved....I ran a parallel install then copied the .exe files to the
    original system32 folder. I don't know how ntoskrn error came up but at least
    now I can login.
     
    LincolnIT, Nov 5, 2006
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.