KB0042 - HTTP Error 500.19 - internal server error 0x8007000d
Problem
When trying to browse your instance of PowerShell Universal (running on IIS under Windows Server via the ZIP install of PowerShell Universal [1] ) you receive HTTP Error 500.19 - Internal Server Error with error code 0x8007000d
Cause
You may have installed the wrong .NET setup file or overlooked installing it[2]
Solution
Be sure that you installed the current version of the recommended "Hosting Bundle" from the ASP .NET Core Hosting Bundle (currently 7.x) per the documentation[3]
(figure shows the setup screen of the correct installer)
(figure shows how the ASP .NET Core Hosting Bundle should appear in the Server's Control Panel)
Always be sure to reboot the server after installing the hosting bundle
Reference
Related Articles
PowerShell Universal server crashes with error "Unable to cast object of type 'LiteDB.EmptyPage' to type 'LiteDB.DataPage'. "
Version: 1.4.x Issue: An error is thrown when running jobs that states: Error executing job 31: Unable to cast object of type 'LiteDB.EmptyPage' to type 'LiteDB.DataPage'. at LiteDB.PageService.GetPage[T](UInt32 pageID) This only happens ...IIS: HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure
Applies to: PowerShell Universal 1.4 or later When configuring PowerShell Universal to run under IIS, you may be presented with an error that states ANCM Out-Of-Process Startup Failure. This error can be presented for a variety of reasons but the ...OpenID Connect does not work with HTTP
Version: Any Problem: When configuring PowerShell Universal OpenID Connect authentication, the server will return a 500 error when attempting to authenticate. Root Cause Chrome 80 introduced new settings that require cross-site cookies to be secure. ...KB0015 - Offline PSU server has slow dashboards
Disclaimer Please be careful with changing any settings on your server around the Certificate Revocation List. You should only do this if you know what you are doing. Read the related Github articles (linked below) in their entirety. Symptom PSU ..."[WARN] Call failed. An error occurred while sending the request." message in all jobs
Version: Any Root Cause When PowerShell Universal starts a new job, it uses the Management API to retrieve job information from the server. It does this over HTTP and will generate a Read-Only app token for the identity of the user that started or ...