467,905 Members | 1,714 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,905 developers. It's quick & easy.

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

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.
--
Dan
Jul 21 '05 #1
  • viewed: 3399
Share:
2 Replies
Please Ignore, I found it.

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

Thanks,
Dan

"Daniel" <dh******@data2you.net> wrote in message
news:ul**************@TK2MSFTNGP10.phx.gbl...
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.
--
Dan

Jul 21 '05 #2
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....
"Daniel" <dh******@data2you.net> wrote in message news:Os**************@TK2MSFTNGP09.phx.gbl...
Please Ignore, I found it.

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

Thanks,
Dan

"Daniel" <dh******@data2you.net> wrote in message
news:ul**************@TK2MSFTNGP10.phx.gbl...
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.
--
Dan


Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by VB Programmer | last post: by
1 post views Thread by serge calderara | last post: by
1 post views Thread by AVL | last post: by
1 post views Thread by ankit | last post: by
3 posts views Thread by דורון חסידים | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.