DBmaintenance workflow job doesnt want to run anymore - commvault 11.40.67

Iam successful in running the DBmaintenance from the command line either with the -full or -recommended options.

​@bc1410 

try updating the workflow with the latest one from https://cloud.commvault.com/commandcenter/#/softwareStore?keyword=dbmaint.

make sure you can get to port 25 on your SMTP host.

also send the log called workflowengine.log from the commserv. 

Hi ​@Gseibak 

Yes I actually just updated the DBMaintenance workflow as it was saying there was an update available. Now its states that it is “Up to DATE”.  I just tried to run it again and same thing - failed. 

I have tested sending an email that work works successfully.  (via the the email   commcell control panel | Maintenance )

send the log called workflowengine.log from the commserv.

maybe an elementary question but how to just send the workflowengine.log.   Im not seeing the option to just send the workflowengine.log   I told you Im a commvault beginner sort of speak   😀

​@Gseibak  - did you want me to just attach the workflowengine log to this topic?

yes please

​@Gseibak  - see attched

​@Gseibak   Is this correct for the workflow DBmaintenance - execute.   I actually added the startUpPath but not even sure if I needed to.  It still fails.

SNIP:

hello,

I had the same issue with a customer of mine. 

The Issue is that the part ‘-N path….’ does not belong in the Input Field command. It should looking like this.

in later Commvault Versions you have to think about the enhanced security for changes in the workflows.

Enhanced Security for Custom Workflows and Reports

Kind Regards

Florian

Thanks  ​@Florian Kaiser 

I think Im back to the way it use to be.   But still wondering where this “Script$_run_closure1...” stuff is coming from and why in the email that it auto generates.. 

This is the email results that Im getting.

SNIP:

Thanks

BC