Debugging

[ats@jbex]

I am using VS 2005 on an XP machine (development environment). This is a
recently built machine and I cannot debug my projects. I get teh following
error:

Unable to start debugging on teh web server. The server committed a
protocol violation. Section=ResponseHeader Detail+CR must be followed by LF

Click Help for more information.

There is no HELP button on teh error message just an OK. Before I changed
machines, the debugging worked perfectly.

Any help greatly appreciated.

TIA
--
ats@jbex

The world is my expense
The cost of my desire
Jesus blessed me with its future
And I protect it with fire

Rage Against The Machine - Sleep Now In The Fire

 

[Andrew Morton]

Is the web server on the same machine?

If you go into IIS Manager and get the properties for the web site, is there
anything strange in the Custom HTTP Headers?

Does an ordinary .html page get served correctly from the same web server?
You can use WFetch from the MS IIS Diagnostics toolkit to see the headers.

Or are you using the VS web server?

Andrew


p.s.

I get teh...
Unable to start debugging on teh ...
...on teh error message ...

Too much time on teh [sic] icanhascheezburger site ?

 

[Phill W.]

I am using VS 2005 on an XP machine (development environment). This is a
recently built machine and I cannot debug my projects. I get teh following
error:

Unable to start debugging on teh web server. The server committed a
protocol violation. Section=ResponseHeader Detail+CR must be followed by LF

Try navigating to the project Url directly in your favourite web browser
- you might get something a little more useful (like a sensible error
message) to look at.

Failing that, you'll have to open up the web server logs and see what it
thinks it's doing.

HTH,
Phill W.

 

[ats@jbex]

Is the web server on the same machine?

If you go into IIS Manager and get the properties for the web site, is there
anything strange in the Custom HTTP Headers?

Does an ordinary .html page get served correctly from the same web server?
You can use WFetch from the MS IIS Diagnostics toolkit to see the headers.

Or are you using the VS web server?

Andrew


p.s.

Web server is on the same machine.
In the Custom HTTP Headers the following appears twice:
X-Powered-By ASP.NET
Could this be causing the problem?
A standard html page serves up OK from a browser. Not sure what you mean
exactly by 'using the VS web server'. I click on debug in the IDe and get
the error message I mentioned. If I browse to teh site using the browser it
works fine, I just can't debug it.
--
ats@jbex

I'm not gonna be taken in
They said if I don't join I just can't win
I've heard that story many times before
And every time I threw it out the door

SLF - Wasted Life

 

[Andrew Morton]

[Responses in-line]

Web server is on the same machine.

In the Custom HTTP Headers the following appears twice:
X-Powered-By ASP.NET
Could this be causing the problem?

That isn't usual. Simply delete the custom headers to eliminate that
possibility.

A standard html page serves up OK from a browser.

The browser may be ignoring errors. WFetch would show you everything.

Not sure what you
mean exactly by 'using the VS web server'.

VS comes with a web server of its own ("Cassini") for development use.

I click on debug in the
IDe and get the error message I mentioned. If I browse to teh site
using the browser it works fine, I just can't debug it.

Also, you could use Wireshark to see the actual Ethernet packets to find out
exactly what request is evoking the erroneous response.

Andrew

 

[ats@jbex]

[Responses in-line]

Web server is on the same machine.

In the Custom HTTP Headers the following appears twice:
X-Powered-By ASP.NET
Could this be causing the problem?

That isn't usual. Simply delete the custom headers to eliminate that
possibility.

A standard html page serves up OK from a browser.

The browser may be ignoring errors. WFetch would show you everything.

Not sure what you
mean exactly by 'using the VS web server'.

VS comes with a web server of its own ("Cassini") for development use.

I click on debug in the
IDe and get the error message I mentioned. If I browse to teh site
using the browser it works fine, I just can't debug it.

Also, you could use Wireshark to see the actual Ethernet packets to find out
exactly what request is evoking the erroneous response.

Andrew

Thanks for the info. I will try them all.
--
ats@jbex

I'm not gonna be taken in
They said if I don't join I just can't win
I've heard that story many times before
And every time I threw it out the door

SLF - Wasted Life

 

[ats@jbex]

[Responses in-line]

In the Custom HTTP Headers the following appears twice:
X-Powered-By ASP.NET
Could this be causing the problem?

That isn't usual. Simply delete the custom headers to eliminate that
possibility.

Deleted this and it gave a different error message. Found the answer I
needed for this one on Google. I can now debug the site

--
ats@jbex

What we don't know keeps tha contracts alive an movin'
They don't gotta burn tha books they just remove 'em
While arms warehouses fill as quick as tha cells
Rally round tha family, pockets full of shells

Rage Against The Machine - Bulls On Parade

 

[Andrew Morton]

[Responses in-line]
In the Custom HTTP Headers the following appears twice:
X-Powered-By ASP.NET
Could this be causing the problem?

That isn't usual. Simply delete the custom headers to eliminate that
possibility.

Deleted this and it gave a different error message. Found the answer I
needed for this one on Google. I can now debug the site

Glad it helped!

Incidentally, for anyone reading this thread in the future, could you let us
know what the new error message was and perhaps a link to the solution?

Andrew

 

[ats@jbex]

On Fri, 12 Sep 2008 13:17:13 +0100, Andrew Morton wrote:

[Responses in-line]

In the Custom HTTP Headers the following appears twice:
X-Powered-By ASP.NET
Could this be causing the problem?

That isn't usual. Simply delete the custom headers to eliminate that
possibility.

Deleted this and it gave a different error message. Found the answer I
needed for this one on Google. I can now debug the site

Glad it helped!

Incidentally, for anyone reading this thread in the future, could you let us
know what the new error message was and perhaps a link to the solution?

Andrew

The error said something about not being able to run the Debugger because
Integrated Windows Authenticationwas not set. I had a look and it was. When
I googled the problem, it appears that I needed to uncheck the Allow
Anonymous Access for it to work.
--
ats@jbex

Those who died are justified, for wearing the badge, they're the chosen
whites
You justify those that died by wearing the badge, they're the chosen whites

Rage Against The Machine - Killing In The Name