
Signature
Kumar Reddi
http://kumarreddi.blogspot.com
Thanks everybody,
The command line registrations did not work at all, however:
I worked under the "Safe Mode", uninstalled IIS, then under the normal mode
uninstalled the framework.
Then rebooted, Installed the IIS in normal mode, again rebooted and under
the normal mode installed the framework. Then rebooted and through the
"Internet Information Services" control bar, configured server extensions,
then rebooted and... wow...that was all!
Now it just works fine, but God! It really wasted my time (5 hours) just to
create an .aspx page.
I think many others have the same problem, so my experience might be a great
aim for them.
Thanks again.
> Try running the following commands
>
[quoted text clipped - 21 lines]
>>
>> Thanks for any help
Flip - 06 Dec 2004 15:03 GMT
> I think many others have the same problem, so my experience might be a great
> aim for them.
It's a bit late now to test this out as your server is back up and running,
but maybe someone else can comment on this. I to had what sounds to be a
similar problem, but mine turned out to be I had stopped the Sharepoint
webapp and the application pool as well for that web app. Even when I
started the webapp (a few days after I stopped it, so I forgot about the app
pool), VS still couldn't connect. After a bit more curse words and a coffee,
I looked at the application pool, started it and I was back to the races.
re wasted your time (5h) just to create an aspx
hhmmm? I have had 5d just to get a JSP working under a daemon in linux. :<
Talk about being a bad setup. :< The 5h is rough I agree, but I hope that's
the last of the big hiccups like that. With my j2ee server, I ran into that
kind of crap ALL THE TIME! :< I'm getting a lot more sleep now and not
pulling my hair out with .NET!
Keep it up, you'll get it yet! :