Re: Disabling NDR Logging

Tech-Archive recommends: Fix windows errors by optimizing your registry

Do me a favor and check the following in your registry.

HKLM\System\CurrentControlSet\Services\MSExchangeTransport\Diagnostics -
look at the Categorizer value on the right side and see if that value is set
to 7. Per http://support.microsoft.com/?kbid=262308, it indicates that this
value must be set manually via the registry and this is what controls
logging NDR's to the Application log. If it is set to 7 (Field Engineering
diagnostic logging), set it back to 0 (default - no logging).

--
Ben Winzenz
Exchange MVP
MessageOne


"John Hornbuckle" <JohnHornbuckle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C2A5C6E4-6DA3-456D-AB5E-275CAFD0077B@xxxxxxxxxxxxxxxx
> Yeah, I had already checked that. They're all set to "None." Also, I've
> been
> discussing this issue with other Exchange admins on a mailing list I'm on,
> and a number of them experience the same thing.
>
>
>
> "Ben Winzenz [Exchange MVP]" wrote:
>
>> Have you looked at the Diagnostics logging settings on your server?
>>
>> From ESM, server properties, Diagnostics logging tab. Run through all of
>> the logging options and see if any are set. Specifically, you can look
>> at
>> MSExchange Transport and see if NDR logging level is set to anything but
>> None.
>>
>> --
>> Ben Winzenz
>> Exchange MVP
>> MessageOne
>>
>>
>> "John Hornbuckle" <JohnHornbuckle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:B0957BDD-D569-42D4-98CE-B33BB126F4EF@xxxxxxxxxxxxxxxx
>> > Just thought I'd bump this thread up one last time. Surely someone out
>> > there
>> > has some information about this. I've been talking to other Exchange
>> > admins
>> > on another forum, and it's an issue that a lot of people are concerned
>> > about.
>> > Event logs are being filled with useless entries, and no one seems to
>> > know
>> > how to stop it...
>> >
>> >
>> > "John Hornbuckle" wrote:
>> >
>> >> Wow... Not one response! I guess I've stumped everyone. I don't know
>> >> whether
>> >> to be impressed, or disturbed.
>> >>
>> >> Can anyone maybe recommend another forum to which I could pose my
>> >> question?
>> >>
>> >>
>> >>
>> >> "John Hornbuckle" wrote:
>> >>
>> >> > Exchange Server 2003, SP1 on Windows Server 2003.
>> >> >
>> >> > I'm sure I'm just overlooking the obvious, but could one of you tell
>> >> > me
>> >> > how to disable the logging of NDRs in the application log? Or is it
>> >> > not
>> >> > possible to disable it? Or would it be a bad thing to do so, even if
>> >> > it
>> >> > were possible?
>> >> >
>> >> > I just don't see the sense in filling up my app log with NDRs, but
>> >> > maybe
>> >> > I'm not considering some useful benefit of this logging...
>>
>>
>>


.

Relevant Pages

  • Re: Disabling NDR Logging
    ... >>> Have you looked at the Diagnostics logging settings on your server? ... >>> From ESM, server properties, Diagnostics logging tab. ... >>> Exchange MVP ...
    (microsoft.public.exchange.admin)
  • Re: Quick Launch - Show More Icons
    ... Tim Meddick wrote: ... What I mean by logging off / logging back on has got nothing to do ... logoff your CURRENT USER. ... when you change the registry directly - this often does not ...
    (microsoft.public.windowsxp.general)
  • Re: Quick Launch - Show More Icons
    ... What I mean by logging off / logging back on has got nothing to do with network ... Although the same terminology is used to describe the 'logging' on to the network - ... to see the changes" and they DO NOT mean by that: network connections or internet ... I'm doing it (making the registry changes) *directly* in regedit, ...
    (microsoft.public.windowsxp.general)
  • RE: Events 40960 & 40961
    ... Also Enable WINLOGON LOGGING and USERENV LOGGING ... Start Registry Editor. ... kerberos was "There currently are no logon servers available to service the ... with the server LDAP/server.domain.com. ...
    (microsoft.public.windowsxp.general)
  • Re: Policies being applied to only some machines
    ... entry into the registry on the stubborn computers and sure enough, ... those machines are all complaining that they cannot find or they do ... The 2003's registry shows a combination of 4 different GUID's being ... Thanks for the logging information advice. ...
    (microsoft.public.win2000.group_policy)