nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Actuate_BIRT_Mailer_Report failing

CodeRookie

<p>Good morning, all! For the past two days, I've had a scheduled job run, only to have the mailer fail for each instance. The detail message I'm getting is:</p>
<p> </p>
<div>There is non-fatal error. Cause : There are errors evaluating script "importPackage(Packages.com.acbirt.report.mailer);</div>
<div>acbirtconverter = new AcBIRTFileConverter();</div>
<div>acbirtconverter.convertReport(params["iServerURL"].value, </div>
<div>params["Email_Choice"].value,</div>
<div>params["acParamUserId"].value,</div>
<div>params["acParamUserPwd"].value, </div>
<div>params["docOutputName"].value, </div>
<div>1, "", "",</div>
<div>params["Emails"].value, </div>
<div>params["fromEmail"].value, </div>
<div>params["Comments"].value, </div>
<div>params["Comments"].value, </div>
<div>params["smtpHost"].value, </div>
<div>params["acLocale"].value);</div>
<div>":</div>
<div>Wrapped Soap Server error. (/report/method[@name="afterFactory"]#4) (Element ID:1)com.actuate.reportapi.enginemanager.JREMException: There is non-fatal error. Cause : There are errors evaluating script "importPackage(Packages.com.acbirt.report.mailer);</div>
<div>acbirtconverter = new AcBIRTFileConverter();</div>
<div>acbirtconverter.convertReport(params["iServerURL"].value, </div>
<div> </div>
<div>There is more details that follow this, but I didn't see the need to have a post that rambles on forever. If anyone can shed some light on the subject, I would be greatly appreciative. Have a great day!</div>
<div> </div>
<div>Thanks,</div>
<div>Scott</div>

Find more posts tagged with

Comments

JFreeman

<p>The first part of the stack trace indicates the error is happening on line 4 of the script in afterFactory. I would start there for investigating why the script is failing.</p>
<p> </p>
<p>Is it possible for you to attach the log file with the full stack trace(s) that are occurring and the corresponding report?</p>

CodeRookie

<p>It appears that the problem may have resolved itself (somewhat). I noticed this morning that the mailer did not fail as compared to the previous two days. I saw that the report that was being mailed actually had content to it as opposed to the previous days' reports. I'm going to watch for tomorrow's results and see what happens. Probably not the best method to use for troubleshooting, but it's not a critical report. Thanks for your help! Have a great day!</p>
<p> </p>
<p>Scott</p>

JFreeman

<p>I'm glad to hear it sounds like it is resolved.</p>
<p>Let us know if you have additional questions.</p>

CodeRookie

<p>Good morning, all! Unfortunately, my problem has reared its ugly head again. The report itself runs fine, but the BIRT mailer is failing. I am attaching a copy of the full stack trace (Word doc) plus a copy of the actual report design. Any pointers would be appreciated.</p>
<p> </p>
<p>Thanks!</p>
<p>Scott</p>

JFreeman

<p>The stack trace indicates the error is happening at line 4 in the afterFactory method of the report. Looking at the report, this line appears to be the first instance of writing a debug output using the Script Logger:</p>
<pre class="_prettyXprint _lang-js">
scriptLogger.debug("Start After Factory...");
</pre>
<p>However, the script listed in the stack trace output appears to have some differences compared with the version of the report that is attached. Is the report attached the exact version of the report that was running when the errors occurred?</p>
<p> </p>
<p>In order to pursue this issue, I would start by focusing in on the code that is on line #4 of the afterFactory method of the report. If it is indeed the the logging statement, I would start by commenting out the logging and see if the report completes successfully. </p>

CodeRookie

<p>Sorry about that, Jesse. I forgot I had changed some stuff in that version. I'm attaching the original version of the report. I'll look at the area you had pointed out. Thanks for your help!</p>
<p> </p>
<p>Scott</p>

JFreeman

<p>The only difference I see with this version of the report is that the log level is set to Info instead of Debug but line 4 of the afterFactory is still the logging statement I pointed out previously.</p>
<p> </p>
<p>I would start by commenting out the logging statements and see if that resolves the issue. If so, then begin investigating the logging for why it is having issues.</p>

CodeRookie

<p>Thanks, Jesse! I'll follow those recommendations as soon as I get a chance. Was called upon to develop a new report today. So, that has precedence at the moment. Have a great afternoon!</p>
<p> </p>
<p>Scott</p>

JFreeman

<p>You're welcome.</p>
<p>Let us know if you have additional questions.</p>