#1 2018-01-04 13:18:35

jeffrozica
Member
Registered: 2017-08-17
Posts: 21

Getting an email error after scheduled job runs after v3.0.3.6002 upg

I upgraded our QA environment to latest v3.0.3.6002 release last night and now after our scheduled jobs ran, each one got this error when trying to send an email, but the report ran and placed the output in the correct folder.   My email settings did not change and this was working before….   Before I was on the latest v3.0.3 beta version as of 2017-08-31.

I was able to send an email via reportserver by creating a test user and clicking on the ACTIVATE button and that works, its just trying to send emails after a scheduled job runs, I get this error.

Since these scheduled jobs existed before the upgrade, I recreated a new scheduled job for one of the same reports and it ran successfully and the email was sent for scheduling a new job, but when the scheduled job ran at its scheduled time, it failed to send the email and got the same error so I think there is an issue with this release regarding this.

This error only happens when you try to have the scheduled output go to a teamspace and folder and it tries to send you a notification that the report ran.  If you have it send the report via an email attachment, it works, but if you have it go to a teamspace and folder and it normally would send an email to notify you the report ran, that’s when you get this email error.

Can you please look into this issue?  We need this functionality to work as it did before.

ERROR

extension net.datenwerke.rs.scheduleasfile.service.scheduleasfile.hooker.ScheduleAsFileEmailNotificationHooker failed to executed actionExecutionEndedSuccessfully
javax.el.PropertyNotFoundException: Cannot find property filename
                at de.odysseus.el.util.RootPropertyResolver.getValue(RootPropertyResolver.java:86)
                at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:63)
                at de.odysseus.el.util.SimpleResolver.getValue(SimpleResolver.java:120)
                at de.odysseus.el.tree.impl.ast.AstIdentifier.eval(AstIdentifier.java:91)
                at de.odysseus.el.tree.impl.ast.AstEval.eval(AstEval.java:51)
                at de.odysseus.el.tree.impl.ast.AstComposite.eval(AstComposite.java:35)
                at de.odysseus.el.tree.impl.ast.AstNode.getValue(AstNode.java:31)
                at de.odysseus.el.TreeValueExpression.getValue(TreeValueExpression.java:122)
                at net.datenwerke.rs.utils.juel.JuelServiceImpl.evaluate(JuelServiceImpl.java:181)
                at net.datenwerke.rs.utils.juel.JuelServiceImpl.evaluate(JuelServiceImpl.java:167)
                at net.datenwerke.rs.utils.juel.SimpleJuel.parseAsObject(SimpleJuel.java:36)
                at net.datenwerke.rs.utils.juel.SimpleJuel.parse(SimpleJuel.java:28)
                at net.datenwerke.rs.core.service.mail.MailTemplate.configureMail(MailTemplate.java:73)
                at net.datenwerke.rs.core.service.mail.MailServiceImpl.newTemplateMail(MailServiceImpl.java:101)
                at net.datenwerke.rs.scheduleasfile.service.scheduleasfile.hooker.ScheduleAsFileEmailNotificationHooker.sendmail(ScheduleAsFileEmailNotificationHooker.java:145)
                at net.datenwerke.rs.scheduleasfile.service.scheduleasfile.hooker.ScheduleAsFileEmailNotificationHooker.actionExecutionEndedSuccessfully(ScheduleAsFileEmailNotificationHooker.java:101)
                at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeActions(SchedulerTask.java:461)
                at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:209)
                at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:101)
                at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
                at java.util.concurrent.FutureTask.run(Unknown Source)
                at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                at java.lang.Thread.run(Unknown Source)

Offline

#2 2018-01-04 14:15:31

eduardo
Administrator
Registered: 2016-11-01
Posts: 719

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Hi jeffrozica,

we are able to reproduce this and are looking what happens here. We will update this forum when we have more information.

Regards,
Eduardo

Offline

#3 2018-01-04 15:49:07

jalbrecht
Administrator
Registered: 2016-10-21
Posts: 123

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Hi jeffrozica,

we are still in the process of analyzing the reasons of this unexpected behaviour. But we found a not yet fully tested workaround:
In reportserver go to FileServer Root/etc/scheduler/ and open file scheduler.cf. These is a sinlgle occurance of the string ${filename} in line 20:

  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}

Change ${filename} to ${name} and check if this works. The line should read:

  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${name}

after the change. Do a config reload in the terminal to activate the change or restart the ReportServer.

This change seems to fix the problem in our test environment (without having performed a complete test yet). Pls. test this workaround and let us know the result.
We will correct this with the next patch release.

wbr jan

Offline

#4 2018-01-04 16:58:55

jalbrecht
Administrator
Registered: 2016-10-21
Posts: 123

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Hi jeffrozica,

we can confirm that the change described above is correcting the problem. The Problem itself is caused by our tightening of juel execution: before (until RS 3.0.3 6000) it was more lazy and we changed this behaviour to forcing correct variable evaluation. This caused the error since the variable filename never existed ... . The next patch will correct the scheduler.cf as described above, hence fresh installations will have no issue and existing ones must be corrected manually.

wbr jan

Offline

#5 2018-01-05 08:35:08

eduardo
Administrator
Registered: 2016-11-01
Posts: 719

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Hi jeffrozia,

we will support both in the next reportserver patch:
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
and
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${name}
They will both reference the field name in the configuration window. Thus, existing installations will *not* have to be corrected manually, they will work out-of-the-box.

For your reference: this will be addressed in ticket RS-2853.

Regards,
Eduardo

Offline

#6 2018-04-18 12:12:46

hMobile
Member
Registered: 2018-03-27
Posts: 26

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Hi,

The workaround works for me and now I'm receiving the information mails...

But I have a no resolved label in the body of the mail:

A scheduled report was executed and stored in your TeamSpace 

  Report: Report in Excel
  Filename: ${now} - Report in Excel
  Description: na
  TeamSpace: Sales
  Folder: Test1

Is there any other line to correct?

Thanks,

Rom

Offline

#7 2018-04-18 12:14:05

hMobile
Member
Registered: 2018-03-27
Posts: 26

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Update: the report comes with the correct date-name into the email.

Rom

Offline

#8 2018-07-27 11:19:21

eduardo
Administrator
Registered: 2016-11-01
Posts: 719

Re: Getting an email error after scheduled job runs after v3.0.3.6002 upg

Hi,

these two bugs are corrected (RS-2986 and RS-2988). Both {filename} and {name} will work, the {name} will show the filename without the extension, while the {filename} will show the complete filename. This will work for scheduling to email and to teamspaces. Both bugs will be fixed in the next reportserver version and will work for both new installations and upgrades.

Regards,
Eduardo

Offline

Board footer

Powered by FluxBB