ASPNET-Account on a W2KServer Domain Controller

[Michael Maes]

Hello,

I can't get the ASPNET-Account installed on a Windows 2000 (5.00.2195) Server SP4 Domain Controller.
I always receive "Web Server not running ASP.NET version 1.1" when I try to start a APS.NET WebApplication.

"I tried aspnet_regiis.exe -i", I tried to re-install fw v1.1, but the account ASPNET won't get installed.

Any suggestions?

Thanks,

Michael

 

[William]

On Sun, 4 Apr 2004 21:42:04 +0200, "Michael Maes" <[email protected]> typed
and posted to microsoft.public.dotnet.framework.adonet:

Under the .NET Framework 1.1 the identity of the ASPNET process is
IWAM_MachineName. Maybe this is why the <LOCAL_MACHINE_NAME>\ASPNET account
does not exist.

Check this KB article on how to manually remove the .NET framework v1.0 and
repair the .NET Framework v1.1. I am thinking you have a pooched system and
should start from scratch.
http://support.microsoft.com/?id=320112

Hope this helps
Will

 

[Michael Maes]

Hi Will,

I think my problem lies elsewhere: the machine has never had v1.0 installed.
Also, starting from scratch will be difficult, since it's one of the
main-servers.
The only reason ASP.NET has to be on that machine is to be able to run our
Licensing-Software over the internet.

To my best understanding, the IWAM-user & the ASPNET-user are not the same.
Anyway: the IWAM IS installed on the server, but still vs.NET-ASP-App (& the
licensing-software) won't start.

I have just un-installed vs.NET & Framework on the system and re-installed.
The result is the same: no ASPNET-User & Unable to Create ASP.NET Apps

My guess is that, since the server is a Domain Controller, it can't install
the (local) ASPNET- User.

Kind regards,

A "desperate" Michael

 

[Michael Maes]

Sorry, missed the NewsGroup with "one row".
Should have been ...adonet of course.....
Hello,

I can't get the ASPNET-Account installed on a Windows 2000 (5.00.2195) Server SP4 Domain Controller.
I always receive "Web Server not running ASP.NET version 1.1" when I try to start a APS.NET WebApplication.

"I tried aspnet_regiis.exe -i", I tried to re-install fw v1.1, but the account ASPNET won't get installed.

Any suggestions?

Thanks,

Michael

 

[Steven Cheng[MSFT]]

Hi Michael,

Yes, you're right, the problem you encountered is exactly caused by the
Domain Controler which can't have local account such as the
"Machine\ASPNET" installed and the ASP.NET's default process account is
Machine\ASPNET. One resolution is to change the account of the ASP.NET
process in the machine.config file
Generally, you can change it from "Machine\aspnet" to "System". The
following KB article is discussing on this issue:

#FIX: ASP.NET Does Not Work with the Default ASPNET Account on a Domain
Controller
http://support.microsoft.com/?id=315158

Please have a look and try the means to see whether it helps. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Michael Maes]

Hi Steven,

I'm getting "desperate" here: I followed the instructions but the problem
remains the same.
One side-thought: the article is for v1.0 and the server has v1.1 (never had
v1.0).

"Note With ASP.NET 1.1, the identity of the ASPNET process is
IWAM_MachineName, and this problem does not apply. "

I still receive:

"Visual Studio .NET has detected tha the specified Web server is not running
ASP.NET version 1.1. You will be unable to run ASP.NET Web applications or
services."

Also: the IWAM_MachineName - Account IS installed by the DC.

Help!

Michael

 

[William]

Starting from scratch does not always mean rebuilding the server I have
seen others have some kind of luck with the following but for a live production
server should be a last resort.

1) Uninstall IIS from Add/Remove programs
2) Rename metabase.bin (you can find it in
C:\winnt\system32\inetsrv\)
3) Make sure the following accounts are gone...
IWAM_MachineName
IUSR_MachineName
ASPNET
4) Reinstall IIS and reapply latest SP installed
5) Rerun aspnet_regiis -I

Also using the SYSTEM account as another poster mentioned should only be used
to see if the problem is with security and NOT as a resolution. The KB article
will go into setting up an account that has the correct permissions for the ASP
worker account and this should be used.

Will

 

[Steven Cheng[MSFT]]

Hi Michael,

I think the KB is also suitable for ASP.NET1.1 since in IIS ,the process
still run under machine\ASPNET by default. So have you tried setting the
userName attribute to "SYSTEM" in the <processModel> section of the
Machine.config file. Please confirm this first, if it still not work when
the processModel's account is set to "SYSTEM", I'm afraid there've been
some serious corruptions on the server box. Generally, it is not recommend
that we running ASP.NET on a Domain Controller machine.
In addtion, I think you can also have a look at William's suggestions in
the latest reply which is also helpful for repairing the ASP.NET framework.
Anyway, please have a try on them and feel free to post here if you have
any new findings. Thanks.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Michael Maes]

Hi Steven and William,

Sorry if I didn't react immediatly J but I'm currently a bit "drowning in work".
I did try all the steps in the KB (including the System-account).
None of it worked.
I didn't however reboot the server (since it's a production-one). I'm not shure if this needs to be done in such a scenario (the KB didn't mention anything about that).

I contacted our network-guy and he thought that un- & re-installing IIS on a production-server could be a risk.
I now asked him to make an estimate to move our entire IIS-related 'stuff' to another (non-dc) machine.
Still waiting for his reply (busy guy - external)

If you're shure that un- & re-installing IIS (& FW & vs.NET) on a production-server can't pose any problem (risk), then I'm willing to give it a try.....

Kind regards,

Michael

 

[William]

If you have the option of moving your IIS related stuff to another non DC
machine that would be the preferred way to go as you will be able to keep the
production server up at the same time testing and debugging the new IIS server
setup and your web apps as well.

Unfortunately there is always risk involved with un and re-installing anything.
If you or your IT guy has the software then I would suggest doing a serious
backup of the production server like imaging the drives with Ghost or an
equivalent (if the server can be down for an hour or so). That way you have a
snapshot of the server just before you begin. You could do this over a day or
two and minimize the downtime. The biggest risk would be with re-setting up
your existing web apps/sites especially if there are specific setups.

William

 

[Steven Cheng[MSFT]]

Hi Michael,

I agree with William and recommend that move the WebApplication to another
non-DC machine if possbile. Thanks.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Michael Maes]

Hi Steven,
Hi William,

We've discussed this internally and we are indeed going to move all the
Web-Related items to a new (non dc) machine.
That's the most secure thing to do.

Thanks for all your good advice,

Kindest regards,

Michael