Error Message

HTTP Error 500.19 Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

Config Error:  Cannot read configuration file due to insufficient permissions.

When the Accelerator is not installed in the default location, the EVAcceleratorAppPool Application Pool Identity may not automatically have rights to the AcceleratorAdminWeb physical directory (InstallPath\AcceleratorAdminWeb).

1. Navigate to the installation location of the Accelerator product.
2. Open the Properties of the AcceleratorAdminWeb subfolder.
3. On the Security tab, click Edit.
4. The EVAcceleratorAppPool account should have the following access to the folder: Read & execute, List folder contents, Read. Ordinarily this access is achieved via inheritance of the entry for the local Users group (of which the EVAcceleratorAppPool account is a member) on the Program Files (x86) directory.
5. If the above inheritance is not in place, the account can be added directly by clicking Add and entering the object name computername\IIS_IUSRS. Since this is a local account, make sure that the local machine, rather than the domain, is selected in the "From this location:" field. Grant it the Read & execute, List folder contents, and Read permissions.
6. Reload the EVBAAdmin page and it should now load properly.

1. Open IIS Manager and left-click on the Application Pools node in the left pane.
2. Right-click on the EVAcceleratorAppPool object in the right pane and select Advanced Settings (see figure 1 below).
3. Under the Process Model section, left-click the field containing ApplicationPoolIdentity and click the ellipsis (...) button to bring up the Application Pool Identity dialog.
4. In the drop-down box select NetworkService and click OK twice (see figure 2 below).
5. Restart the EVAcceleratorAppPool by highlighting EVAcceleratorAppPool and then clicking Stop and then Start in the Actions pane to the right.
6. Restart the Enterprise Vault Accelerator Manager Services from the Services console.
7. Reload the EVBAAdmin page and it hsould now load properly.

Figure 1:

Figure 2:

Applies To

This can be seen when the EV Accelerator product is not installed in the default location on the C: drive but on another logical drive on the server such as D: or E:.