PRB: Server Application Unavailable error when Web client is installed on a Domain Controller
This Zetafax technical note applies to:
If you install the Zetafax web client on a system which is also a domain controller your browser displays the following message when you try and visit its web site:
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable.
Please hit the " Refresh" button in your web browser to retry your request.
Also if you check the event viewer the following event is logged in the system application event log:
aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.
aspnet_wp.exe could not be started.
HRESULT for the failure: 80004005
By default, ASP.NET runs its worker process (Aspnet_wp.exe) with a weak account (the local machine account, which is named ASPNET) to provide a more secure environment. On a domain controller or on a backup domain controller, all user accounts are domain accounts and are not local machine accounts. Therefore, Aspnet_wp.exe fails to start because it cannot find a local account named " localmachinename\ASPNET" . To provide a valid user account on the domain controller, you must specify an explicit account in the < processModel> section of the Machine.config file, or you must use the SYSTEM account.
Administrators may want to install the Zetafax Web client on a system which is not a domain controller, to work around this issue with ASP.NET.
Alternatively you can work through Microsoft Knowledge Base Article Q315158 "BUG: ASP.NET Does Not Work with the Default ASPNET Account on a Domain Controller" which can be found on http://support.microsoft.com/.
This has been identified by Equisys as a problem with the software versions given above.
Last updated: 14 March 2003 (AG/SV)