Hi Patrice,
I caught a trace of one of these responses a while back. I cant remember in
depth what it said, but I'm pretty sure it returned a status code 200 even
though it didn't look as if any code has been run (maybe that was because
the application ran on Release assemblies).
I dont think the "empty response" is the result of a caught but unhandled
server exception, since it has happened on almost all of my pages and the
response is the same regardless of the aspx page.
Further more the "empty response" only happens in periods of time, the rest
of the time the pages looks fine.
Anyway, I'll try to check some of our web controls for any bad exception
handling.
Thanks for your time,
Ricky
"Patrice" <no****@nowhere.com> wrote in message
news:Oe**************@tk2msftngp13.phx.gbl...
What entry do you have in the IIS log for these pages ? Especially the
http status code is ok ? For now i can only think of some problem that would be
caught but not handled server side resulting in a missing body ??? Does it
look like you have only the HTML code but not server side controls ? I
would add for example some static HTML code after the body but before the form
tag to make sure it is my static html code that shows up.
If yes, it's likely a server side problem when server side controls are
processed (session expired ?)...
Good luck.
Patrice
"Ricky K. Rasmussen" <mo****@mvponline.dk> a écrit dans le message de
news:eM**************@TK2MSFTNGP12.phx.gbl... No error what so ever... Only an empty page.
So far we've learned to live with it, but it's becomming a big issue for
us.
And even more strange: When we get "The empty Page" it's not enough to
refresh the empty dialog.
We have to refresh the page that opens up the dialog and the try to open
it again.
Could it be because of server load?
/ricky
"Patrice" <no****@nowhere.com> wrote in message
news:#g**************@TK2MSFTNGP11.phx.gbl... No error server side ?
Patrice
