Re: I hate IIS - "Server Application Unavailable" error message

Juan has given you the hangman's noose. Now I am going to inform you why
Juan told you not to do this.

You can get it running on a domain controller by altering this account. The
problem is you now leave a big hole into your domain controller.

Why is this a problem? Well, once someone has control of your domain
controller, they have control of your domain.

And, why is that dangerous? Do you hold ANY secrets. You know, things like
customer's credit cards, you own employee's social security numbers?
Anything like that? Well, you have the potential of leaving it all open for
someone.

Can this really happen? Well, the likelihood is fairly low. It is almost
impossible on a NORMAL web server, but it is a bit more of a risk on web
server that happens to sit on a DC.

Can you mitigate this. Certainly. Buy a web server.

Here is the bottom line. Is it less risky to tell the person forcing you to
do this to buy a web server or to have your customer's data stolen (and
perhaps your own) or to risk you job telling your boss he needs to spend a
few thousand on a web server? If the later, then find a better job. And, if
it is you that is the boss deciding you need to risk your whole business
over a couple of thosand dollars, then I am wating my time.

Don't put your web server on a DC ... EVER.

Nuff said. If you ignore this, you can take Juan's "fix" and hang yourself.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************
"Kevin Liebowicz" <linux-sux@xxxxxxxxx> wrote in message
news:1183424160.094676.21830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yes, I wasted the past two days trying to fix this.
Yes, this is on a Win2003 Server.
Yes, this machine is a domain controller.

Yes, I seen the dozens of KB articles like this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315158

But the problem is that 99% of these are for ASP .NET 1.x and this
is .NET 2.x which I just installed to try and get .net working for the
first time ever. I've see all the HACKS to get .net 1.x working... but
this is for .net 2.x so these worthless KB articles do nothing for me.

Example -
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315158

RESOLUTION
To work around this problem, use one of the following methods: ·
Create a weak account that has the correct permissions, and then
configure the <processModel> section of the Machine.config file to use
that account.
· Set the userName attribute to SYSTEM in the <processModel> section
of the Machine.config file.
· Configure the <processModel> section of the Machine.config file to
use an administrator account.


THIS IS USELESS !!!!! There is no "userName" attribute in the
Machine.config file in .net 2.x. And if this is a known problem then
why doesn't the installer warn me or fix it automatically. Sorry, but
your software sucks lately.!!!!!!!

The event log is filled with messages like:

<quote>
aspnet_wp.exe could not be started. The error code for the failure is
800700CB. This error can be caused when the worker process account has
insufficient rights to read the .NET Framework files. Please ensure
that the .NET Framework is correctly installed and that the ACLs on
the installation directory allow access to the configured account.
</quote>


Sorry Microsoft - But you are getting WORSE and WORSE. How about
software that simply works????

It's no wonder that Linux is kicking your *** and I'm about 30
seconds away from saying goodbye to your over-complicated bug ridden
crap and making the transition to linux myself.


.