Help, can't run ASP.Net Application...FRUSTRATED!!

  • Thread starter Thread starter Daniel
  • Start date Start date
D

Daniel

Ok folks, I have Windows XP. I installed .Net and developed some VB.Net
components that I want to use in ASP.Net applications.

At this point I realized I didn't have IIS installed on my XP machine, so I
installed it. I then created a ASP.Net web project pointing to "localhost".

I was able to run the application and get to the test.aspx page in the
browser. However, it would not let me debug the application. It kept
throwing an error, and I tried everything the help page suggested. Then I
read further down the same help page that IIS should be installed before
installing .Net. So needless to say I was annoyed but it was my fault so I
grudgingly attempted to "repair" it as the help page suggested. I did so,
but it still didn't debug. So I then tried to "repair" it with the option
from the .Net Setup CD. I did so (it took an hour and a half), but it still
didn't allow me to debug the .Net application.

So I figured I just needed to completely remove .Net and start from scratch.
I removed the Enterprise Architech as well as the .Net Framework and
rebooted (that alone took about 30 mins). I then installed .Net again
(which took around an hour). After all this, I created another ASP.Net
application on my local machine.

Now, not only can I not debug the app but it won't even run. Instead I get
a "Server Application Unavailable" page telling me to look in the event log
to see what's wrong. The problem is there is no entry in the event log.
After 3 Hours of watching different progress bars
installing/uninstalling/repairing I'm worse off than when I started.
 
Please Ignore, I found it.

It was username attribute on the processModel tag in machine.config file.

Thanks,
Dan
 
Don't you just love these newsgroups - they help solve just about any problem, even if it is just blowing off some steam, then
finding the problem yourself.... Amazing what a fresh look can do....


Please Ignore, I found it.

It was username attribute on the processModel tag in machine.config file.

Thanks,
Dan
 
Back
Top