Discussion:
Can't Run in Debug Mode - Max request length??
(too old to reply)
PJ
22 years ago
Permalink
I'm at the end of my rope, I've tried everything I can think of and, while
the problem is all over google, no answer has worked for me. I'm getting
the following error while trying to start my web project in debug mode.

"Error while trying to run the project: Unable to start debugging on the web
server. Could not start ASP.NET or ATL Server debugging. Verify that
ASP.NET or ATL Server is correctly installed on the server. Would you like
to disable future attempts to debug ASP.NET pages for this project?"

It was working fine yesterday. I am running W2k Pro sp3, .NET Framework 1.0
sp2, VS.NET 2002.
I have tried reinstalling the framework and recreating the projects. The
web application is able to run outside of debug mode. I AM able to attach
the debugger to the aspnet_wp, I am just not able to start it in debug mode.
Also, I AM able to start another web application in debug mode without
problems.

I HAVE ALREADY BEEN THROUGH THE CHECKLIST AT
http://gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerproblems.doc

Every project that can be is marked to enable ASP.NET debugging. Does
anyone have any ideas?
I can access the application through the browser normally, but many of the
submits are giving me an error: "Maximum request length exceeded". This is
happening when the HttpWorkerRequest is calling GetEntireRawContent, so it's
we'll before the code hits my page. My current web.config settings for this
are:

<httpRuntime
executionTimeout="1800"
maxRequestLength="524288000"
/>

.5 gig as I am starting to set up large file uploads. I was working w/ an
httpmodule yesterday, but I have since commented it out in the web.config.
Nothing is working...does anyone have any ideas?

~TIA
PJ
PJ
22 years ago
Permalink
well, after spending all day with this, I took out

<httpRuntime
executionTimeout="1800"
maxRequestLength="524288000"
/>

and that solved my problem. I don't understand why, as I have had this
setting for over a week now w/out issue. I need to increase the default
maxRequestLength in order to allow large file uploads. I assume the
debugger just throws it's generic "Unable to start debugging error.." when
an error has occured with the max request length. My question is, why would
the above setting cause a "Max Reuqest Length exceeded" error??

TIA~ PJ
...
http://gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerproblems.doc
...
David Hanson
22 years ago
Permalink
I just encountered this issue as well. I added the <httpRuntime
maxRequestLength="#########" /> setting into my web.config file and I
was unable to run my project in debug mode. After reviewing
documentation on MSDN I was able to resolve the issue.

I made the mistake of thinking the value I passed to maxRequestLength
had to be for the maximum number of bytes, where it is actually
requesting the maximum number of *kilobytes*. As a result, I was
probably passing it a number that was too large for the parameter to
handle. This is the error I received:

"Error while trying to run your project: Unable to start debugging on
the web server. Could not start ASP.NET or ATL Server debugging.

Verify that ASP.NET or ATL Server is correctly installed on the
server."

Once I passed the # of kilobytes instead, my problem was resolved.

I tried using your initial number (524288000) and received the same
error. Once I divided your number by a 1000 (which left: 524288) and
used that instead everything worked fine.

Hope this helps.

David Hanson
RITIX Inc.
...
Rajesh Dalvi
15 years ago
Permalink
Thanks :) You are right, If you exceed certain limit of "maxRequestLength", you will not be able to debug the project. Your article help me to solve that. Keep it Up

From http://www.developmentnow.com/g/51_2003_7_0_0_280472/Cant-Run-in-Debug-Mode--Max-request-length.ht

Posted via DevelopmentNow.com Group
http://www.developmentnow.com/g/

Loading...