Solved

aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config f

Posted on 2002-04-10
6
2,266 Views
Last Modified: 2007-11-27
aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.

I need more here than the links that will come up from doing a search for this on Google.com. I really need more a simple step by step explanation of how to fix the problem.

I have tried the those links but either I don't understand something or I am doing something wrong trying to follow them.

If you can help or show me to somewhere than can I would really appreciate it.

Thank you,
Chris Craft
0
Comment
Question by:CJCraft
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 20

Accepted Solution

by:
Silvers5 earned 200 total points
ID: 6931175
By default ASP.NET runs the ASP.NET worker process using a
non-adminitrative windows account called "ASPNET".  This restricts what
an ASP.NET application can do on a machine -- and requires
administrators to explicitly grant security permissions. =20

However, on Windows Domain Controller machines (this includes the
Windows Small Business Server product) the ASPNET account cannot be used
-- since non-administrative local accounts cannot be created and used
(the security policy of a Windows Domain Controller machine prevents
this). =20

If you attempt to use the default ASPNET account when running an ASP.NET
page on a Windows Domain Controller, the worker process will fail to
start -- most likely with an error message similar to the one below:=20

  "aspnet_wp.exe could not be launched because the username and/or
password supplied in the processModel section of the config file are
invalid"

To fix this, it is necessary to configure ASP.NET to instead use the
LocalSystem account after setup.  This is done by modifying the
<processModel> tag within the Machine.Config configuration file
installed in the below location:

   c:\Windows\Microsoft.Net\Framework\V1.0.3705\Config\Machine.Config

By default you will find that the <processModel> configuration tag has a
"userName" attribute set to the value: "MACHINE".  Changing this value
to "SYSTEM" will cause ASP.NET to instead use the LocalSystem account
when executing.  This account *does* have permission to run on Windows
Domain Controllers.

After making the change to the Machine.Config XML file, save it, and
then restart IIS (iisreset).  ASP.NET will then be using the LocalSystem
account to run its worker process, and ASP.NET will function fine on
domain controllers.


you cann add also any other admin account
0
 
LVL 7

Author Comment

by:CJCraft
ID: 6931372
Is there a way I can get it to work without having to give it high level credititials? We are a little uncomfortable about having it run in that context.

I am trying to implement the following:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315158

Thanks again,
Chris Craft
0
 
LVL 23

Expert Comment

by:naveenkohli
ID: 6931558
Unfortunately, there is no workaround this problem right now. MS is under lot of heat because of this issue. As the knowledgebase article suggested, the best of the worst is to create an account that has enough previleges to run ASP.Net service.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 7

Author Comment

by:CJCraft
ID: 6932206
You guys are right I just had to suffer through and do what

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315158
said do, it wasn't that bad after I did it.

Thanks everyone,
Chris Craft
0
 
LVL 23

Expert Comment

by:naveenkohli
ID: 6932237
It seems with this approach, MS is preparing for Windows .NET server family where they are tryig to separate Domain Controllers from Web Servers. Seems like more on the lines of their tightening the secutity policies.
0
 
LVL 2

Expert Comment

by:CUTTHEMUSIC
ID: 6935006
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Hello, all! I just recently started using Microsoft's IIS 7.5 within Windows 7, as I just downloaded and installed the 90 day trial of Windows 7. (Got to love Microsoft for allowing 90 days) The main reason for downloading and testing Windows 7 is t…
I would like to start this tip/trick by saying Thank You, to all who said that this could not be done, as it forced me to make sure that it could be accomplished. :) To start, I want to make sure everyone understands the importance of utilizing p…
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question