Fix Readme
Abstract
The article describes how to fix the issue of Web Page no longer loading after upgrading to Verify Privilege Vault 11.8.
Content
Product: Verify Privilege Vault; Verify Privilege Vault On-Prem
Known Environments: Verify Privilege Vault on-prem environments upgrading to Privilege Vault version 11.8
Issue: After upgrading to the latest version of Privilege Vault, version 11.8+, the website is expected to load successfully, however, it's still trying to load the elements on the page.
The most likely cause of this is that the application pool does not have the correct permissions to rename the "App_Code" in the Privilege Vault application files.
Resolution
There are two potential fixes for this issue:
Rename the folder manually:
- Remote into the upgraded web nodes.
- Open File Explorer.
- Navigate to Privilege Vault's folder, usually "C:\inetpub\wwwroot\PrivilegeVault".
- Find the "App_Code" folder and rename it to something like "App_Code_Bak".
Provide the account running the application pool with permissions on the folder. "Modify" permissions are required.
- Remote into the upgraded web nodes.
- Open File Explorer.
- Navigate to the IIS top-level folder where the Privilege Vault folder is located, usually "C:\inetpub\wwwroot".
- Right-click on the Privilege Vault folder and click "Properties".
- Go to "Security" tab and then click "Edit".
- Click on the account that is running the Privilege Vault application pool.
- Check the "Modify" box in the Allow column and click "OK".
- Click "OK" again.
- Perform an iisreset. See the article for more information.
- After performing the iisreset, you should see that the folder has been renamed.
Cause
Prior to Privilege Vault 11.8.x, the application shipped in a "dynamically compiled" state, which means that aspects of the website (primarily .aspx files) were compiled by IIS when the application received the first request:
This upgrade and future on-prem upgrades or fresh installs are pre-compiled. This means that application startup should be faster, as dynamic compilation is not required.
Pre-compiled applications cannot run in IIS if there is an "App_Code" folder. 11.8 automatically renames this folder on start-up to avoid issues, as long as the account running the application pool has the proper permissions.
Additional information
See the document for more information about running the application pool as a service account and the permissions required.
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS2N2U","label":"IBM Security Verify Privilege"},"ARM Category":[{"code":"a8m3p000000UoHvAAK","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
01 July 2025
UID
ibm17237717