[cifs-protocol] [REG:111063044753520] Unable to dcpromo windows with a Samba4 DC

Hongwei Sun hongweis at microsoft.com
Thu Jun 30 10:31:00 MDT 2011


   When the process being trace exits , the trace file will be saved.  So in your case, when you see the error message and you fail to login, do a reboot so the lsass process will exit during reboot.   Once rebooted,  you can then  get the trace file generated from the machine.


-----Original Message-----
From: Matthieu Patou [mailto:mat at samba.org] 
Sent: Thursday, June 30, 2011 11:13 AM
To: Hongwei Sun
Cc: pfif at tridgell.net; cifs-protocol at samba.org; tridge
Subject: Re: [REG:111063044753520] [cifs-protocol] Unable to dcpromo windows with a Samba4 DC

Hi Hongwei,

> Moving dochelp to bcc
> Hi, Matthieu,
>     The following is the instruction:
>      1.     Run "TTTracer -persistent lsass.exe".
>            This will trace lsass.exe each time it starts until you run "TTTracer -delete lsass.exe".
>     2. Reboot machine, lsass trace will start automatically.
>     3.  Run "TTTracer -stop all"  to stop all tracing on my system.  Trace files are written to the disk.
Will tttracer put trace on disk on reboot in anycase ? because the issue is that the windows server can't really boot in normal mode. On 2003 I've got a popup saying that the lsass.exe had a problem but then no more information and also I'm unable to log in.


More information about the cifs-protocol mailing list