Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

CAN'T DEBUG ASP.NET APP IN VISUAL STUDIO.NET 2003

Error while trying to run project: Unable to start debugging on the web server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running
in the process before attaching.

I've created a local user, member of the local administartors & debugger users group for testing - so I don't think it's a permissions thing. I've repaired the Dot Net Framework and opened up permissions in IE and
IIS.

Per Microsoft's Knowledge base, I did try restarting IIS, which did not help. I don't think IIS is the problem as IIS is running since I can open IE and simply run the web app. I just can't debug. The web folder configuration is standard: anonymous with Integrated authentication. I've reinstalled the DN Framework and registered ASP.NET using ASPNET_REGIIS -i. I've also tried logging in as a local user who is a member of the local administrators & debugger users groups.  All other settings and installs are default.

Any ideas?

Thanks -
0
the_keithm
Asked:
the_keithm
3 Solutions
 
madspireCommented:
0
 
cb1393Commented:
What version of windows are you running?
0
 
cb1393Commented:
>> What version of windows are you running?
On the web server, that is.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
the_keithmAuthor Commented:
Madspire,

Thanks, but after running that fix - same error. I've uninstalled DBF 1.0 & 1.2.
Reregistered msordbi.dll & reregistered ASP.NET: aspnet_regiis -i.


CB, - I'm running Win XP Pro, SP1
0
 
cb1393Commented:
I'm assuming you also installed the .NET server components? Other than that, dunno.
0
 
jitgangulyCommented:
I had the same problem and it was on win2003 server. But I had only .net framework sdk on the server and not VS.net or anything. I can debug my local app (on my local web server) easily but cannot from server and my last bet would be use VS.net/.net framework  disk to install and play around it. Since its a Production I am hesitant to install VS.net , but I do not have any choice.

I would just suggest you to install .net framework and required component from VS studio disk/.net framework disk.
0
 
the_keithmAuthor Commented:
Well, I 've tried all of the suggestions here, but I'm still stuck - thanks for the attempts guys. points will be split.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now