none
Can't log in Windows Server 2012 r2 when the network cable is plug

    Question

  • Hello every body ,
    So here’s my problem, I recently made an update for windows 2012 r2 in 4 of my domain controllers. Since there is impossible for me to enter on these computers.
    I can’t logon on physically on my servers and neither on rdp. The only way I find is to enter in my windows 2012 r2 server domain controllers is to unplug the network cable before the restart of windows and then I plug the network cable after 5 minutes the restart is completely over.
    The problem is don’t find which KB do this kind of thing. Also I have the problem in my physical machines and my virtual servers.
    Thanks


    Tuesday, January 10, 2017 10:09 AM

All replies

  • Hi Marc Lebel,

    >Since there is impossible for me to enter on these computers.
    I can’t logon on physically on my servers and neither on rdp.

    What server do you login? The DCs that installed updates recently, or domain member servers?

    2. When you are unable to login the machine, what error message do you get? Better to provide a screenshot.

    3. Could you find the KB that installed recently, what about the result if uninstall the KBs?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 11, 2017 6:54 AM
    Moderator
  • Hello Anne,

    1.I try to enter on my dc servers that installed the updates. The other dc servers without the update are ok.

    2. I'm unbale to login on rdp and on local the only error i have is that when i tried to enter my login and password windows server does nothing. Not even an error message he just don't do annything, and I assure you that windows is not freeze. I can click to use another account but when i enter an account it's the same no error message he just stay on the same screen.

    3. Here are the suspects

    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3184943)
    Mise à jour pour Windows Server 2012 R2 (KB3182203)
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3175024)
    Mise à jour pour Windows Server 2012 R2 (KB3179574)
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3178539)
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3185911)
    Outil de suppression de logiciels malveillants pour Windows 8, 8.1, 10 et Windows Server 2012, 2012 R2, 2016 Édition x64 - novembre 2016 (KB890830)
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3174644)
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3184122)
    Correctif cumulatif mensuel de sécurité et de qualité pour Windows Server 2012 R2 (KB3185331) - octobre 2016
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3184471) this one failed to be installed
    Mise à jour de sécurité pour Windows Server 2012 R2 (KB3177186)

    I notice also that the updates are not the same in the others servers. 

    Coordialement.

    Marc


    • Edited by Marc Lebel Thursday, January 12, 2017 1:33 PM
    Thursday, January 12, 2017 9:25 AM
  • Hi Marc Lebel,

    Have you got any progress with the issue?

    During some research, it's still hard to find out which KB might cause the issue, if you are still suffering this issue, I would recommend you open a case with MS, so that you may get more professional help and explanation:

    https://support.microsoft.com/en-us/gp/support-options-for-business

    What's more, it's recommended to test new updates in a test environment, after verifying they are stable, then apply them to production environment.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, January 19, 2017 9:47 AM
    Moderator
  • Hello marc here,

    I still have my problem, it's the first time i encounter a problem like this. I already install all the new updates but i still have this problem.

    I will try with microsoft support.

    Best Regards.

    Marc

    Monday, February 6, 2017 1:51 PM
  • Dear Marc,

    Are the domain controllers installed on Physical hardware or virtual hardware.

    If physical try to reinstall the NIC drives.

    If VMware try to reinstall the VMware tools.

    Thanks

    Syed Abdul Kadar M.

    Monday, February 6, 2017 2:05 PM
  • Thanks for the help Syed

    I have the two situations

    4 physical DC 

    1 Hyper-v machine.

    I also tried this solution but i didn't work either.

    https://support.microsoft.com/en-us/kb/2897632

    https://support.microsoft.com/en-us/kb/288759
    Download link (I downloaded the v2 version): https://www.microsoft.com/en-us/download/details.aspx?id=41076

    These are the relevant erros i have on the application eventlog 

    wininit 1015

    application error 1000

    Nom de l’application défaillante lsass.exe, version : 6.3.9600.17415, horodatage : 0x545042fe
    Nom du module défaillant : KERNELBASE.dll, version : 6.3.9600.18340, horodatage : 0x57366075
    Code d’exception : 0xe0010004
    Décalage d’erreur : 0x0000000000008a5c
    ID du processus défaillant : 0x260
    Heure de début de l’application défaillante : 0x01d2809181aff7ae
    Chemin d’accès de l’application défaillante : C:\Windows\system32\lsass.exe
    Chemin d’accès du module défaillant: C:\Windows\system32\KERNELBASE.dll
    ID de rapport : cf9c22bb-ec84-11e6-80f3-00155d1ec103

    These are the relevant erros i have on the system eventlog 

    LSA (LsaSrv) 6038

    Service Control Manager 7038

    Windows Remote Management 10154

    I will kepp you informed of progress.

    Sincerely,

    Marc

    Monday, February 6, 2017 5:24 PM
  • Hello Guys Marc here,

    I unistall all the updates that were installed the day before the crash. And guess what I still have the problem.
    And then i have to competely switch off the server and disconect the powersuply for about 10 minutes then restart the server without the ethernet cable  and only when windows is started i reconnect the ethernet wired an then miracusly i get back my rdp and my windows longon normaly.

    I start to suspect furiously the drivers of the server, i don't know how they'll got compromise by the updates but i think there is a correlation. 

    I'll get you informated.

    Marc out

    Tuesday, February 7, 2017 4:34 PM
  • Hi Marc Lebel,

    Thanks for your feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 8, 2017 3:15 AM
    Moderator
  • Hello Marc again,

    So here are the evolutions of the problem. I did the drivers updates and in all my servers and guess what!

    It didn't work at all. I still have the problem, so i exclude any material problem of the list of suspects.

    Now i furiously think that i have a problem with active directory. I create à new DC hoping this will do the trick but it didn't.

    The only positive thing it's that i can restart the new DC withtout doing the trick with the ethenet cable.

    So stay tuned for more fun.

    Sincerely yours 

    Monday, February 20, 2017 1:26 PM
  • I have a same problem : 

    Version=1
    EventType=APPCRASH
    EventTime=131926374920521441
    ReportType=2
    Consent=1
    ReportIdentifier=06e9ead0-1e4a-11e9-8214-6c0b8406b117
    IntegratorReportIdentifier=06e9eacf-1e4a-11e9-8214-6c0b8406b117
    NsAppName=lsass.exe
    Response.type=4
    Sig[0].Name=Nom de l’application
    Sig[0].Value=lsass.exe
    Sig[1].Name=Version de l’application
    Sig[1].Value=6.3.9600.17415
    Sig[2].Name=Horodatage de l’application
    Sig[2].Value=545042fe
    Sig[3].Name=Nom du module par défaut
    Sig[3].Value=KERNELBASE.dll
    Sig[4].Name=Version du module par défaut
    Sig[4].Value=6.3.9600.19178
    Sig[5].Name=Horodateur du module par défaut
    Sig[5].Value=5bc006fd
    Sig[6].Name=Code de l’exception
    Sig[6].Value=e0010004
    Sig[7].Name=Décalage de l’exception
    Sig[7].Value=0000000000008e6c
    DynamicSig[1].Name=Version du système
    DynamicSig[1].Value=6.3.9600.2.0.0.272.7
    DynamicSig[2].Name=Identificateur de paramètres régionaux
    DynamicSig[2].Value=1036
    DynamicSig[22].Name=Information supplémentaire n° 1
    DynamicSig[22].Value=5e0f
    DynamicSig[23].Name=Information supplémentaire n° 2
    DynamicSig[23].Value=5e0f72cab33a00ba89b86bb1c4ab2a06
    DynamicSig[24].Name=Information supplémentaire n° 3
    DynamicSig[24].Value=36ca
    DynamicSig[25].Name=Information supplémentaire n° 4
    DynamicSig[25].Value=36ca3578e2e097fb0db5f8f7695eaab7
    UI[2]=C:\Windows\system32\lsass.exe
    UI[5]=Rechercher une solution en ligne (recommandé)
    UI[6]=Rechercher une solution plus tard (recommandé)
    UI[7]=Fermer
    UI[8]=Local Security Authority Process a cessé de fonctionner et a été arrêté
    UI[9]=Un problème est à l’origine du dysfonctionnement de cette application. Windows vous préviendra si une solution est disponible.
    UI[10]=&Fermer
    LoadedModule[0]=C:\Windows\system32\lsass.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[5]=C:\Windows\system32\SspiSrv.dll
    LoadedModule[6]=C:\Windows\system32\SspiCli.dll
    LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[8]=C:\Windows\system32\lsasrv.dll
    LoadedModule[9]=C:\Windows\system32\msvcrt.dll
    LoadedModule[10]=C:\Windows\system32\WS2_32.dll
    LoadedModule[11]=C:\Windows\SYSTEM32\cfgmgr32.dll
    LoadedModule[12]=C:\Windows\system32\MSASN1.dll
    LoadedModule[13]=C:\Windows\system32\NSI.dll
    LoadedModule[14]=C:\Windows\SYSTEM32\samsrv.dll
    LoadedModule[15]=C:\Windows\system32\bcrypt.dll
    LoadedModule[16]=C:\Windows\system32\ncrypt.dll
    LoadedModule[17]=C:\Windows\system32\NTASN1.dll
    LoadedModule[18]=C:\Windows\system32\lsadb.dll
    LoadedModule[19]=C:\Windows\system32\DSPARSE.dll
    LoadedModule[20]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[21]=C:\Windows\system32\CRYPTBASE.DLL
    LoadedModule[22]=C:\Windows\system32\bcryptPrimitives.dll
    LoadedModule[23]=C:\Windows\system32\msprivs.DLL
    LoadedModule[24]=C:\Windows\SYSTEM32\netjoin.dll
    LoadedModule[25]=C:\Windows\system32\negoexts.DLL
    LoadedModule[26]=C:\Windows\system32\cryptdll.dll
    LoadedModule[27]=C:\Windows\system32\kerberos.DLL
    LoadedModule[28]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[29]=C:\Windows\system32\mswsock.dll
    LoadedModule[30]=C:\Windows\system32\msv1_0.DLL
    LoadedModule[31]=C:\Windows\system32\netlogon.DLL
    LoadedModule[32]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[33]=C:\Windows\system32\logoncli.dll
    LoadedModule[34]=C:\Windows\SYSTEM32\powrprof.dll
    LoadedModule[35]=C:\Windows\system32\USERENV.dll
    LoadedModule[36]=C:\Windows\system32\profapi.dll
    LoadedModule[37]=C:\Windows\system32\tspkg.DLL
    LoadedModule[38]=C:\Windows\system32\pku2u.DLL
    LoadedModule[39]=C:\Windows\system32\wdigest.DLL
    LoadedModule[40]=C:\Windows\system32\rsaenh.dll
    LoadedModule[41]=C:\Windows\system32\schannel.DLL
    LoadedModule[42]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[43]=C:\Windows\system32\efslsaext.dll
    LoadedModule[44]=C:\Windows\system32\dpapisrv.dll
    LoadedModule[45]=C:\Windows\system32\ntdsa.dll
    LoadedModule[46]=C:\Windows\system32\bcd.dll
    LoadedModule[47]=C:\Windows\SYSTEM32\winsta.dll
    LoadedModule[48]=C:\Windows\system32\ntdsai.dll
    LoadedModule[49]=C:\Windows\system32\AUTHZ.dll
    LoadedModule[50]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[51]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[52]=C:\Windows\system32\NTDSKCC.dll
    LoadedModule[53]=C:\Windows\system32\ntdsbsrv.dll
    LoadedModule[54]=C:\Windows\system32\NTDSAPI.dll
    LoadedModule[55]=C:\Windows\system32\NTDSATQ.dll
    LoadedModule[56]=C:\Windows\system32\ESENT.dll
    LoadedModule[57]=C:\Windows\system32\VERSION.dll
    LoadedModule[58]=C:\Windows\system32\KdsCli.dll
    LoadedModule[59]=C:\Windows\system32\DSROLESRV.dll
    LoadedModule[60]=C:\Windows\system32\SYSNTFY.dll
    LoadedModule[61]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[62]=C:\Windows\system32\W32TOPL.dll
    LoadedModule[63]=C:\Windows\system32\VSSAPI.DLL
    LoadedModule[64]=C:\Windows\system32\wevtapi.dll
    LoadedModule[65]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[66]=C:\Windows\SYSTEM32\combase.dll
    LoadedModule[67]=C:\Windows\system32\WDSCORE.dll
    LoadedModule[68]=C:\Windows\system32\VssTrace.DLL
    LoadedModule[69]=C:\Windows\system32\DSROLE.dll
    LoadedModule[70]=C:\Windows\system32\ntdsmsg.dll
    LoadedModule[71]=C:\Windows\system32\netutils.dll
    LoadedModule[72]=C:\Windows\system32\KDCPW.DLL
    LoadedModule[73]=C:\Windows\system32\rassfm.DLL
    LoadedModule[74]=C:\Windows\system32\scecli.DLL
    LoadedModule[75]=C:\Windows\system32\wkscli.dll
    LoadedModule[76]=C:\Windows\system32\kdcsvc.dll
    LoadedModule[77]=C:\Windows\SYSTEM32\secur32.dll
    LoadedModule[78]=C:\Windows\System32\rasadhlp.dll
    LoadedModule[79]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[80]=C:\Windows\system32\dssenh.dll
    LoadedModule[81]=C:\Windows\SYSTEM32\gpapi.dll
    LoadedModule[82]=C:\Windows\System32\cryptnet.dll
    LoadedModule[83]=C:\Windows\system32\ole32.dll
    LoadedModule[84]=C:\Windows\system32\GDI32.dll
    LoadedModule[85]=C:\Windows\system32\USER32.dll
    LoadedModule[86]=C:\Windows\SYSTEM32\kernel.appcore.dll
    LoadedModule[87]=C:\Windows\system32\samcli.dll
    LoadedModule[88]=C:\Windows\system32\SAMLIB.dll
    LoadedModule[89]=C:\Windows\SYSTEM32\clbcatq.dll
    LoadedModule[90]=C:\Windows\system32\es.dll
    LoadedModule[91]=C:\Windows\system32\PROPSYS.dll
    LoadedModule[92]=C:\Windows\system32\pwdssp.dll
    LoadedModule[93]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[94]=C:\Windows\system32\rpchttp.dll
    LoadedModule[95]=C:\Windows\system32\pcwum.dll
    LoadedModule[96]=C:\Windows\system32\certpoleng.dll
    LoadedModule[97]=C:\Windows\system32\srvcli.dll
    LoadedModule[98]=C:\Windows\system32\cscapi.dll
    LoadedModule[99]=C:\Windows\system32\WINBRAND.dll
    LoadedModule[100]=C:\Windows\system32\MPR.dll
    LoadedModule[101]=C:\Windows\system32\dhcpcsvc6.DLL
    LoadedModule[102]=C:\Windows\system32\dhcpcsvc.DLL
    FriendlyEventName=Fonctionnement arrêté
    ConsentKey=APPCRASH
    AppName=Local Security Authority Process
    AppPath=C:\Windows\system32\lsass.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=8102D8877E41CC9ABDB06D18FC7E6609

    Do you have a solution ?

    Tuesday, January 22, 2019 4:14 PM
  • Hi,

    Do you have teaming enabled in your Hyper-v.

    If yes break the teaming an try with the individual Ethernet card.

    Thanks

    Syed Abdul Kadar M.


    Dont forget to mark as Answered if you found this post helpful.

    Wednesday, January 23, 2019 7:02 PM
  • Hi,

    I don't have enabled Hyper-V.

    Best Regards.

    Friday, January 25, 2019 10:55 AM
  • Hello,

    We installed a new 2016 server with an ISO retrieved from the Microsoft site.

    US language installed.

    All updates have been installed.

    Network change in static, and DNS.

    Renaming the machine, putting in the domain.

    Installation role AD-DS, promote.

    Restart.

    Error again:

    Faulting application name: lsass.exe, version: 10.0.14393.2580, time stamp: 0x5bbdaebc
    Faulting module name: msvcrt.dll, version: 7.0.14393.2457, time stamp: 0x5b7e2c5b
    Exception code: 0xc0000005
    Fault offset: 0x0000000000073f80
    Faulting process id: 0x210
    Faulting application start time: 0x01d4b7ad91b668cb
    Faulting application path: C:\Windows\system32\lsass.exe
    Faulting module path: C:\Windows\System32\msvcrt.dll
    Report Id: ae1be24a-1dda-4d6b-a479-056316fdbb8b
    Faulting package full name: 
    Faulting package-relative application ID: 

    ------------------------------------------------------

    Fault bucket , type 0
    Event Name: CriticalProcessFault2
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: lsass.exe
    P2: 10.0.14393.2580
    P3: 5bbdaebc
    P4: msvcrt.dll
    P5: 7.0.14393.2457
    P6: 5b7e2c5b
    P7: c0000005
    P8: 0000000000073f80
    P9: 00000000
    P10: 0x00000000

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_lsass.exe_8fc374e468b3abcb5ba9dab30dcb449a29f7eae_9d5d5d34_0f133e23

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: ae1be24a-1dda-4d6b-a479-056316fdbb8b
    Report Status: 4
    Hashed bucket: 

    ------------------------------------------------------

    A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005.  The machine must now be restarted.

    Tuesday, January 29, 2019 9:23 AM