| Comments |
| 9/2/2021 11:56:44 AM |
Bob Denny |
|
| 9/2/2021 10:30:04 AM |
Bob Denny |
REOPENED
The logged message
2021-09-01 21:52:43.8: HTTP command listener failed to start: Access is denied
2021-09-01 21:52:43.8: If this is Windows 8-10, you will need to add permission (ACL) to listen on port 9123.
2021-09-01 21:52:43.8: See Scheduler Help > Configuring the Program > Noteworthy Configuration Options, at the bottom.
is scaring people. Change the log level to Debug and add a note that this an optional feature. Not worth making this a config option and surprising people with it defaulted OFF. |
| 9/11/2018 12:22:47 PM |
Bob Denny |
|
| 9/11/2018 12:10:39 PM |
Bob Denny |
|
| 9/11/2018 12:08:15 PM |
Bob Denny |
REOPENED
Add friendly error message for case where Windows 10 security prevents starting the listener. Point to the docs where this is covered. |
| 6/27/2018 9:04:46 AM |
Bob Denny |
With the ACL added, it's working for him. Close it. |
| 6/26/2018 6:07:47 PM |
Bob Denny |
|
| 6/26/2018 5:14:25 PM |
Bob Denny |
Stephane can't get it to run on Windows 10. I did some research and found this MSDN article. Apparently you need to add an ACL with netsh??? I'm OK because it's for localhost or the local IP. Just need to determine these addresses, then add as ACLs. Can this be done internal to the program? Also I found this StackOverflow post that says you can get away without adding ACLs if you use exactly 'localhost' as the host, not even 127.0.0.1. However it may require .NET 4.5 and I am not ready to move to that.
netsh http add urlacl url=http://+:9876/MyUri user=DOMAIN\user
|
| 5/7/2018 6:52:55 PM |
Bob Denny |
|
| 5/7/2018 6:38:34 PM |
Bob Denny |
|
| 5/7/2018 2:22:43 PM |
Bob Denny |
OH! I never told those guys I had done this! OK, complete the docs and get a copy of the Scheduler.EXE out to them. |
| 2/19/2018 12:27:04 PM |
Bob Denny |
|
| 2/3/2018 7:12:56 PM |
Bob Denny |
|
| 2/3/2018 5:49:51 PM |
Bob Denny |
Using a tiny local-only web server to receive the command. May use for start/stop of dispatcher as well, eh? Simply call Engine.InterruptDispatcher(bool StopRunningPlans). |