After the latest release of UD (2.9.0), we seem to be unable to run even the most simple dashboard in Azure Web Apps. Regardless of what we deploy, we seem to always get an IIS error stating: " HTTP Error 502.5 - Process Failure". In the event log, I’m able to see that the server was unable to start a Powershell.exe process, but I get no useful data besides that. The event log error can be seen below:
<Event>
<System>
<Provider Name="IIS AspNetCore Module"/>
<EventID>1000</EventID>
<Level>1</Level>
<Task>0</Task>
<Keywords>Keywords</Keywords>
<TimeCreated SystemTime="2020-02-26T21:41:45Z"/>
<EventRecordID>909532515</EventRecordID>
<Channel>Application</Channel>
<Computer>RD281878B9A69D</Computer>
<Security/>
</System>
<EventData>
<Data>Application 'MACHINE/WEBROOT/APPHOST/MBIT-PRD-DESKTOPDASHBOARD-WEBAPP__0C7C' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'PowerShell.exe ', ErrorCode = '0x80004005' : 5.</Data>
</EventData>
</Event>
I am aware that in the most recent release the web.config file was changed to now reference Powershell.exe directly, vs the Universal Dashboard server file, and I’m curious if that is part of the issue. Has anyone else experienced this problem?
At the beginning of the script I started the logging. Below that, I was doing the UD module import. So it never looked at the config in the directory, instead pulling the defaults from where the module was installed from PSGallery.
And the first 2 lines of code in my dashboard.ps1 are as below: $WarningPreference = "SilentlyContinue" Import-Module .\UniversalDashboard.psm1
My dashboard does load, and I’m able to get to the login page and complete AzureAD authentication, but afterwards I’m left with a blank page. The only thing that appears in Chrome’s DevTools is the below warning, which I don’t believe has any bearing on this.
Given the security concerns with earlier versions of UD, we obviously don’t want to downgrade our dashboard at this point. @adam I’m hoping you can shed some light here.
UPDATE:
Literally moments after posting this, the below error appeared in devtools after several minutes sitting on a blank page. Nothing changed on the page itself.
Following up on this as well as @jmknight2 coworker.
@adam Was a guide developed on any changes needed to migrate to 2.8.x to 2.9.x on an Azure App Service? We’ve deployed 3 different dashboards and all of them error out on 2.9.x on a Azure App Service.