Re: ADAM logging
From: Dmitri Gavrilov [MSFT] (dmitrig_at_online.microsoft.com)
Date: 11/05/04
- Next message: Andy Barkl: "Re: Where is Group Policy Management console?"
- Previous message: theodolite: "Inter Forest Migration"
- In reply to: Lee Flight: "Re: ADAM logging"
- Next in thread: Rich Riopel: "Re: ADAM logging"
- Reply: Rich Riopel: "Re: ADAM logging"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 4 Nov 2004 21:43:32 -0700
Logging every query into a file would probably be too expensive perf-wise.
We have some tracing capabilities with ETW, AD Perf Advisor uses this. But
we don't log the complete query, afaik.
-- Dmitri Gavrilov SDE, Active Directory Core This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Lee Flight" <lef@le.ac.uk-nospam> wrote in message news:OoiuYGtwEHA.1404@TK2MSFTNGP11.phx.gbl... > Thanks for the heads up, in the absence of better info. I have a tendency > to bounce the service after changes. > > I agree this method of diagnosis is a last resort hack and wherever possible > prefer a network sniff. > > Would logging of the unparsed LDAP client query be difficult to do inside of > AD,ADAM as an enhancement? > > Thanks again > Lee Flight > > "Dmitri Gavrilov [MSFT]" <dmitrig@online.microsoft.com> wrote in message > news:%23XamABswEHA.3908@TK2MSFTNGP12.phx.gbl... > > He does not need to restart, actually. Diagnostics regkey values are > > picked > > up automatically, we register a registry callback. The same applies to the > > stuff in Parameters key. > > > > Note these event will only be logged for successful searches. If you fail > > to > > authenticate, and the search base is invisible to you, then no search is > > performed. > > > > The most reliable way to diagnoze the problem is to take a network sniff. > > > > -- > > Dmitri Gavrilov > > SDE, Active Directory Core > > > > This posting is provided "AS IS" with no warranties, and confers no > > rights. > > Use of included script samples are subject to the terms specified at > > http://www.microsoft.com/info/cpyright.htm > > > > "Lee Flight" <lef@le.ac.uk-nospam> wrote in message > > news:#2KZUkrwEHA.3492@TK2MSFTNGP11.phx.gbl... > >> Hi > >> > >> did you restart the ADAM instance after you made the change? > >> > >> Lee Flight > >> "Rich Riopel" <Rich Riopel@discussions.microsoft.com> wrote in message > >> news:AC609DDA-0E85-4E6F-B2B7-75A1BA2CA724@microsoft.com... > >> > Hi, > >> > > >> > I have tried setting field engineering to 5 and Expensive Search > >> > Results > >> > Threshold to 1 but I still do not get any loggin to the eventlog. I am > >> > hoping to find a way to view queries as they come in to the directory > >> > in > >> > order to trouble shoot an issue like tailing the slapd log in openldap. > >> > > >> > Thanks. > >> > Rich > >> > > >> > "Lee Flight" wrote: > >> > > >> >> Here's what I use when network sniffing is not an option. > >> >> > >> >> Use at your own risk. > >> >> > >> >> Diagnostic LDAP Query logging for the ADAM: > >> >> ------------------------------------------------------ > >> >> > >> >> WARNING: Diagnostic logging can be verbose and degrade > >> >> performance on a production ADAM instance. > >> >> > >> >> This requires some registry changes so bear in mind the > >> >> usual WARNING about editing the registry: > >> >> > >> >> Assuming that your ADAM instance has service name ADAM_instance1 > >> >> then under: > >> >> > >> >> > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_instance1\Diagnost > > ics > >> >> > >> >> Edit the value > >> >> > >> >> 15 Field Engineering > >> >> > >> >> and set it to 5 > >> >> > >> >> Then create a DWORD registry key under > >> >> > >> >> > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_instance1\Paramete > > rs\ > >> >> > >> >> Expensive Search Results Threshold REG_DWORD 0x1 > >> >> > >> >> Stop and Start the ADAM instance > >> >> > >> >> Run a search. You should see messages in the ADAM Instance > >> >> log of the system Event viewer in the category Field Engineering. > >> >> Look for an event id 1644 > >> >> > >> >> REMEMBER to reset the registry value > >> >> > >> >> > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_instance1\Diagnost > > ics > >> >> > >> >> 15 Field Engineering > >> >> > >> >> to 0 and to delete the DWORD registry key > >> >> > >> >> Expensive Search Results Threshold > >> >> > >> >> under > >> >> > >> >> > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_instance1\Paramete > > rs > >> >> > >> >> when done. > >> >> > >> >> -- > >> >> Lee Flight > >> >> > >> >> "Greg Martin" <gmartin@gmartin.org> wrote in message > >> >> news:ONpUh0stEHA.1720@TK2MSFTNGP14.phx.gbl... > >> >> > I'm trying to get ADAm to log more information about ldap queries in > >> >> > order > >> >> > to diagnose an integration issue. i found the Diagnostics key in > >> >> > the > >> >> > registry and have set tho LDAp Interface Events key to 0xffffffff > >> >> > but > >> >> > while > >> >> > it is logging some information it seems to only log failed results. > >> >> > I'm > >> >> > looking for the "original" query or as much as I can find out about > > it. > >> >> > > >> >> > Any help or reference would be appreciated > >> >> > > >> >> > Thanks > >> >> > \\Greg > >> >> > > >> >> > > >> >> > >> >> > >> >> > >> > >> > > > > > >
- Next message: Andy Barkl: "Re: Where is Group Policy Management console?"
- Previous message: theodolite: "Inter Forest Migration"
- In reply to: Lee Flight: "Re: ADAM logging"
- Next in thread: Rich Riopel: "Re: ADAM logging"
- Reply: Rich Riopel: "Re: ADAM logging"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
