IIS Application pools can stop after one request to the server. This article details these cases, and provides resolutions to each case.
Note: This article applies to operating systems with IIS 6.0 and above.
Incorrect login information
The identity under which the application pool user is running, contains incorrect login information. This issue is more common to those people who run Dundas Dashboard under specific user credentials.Resolution
: Verify the credentials are correct by doing the following:
- Go to Notepad and right click, then select Run as. (On Windows 7, press the CTRL key, do a right-click, then select Run as a different user.)
- Select The following user option, and enter your credentials.
- Then click the OK Button.
If you see Notepad, the credentials are correct. If you received the following dialog, your credentials are not correct, and you should contact your system administrator:
The dialog that appears when your credentials are not valid.
The identity under which the app pool user is running does not have enough privileges
The identity under which the application pool user is running does not have enough privileges to run the web application. This issue is more common to those people who run Dundas Dashboard under specific user credentials.
: Verify the application pool user is part of the IIS_WPG (IIS Worker Process Group):
- Right Click on My Computer and click the Manage item.
- Expand the Local Users and Groups.
- Select Groups.
- Right click the IIS_WPG group.
- Click Properties.
- Verify that your application pool user is a member of this group. If the user is not a member click the add button and enter the users name.
The IIS_WPG Properties Dialog.
The resolution is similar to IIS 6, except the user group is named IIS_IUSRS
instead of IIS_WPG.
On Windows 2008, you can follow these steps
to add an account to the IIS_IUSRS group.