This whole thing has already been discussed in this thread:
I have exactly the same scenario as the guy who started this thread - IIS on
a domain controller. Before you start lecturing me on my setup, I am a
professional developer and the reason I have IIS running on a domain
controller is that I have a small development network with a server (domain
controller/web server/SQL Server) and a couple of workstations. The server
also serves as a test deployment server for applications I build for my
customers. This should not be unusual given the population of MSDN members
(of which I am one). I have talked to a handful of them at Microsoft events
who do the same thing.
My server is Win 2003 Server standard, which I upgraded from Win 2000
Server. This in itself was a nightmare and I had to burn one of my 4 support
incidents to get it done. Took two days altogether. I couldn't believe how
badly it went. All of my software comes from my MSDN subscription.
Now I am trying to deploy an ASP.NET 2.0 app to the server from the
development workstation to testbed it.
I have all the same symptoms as discussed in the thread above - no
application pools showing up (they were there when I installed ASP.NET 2.0 on
the Win 2000 server before I upgraded, and now have disappeared), same error
messages in the app log. I did all of the things specified in the KB articles
as well as the stuff recommended in the thread... re-registering asp.net,
setting up special account, setting permissions, ....
The big difference for me is that I put the user account and password in the
machine.config file and it still does not work.
Please do not lecture me about not running IIS on a domain controller. This
is a development environment and it is very tightly secured behind a
firewall. And please, no lame comments from the Linux crowd, OK? We've heard
it all before. When my customers switch to Linux, then maybe I will too.
Until then, I work with what they've got.
Any advice from anybody else out there who has gone through this nightmare
would be greatly appreciated.
Thanks
Robert
I have exactly the same scenario as the guy who started this thread - IIS on
a domain controller. Before you start lecturing me on my setup, I am a
professional developer and the reason I have IIS running on a domain
controller is that I have a small development network with a server (domain
controller/web server/SQL Server) and a couple of workstations. The server
also serves as a test deployment server for applications I build for my
customers. This should not be unusual given the population of MSDN members
(of which I am one). I have talked to a handful of them at Microsoft events
who do the same thing.
My server is Win 2003 Server standard, which I upgraded from Win 2000
Server. This in itself was a nightmare and I had to burn one of my 4 support
incidents to get it done. Took two days altogether. I couldn't believe how
badly it went. All of my software comes from my MSDN subscription.
Now I am trying to deploy an ASP.NET 2.0 app to the server from the
development workstation to testbed it.
I have all the same symptoms as discussed in the thread above - no
application pools showing up (they were there when I installed ASP.NET 2.0 on
the Win 2000 server before I upgraded, and now have disappeared), same error
messages in the app log. I did all of the things specified in the KB articles
as well as the stuff recommended in the thread... re-registering asp.net,
setting up special account, setting permissions, ....
The big difference for me is that I put the user account and password in the
machine.config file and it still does not work.
Please do not lecture me about not running IIS on a domain controller. This
is a development environment and it is very tightly secured behind a
firewall. And please, no lame comments from the Linux crowd, OK? We've heard
it all before. When my customers switch to Linux, then maybe I will too.
Until then, I work with what they've got.
Any advice from anybody else out there who has gone through this nightmare
would be greatly appreciated.
Thanks
Robert