*****UNABLE TO MAP THE DEBUG START PAGE URL TO A MACHINE NAME - HELL ON EARTH - PLEASE HELP!!!!!!!!!

[Tom wilson]

I can't get rid of this error. The only reference I can find is this:

1. Debugging through a firewall. Microsoft does not recommend or
support remote
ASP.Net debugging through a firewall. The best way to do overcome
this is use
Terminal Services to log into the remote server and debug locally.

No firewall between me and the server.

2. One common failure for RPC is the inability to resolve the remote
machine
name. RPC relies on name resolution for communication between
machines. If
you are unable to resolve the remote servers machine name to the
correct IP
address errors may occur.

Resolves fine, RPCPing returns "Completed 1 calls in 1 ms"

3. RPC Traffic can flow in one direction but not the other. RPC
traffic must be
able to go from the machine used to do the debugging to the remote
server and
from the remote server back to the machine used to do the debugging
in order
to successfully debug remotely. Make sure that RPC communication is
enabled
in both directions.

Make sure it's enabled in both directions. Thanks for indicating how
to do that.

Here's more of what I've been through, it's the most popular search
result for this error on the web. With no answer:

"Are you running a version of Windows that allows the Visual Studio
debugger to automatically attach to a Web application?"

Who knows, the help doesn't indicate how I'm supposed to know.

"Does your Web application have a Web.config file?"

Yes, debug is set to true

"Does the Web.config file contain any syntax errors?"

No, it's fine

"You need to be a member of the Administrators group if..."

I am logged in as the domain administrator with full privs.

"Did you create the project by specifying a specific IP address"

No, http://www.server.com/MyaApp, the recommended method

"Does the machine running IIS server have Visual Studio .NET Remote
Components installed? "

Who knows? The article doesn't indicate how to tell. (thanks)

"Were the proper setup programs run to install ASP.NET or ATL Server
and remote debugger components on the server? "

Again, how am I supposed to know? I installed the full VS.Net 2003
package on the server and workstation.

"Are you using Terminal Server to try to debug a Web application on a
remote machine?"

no.

"When you install Visual Studio .NET on Windows Server 2003, ASP.NET
is not enabled by default. To develop Web projects, you must run the
Security Lockdown Wizard after completing Visual Studio .NET Setup."

Downloaded it and it refuses to install on a W2003 server.

"To configure IIS after running setup on Windows Server 2003
From the Start menu, choose All Programs.
Choose Administrative Tools and then choose Internet Information
Services.
Right-click your machine name in the left pane and choose Security. "

*smashes head on desk repeatedly* There is no such option in IIS
manager and the lockdown wizard will not install. (I hate MS
documents)

- The web site has FP extensions installed and working
- It is defined as an application
- Directory security is set to Windows authentication only, anonymous
access enabled
- The .aspx application works no problem, detailed error messages are
being reported by the browser.
- There's a valid web.config with debug set to true
- Web server extensions include asp.net debugging
- Debugging is enabled within the project

Another route is to try and attach manually:

To manually attach

"Start the application without debugging. (From the Debug menu, choose
Start Without Debugging.) "

No problem.

"Attach to the appropriate IIS process or worker process. By default,
inetinfo.exe for ATL Server applications or aspnet_wp.exe for ASP.NET
applications (w3wp_wp.exe for ASP.NET applications under Windows
Server 2003). "

On which machine? Mine or the server? I go into Debug/Processes. It
shows me all process running on my machine. inetinfo.exe or
w3wp_wp.exe do not exist in the list. So I enter the server name. A
list of processes shows up and there's inetinfo. I choose it and
click Attach:

"Unable to attach to the process. The process does not have
sufficient privileges to be debugged."

I can't find any reference to this error at all. Google returns
nothing relevant.

I'm at a non-productive dead end with no solution. I just don't know
what to do. I've read them all and tried it all. Postings of this
problem in this newsgroup have gone ignored every time. I'm pulling
my hair out.

What can I do? I REALLY REALLY REALLY need this to work, weeks and
weeks ago when I began this nightmare.

Thanks!

 

[Roy]

Good lord, I recommend switching careers to something more calming,
like basket-weaving or somesuch...

Barring that, in reference to those times above where you answered your
own questions with "I don't know, how am I supposed to know?" I
recommend you contact MS customer support. That's what they're there
for.

Have nothing else to offer.

 

[Jeremy S]

This group is only ONE of many of your options.

If you have to resolve it, you can always go for the paid technical support.
Once you pay the fee, Microsoft will work with you until it is resolved. My
company has gone that route a number of times on urgent or exotic technical
issues and has generally had *very* positive experiences.

This group is filled with your peers - people who don't know everything and
aren't responsible for Microsoft products. So, if you are having a
particularly exotic problem, then odds are that no one else has encountered
it either, and will not be able to help.

-HTH