HTTP Error 500.19

kmxsoft · Post by **kmxsoft** » Wed Sep 18, 2019 11:06 pm

I have Vault installed and working well on a Windows Server 2016 system. I am currently trying to port this to a new Windows Server 2019 system. Whilst the installation goes well, when I attempt to access the Vault control panel I am met with HTTP Error 500.19 - Internal server error. The SQL Server database has been created without a problem.

The resulting web page gives various detail which I have attached in a zip file. Unfortunately I'm a bit confused with the detail so would appreciate any assistance to figure out what has gone wrong.

Thanks in anticipation.

----
[From the SourceGear Moderator]

Note, the attached HTML page included some banners and other information that was irrelevant to the issue, and was removed. The HTML error message is seen below.

Code: Select all

<body> 
<div id="content"> 
<div class="content-container"> 
  <h3>HTTP Error 500.19 - Internal Server Error</h3> 
  <h4>The requested page cannot be accessed because the related configuration data for the page is invalid.</h4> 
</div> 
 
<div class="content-container"> 
 <fieldset><h4>Detailed Error Information:</h4> 
  <div id="details-left"> 
   <table cellspacing="0" cellpadding="0" border="0"> 
    <tbody><tr class="alt"><th>Module</th><td>IIS Web Core</td></tr> 
    <tr><th>Notification</th><td>BeginRequest</td></tr> 
    <tr class="alt"><th>Handler</th><td>Not yet determined</td></tr> 
    <tr><th>Error Code</th><td>0x80070021</td></tr> 
    <tr class="alt"><th>Config Error</th><td>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".
</td></tr> 
<tr><th>Config File</th><td>\\?\C:\inetpub\wwwroot\VaultService\web.config</td></tr> 
   </tbody></table> 
  </div> 
  <div id="details-right"> 
   <table cellspacing="0" cellpadding="0" border="0"> 
    <tbody><tr class="alt"><th>Requested URL</th><td>http://192.168.0.7:80/VaultService/VaultWeb/Login.aspx?ReturnUrl=%2fVaultService%2fVaultWeb%2fDefault.aspx</td></tr> 
    <tr><th>Physical Path</th><td>C:\inetpub\wwwroot\VaultService\VaultWeb\Login.aspx</td></tr> 
    <tr class="alt"><th>Logon Method</th><td>Not yet determined</td></tr> 
    <tr><th>Logon User</th><td>Not yet determined</td></tr> 
     
   </tbody></table> 
   <div class="clear"></div> 
  </div> 
 </fieldset> 
</div> 
  <div class="config_source content-container"> 
    <fieldset> 
    <h4>Config Source:</h4> 
    <pre><code>  220:     &lt;/security&gt;
<span class="highlight-code">  221:     &lt;handlers&gt;</span>
  222:       &lt;remove name="ReportViewerWebControlHandler" /&gt;
</code></pre> 
    </fieldset> 
  </div> 
 
<div class="content-container"> 
 <fieldset><h4>More Information:</h4> 
  This error occurs when there is a problem reading the configuration 
file for the Web server or Web application. In some cases, the event 
logs may contain more information about what caused this error. 
  <p><a href="https://go.microsoft.com/fwlink/?LinkID=62293&amp;IIS70Error=500,19,0x80070021,17763">View more information »</a></p> 
   
 </fieldset> 
</div> 
</div> 
 
 
</body>

Post by **Tonya** » Thu Sep 19, 2019 8:33 am

Hello,

This is likely an IIS related issue. When you setup / configured the IIS server for the Vault Server, did you add the "Application Server" feature as well as the HTTP static content to the role?

Below are the roles that need to be checked:

Web Server (IIS) \ Web Server \ Common HTTP Features \ Static Content ( checked) Web Server (IIS) \ Web Server \ Application Development \ ASP.NET 4.6 (checked )

Please let me know if this doesn't resolve the problem.

Thanks,

Tonya

kmxsoft · Post by **kmxsoft** » Thu Sep 19, 2019 1:23 pm

Hi Tonya,
Thanks for your reply. Problem is now resolved.

One minor difference to your instructions - ASP.NET 4.6 not listed, so I used ASP.NET 4.7 and that worked fine.

Also, my apologies for inclusion of materials not related to this issue - I simply did a web page save and obviously that brought details which weren't required.

Thanks again, I now have a working Vault access panel.

Andrew

Post by **Tonya** » Fri Sep 20, 2019 8:55 am

Hi Andrew,

Glad to hear the problem is now resolved. Thank you for the update.

Tonya

SourceGear Support

HTTP Error 500.19

HTTP Error 500.19

Re: HTTP Error 500.19

Re: HTTP Error 500.19

Re: HTTP Error 500.19