When you try to view a page in a Web Interface logon page, you receive the following error message:
"Server Unavailable: Server Application Unavailable: The web application you are attempting to access to this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what casued this error to occur."
You may also see the corresponding error on the Application event log on the Web Interface server:
“aspnet_wp.exe could not be started. HRESULT for the failure: 80070005”
This problem occurs because the process model user account (by default, ASPNET) does not have the correct user rights for the required system files and folders to run the ASP.NET worker process.
You can restart IIS on the Web Interface server, but this might be a temporary fix. Otherwise, perform the following steps:
To work around this problem,
1. Verify that the ASPNET account has the correct user rights as follows:
%windir%\Microsoft.NET\Framework\Version\Temporary ASP.NET Files: Full Control
%windir%\Temp: Full Control
Application folder: Read
%installroot% hierarchy (for example, %windir%\Microsoft.Net\Framework\Version): Read
Note This is the global assembly cache. You cannot directly use Windows Explorer to edit ACLs for this folder. Instead, open a command window, and then run the following command:
cacls %windir%\assembly /e /t /p domain\useraccount:R
Alternatively, before you use Windows Explorer, run the following command to unregister Shfusion.dll:
After you set user rights in Windows Explorer, run the following command to re-register Shfusion.dll:
2. Set the Web site root (for example, %root%\Inetpub\Wwwroot) or the path that the default Web site points to: Read
3. Set %windir%\System32: Read
(Typically, the ASPNET account has already been granted user rights as a member of the Users group.)
4. If the issue still persists, engage Microsoft for a solution.