Cannot access VaultPro after upgrade VaultPro 6.0 to 6.1

[lharker@aocweb.org]

I am running VaultPro on a Windows Server 2008 R2 running SQL Server 2008. I just upgraded from VaultPro version 6.0 to version 6.1 and now I cannot access VaultPro. One problem I found is the IIS VaultAppPool stops running anytime I try to access VaultPro.

[lbauer]

Check the Event Viewer on the Server machine. Are there any relevant errors?

[lharker@aocweb.org]

There are a lot of errors in the event viewer. Here is a summary:

System Log
Warning - A process serving application pool 'VaultAppPool' terminated unexpectedly. The process id was '2332'. The process exit code was '0xfffffffe'.

Warning - A process serving application pool 'VaultAppPool' terminated unexpectedly. The process id was '4720'. The process exit code was '0xfffffffe'.

Warning - A process serving application pool 'VaultAppPool' terminated unexpectedly. The process id was '4596'. The process exit code was '0xfffffffe'.

Error - Application pool 'VaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

Application Log

Error - The worker process failed to pre-load .Net Runtime version v4.0.30128.

Error - The worker process failed to initialize correctly and therefore could not be started. The data is the error.

[lbauer]

Error - The worker process failed to pre-load .Net Runtime version v4.0.30128.

Looks like a .NET Framework error.

First, re-register the .NET Framework 4.x by running the aspnet_regiis.exe utility:

At a command prompt (run cmd as Admin), type the following, and then press ENTER:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

In this path, the version represents the version number of the .NET Framework that you installed on your server. You must replace the version number with the actual version number on your machine when you type the command. If your Vault Server machine is 32- bit, the command would be:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

Also, verify that the Vault App Pools are using the correct Framework:

1. In the Internet Information Services (IIS) Manager Connections pane select the Application Pools folder underneath the computer name.

2. Select the application pool that you want to configure. In the Actions pane, select Advanced Settings.

3. Under General, verify the value for .NET Framework Version. Vault app pools should use the .NET 4.x Framework. Also, all the Vault app pools should use Integrated Mode, with the exception of SGDavAppPool which uses Classic Mode.

After the Framework attribute has been changed, IIS will recycle the application pool and load the newly specified framework version for the application pool.

Let me know if this does not resolve the problem.

[lharker@aocweb.org]

Perfect!!! That fixed the problem.

Thank you for the quick response.

[lbauer]

Thanks for the update. That's good news. : ) Glad Vault is working for you now.