Help with SM Planned Maintenance Module

[Jon23]

Trying to use the the SM Planned Maintenance application but it's not triggering a facilities request.

I've gone through the Wiki but still nothing - Anyone successfully using this module who can provide some help on where I may be going wrong?

[claytonberry]

Hey guys,

I was having the same issue.   I added some logging to find out where in the script it was getting to when I noticed this error was occurring:

org.mozilla.javascript.EvaluatorException: GlideRecord.addQuery() - invalid table name: cmdb_ci_dc_inverter (sys_script_include.14b43246eb712100eae001e64206fe14; line 760)

EvaluatorException(JavaScript evaluation error on:

new PlannedMaintenanceUtils().checkSchedules();

)

Haven't found the root cause, but it's generated when checking to see if all the records are valid on line 611 (could be off by one or two...added too many gs.log lines to be 100% sure):

this._checkM2mRecordsValid();

I commented out this line (add // to the beginning) to see what happened and then re-ran the Planned Maintenance Nightly Run job and I had Facility Requests being created.

One note of caution...this script isn't fast by any stretch.   I'm seeing things rolling in, but I had a large backlog to run through.   15 minutes later it's still creating requests (had about 1200 in my backlog).

I don't have a ticket opened myself, but if you want to validate this on your system and see if you're having the same issue, please update your tickets with this information to help our support team.

FYI, the Records Valid check is used to see if any of the scheduled tasks are against items that have been deleted out of the CI table...guessing there is a bug there; hope to dig in more when I have time.

[Dr_Bruce]

Sadly didn't kick anything off for me Tried it with SN edit, and without.

Oh well, apparently it's been escalated further up the technical support tree...

[Jon23 · Accepted solution]

ServiceNow support have come back with a solution which correlates with claytonberry findings and appears to fix the issue

The issue was a Maintenance Plan (MP0000015) which was installed when I loaded the demo data.   This maintenance plan is looking at cmdb_ci_dc_inverter table, unfortunately that table does not exist on my instance.   Due to this issue no maintenance plans ran!!

I deleted the MP000015 plan and confirmed that my test maintenance plan generated a ticket - . (Still more testing to do but looks promising)

Dr.Bruce you probably installed the demo data and its the same issue. Let me know if it works for you.

It's concerning that one incorrect MP stops all plans from processing.   I also need to confirm if the first solution supplied (change the script include) is still needed.

[munney]

Thanks jwalton, this fixed it for me as well!

[Jon23]

Just to follow up regarding the script include solution.

ServiceNow support confirmed that changing the script, 'PlannedMaintenanceUtils' is not required, and to only delete the rogue MP to fix the issue.