Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 420
  • Last Modified:

asp.net doesn't work

Hello experts,
in my environment
- Operating System: Windows 2000 Server
- Internet Information Service 5.0
- Visual Studio .Net
I cannot establish a connection to my IIS using asp.net.
-- IE 6.0 gives the following info:
The server application is not available.
The web application on this web server is currently not available. Please click on 'refresh' to repeat this action.
Administration hint: a more detailed info concerning the error exists in system event protocol of the web server.
-- here is the event protocol info:
aspnet_wp.exe couldn't be started, because the userid and/or the password defined in processModel section in the configuration file are invalid.
--
I checked the file machine.config and found the following related entries:
---
<section name="processModel" type="System.Web.Configuration.ProcessModelConfigurationHandler, System.Web, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineOnly"/>
---
<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000" restartQueueLimit="10" memoryLimit="60" webGarden="false" cpuMask="0xffffffff" userName="machine" password="AutoGenerate" logLevel="Errors" clientConnectedCheck="0:00:05" comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate" responseRestartDeadlockInterval="00:09:00" responseDeadlockInterval="00:03:00" maxWorkerThreads="25" maxIoThreads="25"/>
---
I cannot see what's wrong.

The same application works in the following environment exactly as expected:
- Windows XP Professional
- IIS 5.1
- Visual Studio .Net

Does anyone know what could be wrong?

Thank you HStrix


0
HStrix
Asked:
HStrix
  • 4
  • 4
1 Solution
 
kpkpCommented:
the userName="machine" password="AutoGenerate" in your machine.config mean that the ASP.NET application process will try and login using the user account ASPNET (aspnet_wp account).  Do you have this account defined on your machine?  

It should be created during the installation of .NET.  If it doesn't exist - or someone has changed the password, then the ASP.NET worker process can not start (at least not using the machine.config that you have).

you have a couple of options:

try removing and reinstalling .NET - this should (re)create the ASPNET account and machine.config

try changing the username and password settings in machine.config to an account that does work - or create a new account for the ASP.NET process and change machine.config to use this
0
 
HStrixAuthor Commented:
Thank you,
the user ASPNET did exist.
Nevertheless I created a new user
(for three groups: DebugUser, DomainUser, WebUser).
I changed userName and password to my settings.
But the system still tries to use ASPNET instead of my one.
Do I need to change anything in
--
<section name="processModel" type="System.Web.Configuration.ProcessModelConfigurationHandler, System.Web, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" allowDefinition="MachineOnly"/>
--
as well?
0
 
kpkpCommented:
You should just need to change the userName="" password="" in <processModel>.  I just tried it on my machine, and had to reboot for the changes to take effect.  You could probably just restart some processes to get the same effect - but rebooting should do the trick
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
HStrixAuthor Commented:
OK, I'll set both to empty string and will reboot.
But which user is used in that case?
0
 
kpkpCommented:
No! When I said userName="" password="", I was just letting you know which attributes to change!

Put the correct userid and password in the quotes (i.e. the userid for the new user you created to run the ASP.NET worker process, and the password you specified for it)

- then reboot!  OK, so maybe userName="" password="" was a but misleading
0
 
kpkpCommented:
Also, bear in mind that it's not a very good idea to store password info in any file.  Especially in clear text on a web server.  

Although the machine.config shouldn't be accessable to unautorised users, security holes have been found in the past that allow access to these kind of files.

If this is a production machine, if at all possible, try and get the ASPNET user working again. And put the machine.config back to it's default.  Try removing the account, and uninstalling .net - then reinstall .NET
0
 
naveenkohliCommented:
Incase of WIndows 2000 Server (Domain Controller), the <processModel> info in MAchine.config file needs to be changed. Change it to "SYSTEM" from "machine". This is a known issue for domain controllers.
Following link should give you more details on the process identity.

http://www.gotdotnet.com/team/upgrade/v1/aspnet_account_readme.doc

When you make changes to .config file, there is no need to reboot. You simply need to restart IIS. It will oad the changed .config file into process.

Incase of Windows XP, the process model does not need SYSTEM previlieges, therfore you don't have to make any changes to <processModel> and it works out of the box.

Naveen
0
 
HStrixAuthor Commented:
Thank you,
in the first instance my intension was to get it working under Windows 2000 too.
It is NOT a production environment, I'm using localhost.
But until now, I was not able to get working.
I checked also the permissions for the directories,
and - everything looks fine to me.
-----
In the meantime I looked a little bit around and found the following link:
---
http://support.microsoft.com/default.aspx?id=kb;en-us;Q315158
---
This sounds very familiar to me.
I'll give the information about the result.
0
 
HStrixAuthor Commented:
I've applied all of the information available in the above link.
And - I could make it working.
The problem is quite strange.
I'm looking forward to an appropriate patch from Microsoft.
The current solution is a workaround only.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now