-
-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scheduler is not working #27
Comments
I believe in IIS (using the reverse kestrel proxy module) the .Net core application doesn't actually "start" until the first http request comes in. So if you have no http requests that are hit (i.e. you are just trying to use the scheduler), it might be why your asp .net core app hasn't started yet. Sounds like maybe you want to do this by building a console app or windows service? I'm planning on adding some docs for these scenarios in the future. Let me know if this helps! |
Here's the link describing what I had just said.
|
Closing - let me know if you need further aid. |
This was helpful, thanks |
@jamesmh I have tried some different cases with this such as https://www.taithienbo.com/how-to-auto-start-and-keep-an-asp-net-core-web-application-and-keep-it-running-on-iis/ but I am still getting issues. The scheduler doesn't seem to run even though the IIS site should be running and not time out to always be open and running. |
No idea. What version of .NET Core, Coravel and IIS are you running? Is this inproc or outofprocess hosting method? |
Sounds like IIS isn't using the "always running" option? Try out this -> https://www.nickedeye.com/iis-keep-website-alive-always-running/ Let me know 👍 |
Hii, I just got this error. Now, add that |
I tried making a scheduler in .NET Core 2.1 running on Windows Server 2016 with IIS, but unfortunately doesn't work. Here is the code:
Expected: Works and calls API
Actual: Doesn't do anything
The text was updated successfully, but these errors were encountered: