Debugging problems

[Ben]

I am getting the debuggin error: "The breakpoint will not currently be hit.
No symbols have been loaded for this document."

Let me set the background here. Our debugging was working, our network
services group tried to setup debugging without the need for administrator
rights. I got the error above, the error went away. They gave up on the
non-administrator debugging... The error is back.

Let me say this before everyone starts asking about the project.
*The project is in debug mode
*Debug symbols is a selected option
*Not only have I verified the time stamps on the dll and pdb files, I've
deleted them totally forcing a recreation
*This problem spans applications! That's right, I get this error in
http://foo and http://bar
*I've modified the web.config and deleted the dll shadow copy

At this point I just want debugging back. I'd hate to waste a call to MS on
this. It seems like from my searches that this is a semi-common problem.
As I type this, the network services group is trying to reinstall the .net
framework on our server. I'll post an update if that fixes anything.

We are running Windows 2003 server with the 1.1 framework.

Anyone that has or has had this problem, please post any fixes here!

Thanks!
Ben

 

[Ben]

I'm seeing an alarming number of messages saying that the problem could be
to namespace resolution failure. That I should rename my files. It just so
happens that I'm having the problem with you guessed it, default.aspx. I'll
have to try to rename the default.aspx and debug it. Still waiting on the
new framework to be installed. I'll post an update when available.

 

[Steven Cheng[MSFT]]

Hi Ben,

Yes, from my research in some former issues similiar with this, many of
them are also caused by the duplicated file name such as the default.aspx
which cause the debuger unable to find which one to launch. Also there is
another thing you can have a check:

1) Open up the IIS Management Console (Start -> Run -> Type: inetmgr)
2) Right-click on the Default Web Site Tab and choose Properties.
3) Choose the Home Directory Tab.
4) In the Application Settings section, choose the Configuration
Button.
5) Choose the Mappings Tab and ensure that the cache ISAPI
Applications?

In addition, here is a good document on troubleshooting Debugging issues
with web applications in Visual Studio .Net
http://www.gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerpro
blems.doc

Hope also helps. If you have any other findings, please also feel free to
post here.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Ben]

Our network services group called Microsoft to get this problem fixed. The
bottom line was this. On out windows 2003 server the webgarden setting had
been modified from the default of 1. The web garden was appearently
modified in some multiuser debug attempt. It was spawning a new w3wp.exe
for each debug request. VS.Net didn't know which process to attach to.

So, putting webgarden back to 1 fixed the problem. I hope this helps anyone
out there that has a similar problem... Seems like there are several
different versions of this issue...