RE: EIF: minimal runtime sys permissions (not related to installutil)

From: Mike Hayton [MS] (mikehayt__at_online.microsoft.com)
Date: 09/17/04 

Date: Fri, 17 Sep 2004 17:51:12 GMT

Hi there

Some questions:
a) Is ASP.NET involved?
b) The EI.config contains entries for the RequestEventSources (just
checking - I did see (1) below)
c) You say the event isnt output through the RequestEventSource, it is
still output through the EventSource? i.e. when you raise an event, you
raise it through an EventSource. If there is an active request trace then
EIF automatically also raises through the associated RequestEventSource.

Some things to try:
i) can you make sure that the internalExceptionHandler="report" in the
EI.config file for the event sources. By default raising errors are only
output to the perf counters - when you set this attribute to report, the
error is output to the perf counter and the windows event log. (see the EIF
help under the topic of "Event Sources" (look for InternalExceptionHandler))
ii) Can you use the RequestTracing sample that comes with EIF and reproduce
the same results (i.e. no events in the Windows Event Log (WEL) or Windows
Event Tacing (WTE)?)

I expect i) above will help you. There is also a setting of "throw" that
you can set, but it only works if the EI.config's mode="debug". With
'throw' any exceptions in EIF are not caught and bubble up into the
instrumented app.

If you're still having troubles figuring out where the error is occuring -
try attaching a debugger to ii) above and turning on first chance
exceptions. Note: this will show all exceptions including ones that are
caught and handled - there are a few known exceptions thrown and caught in
validating schema of the EI.config xml.

Cheers

Mike 

-- 
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 
--------------------
| We've been using EIF for awhile and having no trouble with request 
tracing if 
| the app is running as user that has admin access. When we go through 
| hardening of the server, we loose request tracing all together *without* 
any 
| errors/warning logged into the event log. We map the requestfilter to 
both 
| logSink and traceSink -- no messages in eventlog or trace log. If 
temporarily 
| user is added to local admin, all works fine; take the user out of local 
| admin - no tracing.
| 
| To cover the obvious: 
| (1) the eventsources have been pre-registered with installutil
| (2) the app user has read access to 
HKLM/CurrentControlSet/Services/EventLog 
| 
| From poking around:
| (1) regmon trace shows that the app process is getting 'access denied' on 
| HKU/Default/Software/MS/windows/CurrentVersion/Internet Settings and
| and HKLM/Software/Microsoft/SystemCertificates (this might be due to 3rd 
| party dlls we use)
| (2) filemon trace shows nothing of interest (i.e. no access denied on the 
| app process).
| 
| Any ideas? 
| 
| Maros
|

Relevant Pages

  • Re: Writing Files asynchronously
    ... > I have a classic app that uses FSWrite to store text into a file. ... > app will hang indefinitely. ... > So I went looking for a way to kill off the pending I/O request. ...
    (comp.sys.mac.programmer.codewarrior)
  • Re: 500 error while GetResponse()
    ... You would of course need to handle any Exception thrown by this method with ... >> The first would mean that the server that your WebRequest sent a Request ... >> The second would mean that your ASP.Net app has a problem. ... >> ..Net Developer ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Catching NPEs
    ... I have developed an app along these lines. ... Unexpected exceptions are caught and rethrown. ... Request servicing continues, and doesn't even diminish in capacity since the thread that dies is recreated immediately unless it's no longer needed anyway. ... Since it's a network using app, most exceptions are I/O exceptions that get handled closer to the source, usually by sending the client an error message and moving on to the next request; they tend to indicate a problem with connectivity or the client having sent a bad or malformed request that includes a bogus URL, parse error, or similarly. ...
    (comp.lang.java.programmer)
  • Re: Web listener
    ... When the request comes in from CGI the app connects to D3 ... running the web server on the MV server can be/is a security risk. ...
    (comp.databases.pick)
  • Re: 500 error while GetResponse()
    ... This utility is a console app which makes a HTTPRequest to - www.ABC.com ... > that executes the GetResponse method is throwing an error. ... > Server Error." ... > The first would mean that the server that your WebRequest sent a Request to ...
    (microsoft.public.dotnet.framework.aspnet)
Quantcast