For those encountering the 'Error executing child request for...'
error, the following may bring some light on the problem. It is
possible that the page you are transfering/executing to is re-invoking
your handler and producing a recursive relationship.
The following describes an example of the recursive relationship.
________________________________
//snippet from web.config
<httpHandlers>
<add verb="*" path="*.aspx"
type="[namespace.handerclassname],[assmeblyname]"
</httpHandlers>
//snippet from the handler specified above
context.Server.Transfer(somepage.aspx)
________________________________
If your application uses similar config/code logic, then you may
encounter the problem as the transfer may be re-invoking the handler.
I suspect that my statements are correct only because I personally ran
into the problem and by changing the page name to end in something
other than 'aspx' (in my case) solved my problem. However, I can not
say for sure that this 'recursive relationship' is actually the
problem. My originally thinking was that the handler could only be
invoked by 'external' requests and not 'internal' requests initiated by
Server.Transfer/Execute, and therefore, the recursion could not be the
problem. But, maybe there is no distinction between external and
internal requests???
Sorry I can't be more definite!
Could someone from Microsoft confirm/deny this?
