HTTP Error 500.19 Win 10

[DTSSL]

Hi - I've read as many posts about this error as I could find, but no solution mentioned has worked for me yet. My details:

- Windows 10, freshly installed IIS with no other web apps installed
- installing: 12/01/2016 05:55 PM 40,278,528 VaultServer64_9_1_0_584.msi
- I've run installer by starting a cmd prompt with admin rights
- chose default install, IIS located at default c:\inetpub\wwwroot
- using Windows auth


URL trying to load:
http://adam/VaultService/VaultWeb/Login ... %20install.

Error information:
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \\?\C:\inetpub\wwwroot\VaultService\web.config
Physical Path C:\inetpub\wwwroot\VaultService\VaultWeb\Login.aspx

Can't think of anything else you might need. Any ideas?

[DTSSL]

I finally found the solution to my problem. Hopefully this will help someone else, as I didn't find any mention of this in the install instructions. Again, this is Win10.

i had to go into Control Panel, Turn Windows Features On or Off, .NET Framework 4.6 Advanced Services, WFC Services, and turn on all the features listed below there. I don't know which one specifically fixed it, it might be only HTTP Activation, but I just turned them all on, and then the Vault Admin Page would load correctly.

[jclausius]

Good find! Do you think it might have been related to this KB article - http://support.sourcegear.com/viewtopic ... 740#p73740 ?

( Looks like it has not yet been updated for Windows 10. )

[Balvert]

It seems HTTP Activation fixed the issue.

Rene

[Wiffle]

I finally found the solution to my problem. Hopefully this will help someone else, as I didn't find any mention of this in the install instructions. Again, this is Win10.

i had to go into Control Panel, Turn Windows Features On or Off, .NET Framework 4.6 Advanced Services, WFC Services, and turn on all the features listed below there. I don't know which one specifically fixed it, it might be only HTTP Activation, but I just turned them all on, and then the Vault Admin Page would load correctly.

Thanks DTSSL that fixed it for me too but I don't know if this is a permanent solution.

[jclausius]

Vault does not have any direct code which uses WCF, but there could be something in the .NET Frameworks that require activation. Glad everyone has it sorted out.