Adam,
I have tried your suggestion by changing the following path in web.config to force dashboard to run in powershell core and it didnt work
“aspNetCore processPath=”.\netstandard2.0\universaldashboard.server.dll" arguments="" stdoutLogEnabled=“true” stdoutLogFile="\?%home%\LogFiles\stdout" forwardWindowsAuthToken=“false” /"
adam
April 18, 2019, 2:34am
2
Hmmm ok. I will have to look into that. I’ve seen that error a couple times when messing with custom components but usually restarting the dashboard fixes it. I’ll try and narrow it down.
any fix to this?
I get the same error
Conversation is ongoing here:
I don’t know why you would be getting multiple processes with IIS. That’s strange and wasn’t aware that’s how IIS was working. As far as the -Wait parameter, yep, it’s just more a less a keep alive and calls a different method within ASP.NET Core that holds the process open and waits for the IIS proxy connection.