Scheduler Service Issues

RE: Scheduler Service Issues

Sam Poe — Wed, 26 Jun 2019 14:46:01 GMT

OK there should be more logs in the event viewer than the finished one. If you look at just lines for InnovatorService there should be at least 3 lines: one that says start, one that looks like AML, and the one that says finished. There might also be some error lines that could tell us more about what's going on. I believe the finished line is just saying that the method is done running, not that it completed successfully. Unfortunately, there isn't a more detailed logging level that the level 2 you are currently using.

RE: Scheduler Service Issues

dortego — Tue, 25 Jun 2019 18:42:15 GMT

There's a 'Method Finished' event with the method name and then an event that says "mpdwsvc - Initializing authorization manager with group name "PdwDataMovementAccess" and..." every time, but the method does not seem to actually run.

RE: Scheduler Service Issues

Sam Poe — Tue, 25 Jun 2019 17:47:31 GMT

Great. Could you check the windows event logs and see if the job is firing and if so, what is the result? Is there an error in that logging that can be checked?

RE: Scheduler Service Issues

dortego — Mon, 24 Jun 2019 15:29:11 GMT

Thanks again for your response. That solved the "last run was less than an Interval ago" error that was showing up, but the changes still don't occur in the database. Not sure where the problem is.

RE: Scheduler Service Issues

Sam Poe — Fri, 21 Jun 2019 14:25:33 GMT

Dortego,

I believe the issue is with the job tags above. In the current setting (with all the *s) you are telling the service to run the method, at some point, any minute of any hour of any day of any month. As you mention this is a nightly job, I would suggest setting the hours to 23, 0, or 01 (and the minutes to something like 02 to account for any timing issues). [For testing, just choose the current hour and put the minutes in the next 5 or 10, so if it's 9:30 AM, set the test at 9 hours 35 minutes.] Also, with the current setting, this method will run every day; if you want it to run only on standard business days, you should probably set days to 1,2,3,4,5 as 0 and 6 represent Sunday and Saturday, respectively (all the time-type values can be a comma-separated list, see the blog post for more information).

Let me know if that works,
Sam

RE: Scheduler Service Issues

dortego — Fri, 21 Jun 2019 00:44:45 GMT

Thank you for your response. I kept <intervalMinutes> at 1 or 2 for all my attempts. Here's the complete InnovatorServerConfig:

<?xml version="1.0" encoding="utf-8" ?>
<innovators>
<innovator>
<server>localhost/.../server>
<database>dbName</database>
<username>admin</username>
<password>innovator</password>
<http_timeout_seconds>600</http_timeout_seconds>
<job>
<method>a_HMS_Avail A-Days Nightly Job</method>
<months>*</months>
<days>*</days>
<hours>*</hours>
<minutes>*</minutes>
</job>
</innovator>
<eventLoggingLevel>2</eventLoggingLevel>
<intervalMinutes>1</intervalMinutes>
</innovators>

RE: Scheduler Service Issues

Sam Poe — Thu, 20 Jun 2019 21:06:43 GMT

Hello dortego,
Can I ask what you have in the <intervalMinutes> tag in you InnovatorServerConfig file? (Everything from <job> to <intervalMinutes> would help me walk through this.) That seems like the most likely source of the error listed. The interval is not how often the task runs, but how often the server should check and see if the time to run it has occurred.
We also have a blog post here with an example that might help to compare your config file to.
Thanks,
Sam