Upgrade Issue - Could not load file or assembly 'DragnetCont

[yogimeister]

Upgrading from vault std 5.1.2 to 6.1 then to 7.2

After the first step to upgrade to 6.1, which did not have any errors, the web console page now presents the following error - Could not load file or assembly 'DragnetControlsLib' or one of its dependencies

Server is 2012R2 with SQL 2008R2

[Beth]

Did you by any chance install the 32-bit version of Vault on a 64-bit machine or vice versa?

Are any of the application pools that relate to to the Vault website running in 32-bit mode? To find that setting, go to the application pools in your IIS Manager. Click on one related to Vault such as the vaultapppool and then click advanced settings. The setting you are looking for is Enable 32-bit Applications.

[yogimeister]

This first appeared after I ran the install for 6.1.0 - file name was VaultServer64_6_1_0_531 so I think we had the right 64bit version

As for the VaultAppPool the Enable 32 bit applications is set to True

[Beth]

If you wish to use the 64-bit version of Vault, then the Enable 32-bit Applications needs to be set to False.

If you want to keep the Enable 32-bit Applications set to True, then you need to install the 32-bit version of Vault.

[yogimeister]

Ok, now I am getting this

Could not find file 'c:\windows\system32\inetsrv\XXXXXXXXVault.Config'

[Beth]

In your IIS Manager, what .NET framework are the application pools set to use?

What are the Managed Pipelines set to?

[yogimeister]

>NET CLR Version v4.0.30319

Pipeline mode = Integrated

[Beth]

What identity is the Vaultapppool running under?

Does that same identity have read/write/modify permissions to the location c:\windows\system32\inetsrv?

[yogimeister]

Identity = ApplicationPoolIdentity

I don't know how to check permissions for this identity/user on the folder in question

[Beth]

Right-click the folder and select Properties. There should be a Security tab. What do you have listed in the security tab?

[yogimeister]

All application packaged = Read & Execute
Creator Owner = Special
System = Special
Administrators = Special
Users = Read &Execute
Trusted Installer = List

[Beth]

I think it would be best if an uninstall/reinstall was performed and allow Vault to set the permissions again.

When you uninstall, choose the option to keep the database.

Instead of double-clicking the .msi to run the installer, run a command prompt as administrator and then launch the .msi from the command line.