Closed dengyakui closed 2 years ago
I solved the problem~. By check the logs, it was the daprd.exe path problem, the website app pool 's identity default to Network Service, so the problem is the user home dirs not exist daprd.exe
by change the iis application pool's identity to current user, Dapr start succeefully.
Glad you were able to work it out! If you would prefer to run the AppPool under the regular identity then you can explicitly tell Sidekick where to find daprd
. We do this ourselves as we push the dapr binaries to a non-user local directory such as C:\dapr\latest
and use the following entry in appsettings.json
to ensure they are picked up by Sidekick:
{
"DaprSidekick": {
"InitialDirectory": "C:\\dapr\\latest"
}
}
Thanks
@dengyakui i have a aspnet core 6 web apps deployed in windows server IIS ,i need help,can you wirte a step by step ?
Ask your question here
We have several aspnet core 6 web apps deployed in windows server 2016 IIS, and the network is on-promised. can not use Docker. We always want to use Dapr to make some microservice, The biggest problem is the process daemon . If the server shutdown or restart, out app should be auto restarted, so we choose IIS In Process Mode to publish our sites, because there are a bunches of toolchains like MSDeloy, VisualStudio, Rider, AzureDevops to support. But IIS can not start daprd process for app side car, if we use the default self-hosted mode, can not auto restart app or dapr side car , or directed start app as backgroud service, not to stuck with the console.
This project seems to solve out problem, but I found it can not properly start daprd when I pub the website to iis.