Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Scheduled report is not run and not emailed

SA-4987

Summary



Administrators received reports from their system managed that they were not receiving scheduled reports if they attempted to reschedule them.


Root Cause



The original problem was when the report scheduled was saved a second time, this was not populating some key fields.



Steps to Reproduce



1. (Optional) stop all agents 
2. Ensure the ScheduleTaskProcess agent is stopped.
3. Log in to the Case Manager portal 
4. Navigate to the Reports tab 
5. Right click on a report (that does not have a schedule) and click the "Schedule" button 
6. Create a Daily Scheduled report, choosing today's date as the starting date. 
7. (Optional through to and including step 11) By default you will need to set the first run at some full hour in the future. 
In SQL (Oracle in this instance) update the pr_sys_queues so that the report will be run immediately 

update pr_sys_queues set pxMinimumDatetimeForProcessing = sysdate where pxinsname like 'SYSTEM-QUEUE-SCHEDULEDTASK 14102%' 
commit 

You may need to examine your instance data to know which row to run 
HINT: By default Oracle does not display the time portion of a date time. But the query below will show this:- 

select to_char(pxcreatedatetime,'DD/MM/YYYY HH24:MI:SS') createdate, pxinsname, 
to_char(pyminimumdatetimeforprocessing,'DD/MM/YYYY HH24:MI:SS') mintime, 
to_char(pxlastexecutiondatetime,'DD/MM/YYYY HH24:MI:SS') lastrunat, pxobjclass, 
pyagentname, pxprocessingnodeid, pyattempts, pymaxattempts, pyitemid, 
pyitemstatus, pzinskey, 
pyselectid, pypriority 
from pr_sys_queues 
where pxinsname like 'SYSTEM-QUEUE-SCHEDULEDTASK 14102%' 


8. In SMA: Navigate to Agent Management > Agents and start the ScheduledTaskProcess agent 
9. In SQL: Re-examine the pr_sys_queues entry. This should show that the pyMinimumDateTimeForProcessing has been updated to tomorrow 
10. If you have configured an email server then you should have also received an email. 
11. In SMA: Stop the ScheduledTaskProcess agent 
12. In PRPC Developer portal: From the Pega button choose, Reporting > Components > Scheduled Tasks
13. Open the newly created Schedule Task 
14. Click the Update button 
15. Click the Delete button 
16. In SQL: Run the query against pr_sys_queues. This should show that the row has disappeared 
17. In Case Manager portal: Refresh the screen. 
18. Right click on the same report and click Schedule button. 
19. Click Reopen button 
20. Click Submit button. 
21. In SQL: Examine the row and verify that some of the required columns are blank.


Resolution



Apply HFix-10381.


SECONDARY CAUSE

After HFix-10381 was supplied to address the problem of the pr_sys_queues entries not being picked up by the ScheduledTaskProcess agent, the administraters were observing another problem relating to the authentication. This was displaying the following exception in the logs.


2014-12-03 14:26:41,870 [        http-8443-10] [Components] [      PegaNBAM:06.03] (pega_integrationengine_default) ERROR COMPANYNAME.CLOUD.com|127.0.0.1
username - Unexpected exception caught while trying to send an email message.
com.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required
    at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1515)
    at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1054)
    at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:634)
    at com.pegarules.generated.SendEmailMessage_060301_QsQ8aHDPfHDWdFzadW7ALQ.SendEmailMessage06_03_01(SendEmailMessage_060301_QsQ8aHDPfHDWdFzadW7ALQ.java:659)
    at com.pegarules.generated.SendEmailMessage_060301_QsQ8aHDPfHDWdFzadW7ALQ.invoke(SendEmailMessage_060301_QsQ8aHDPfHDWdFzadW7ALQ.java:87)
    at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:132)
    at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:109)
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:7975)
    at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(LibrarySupport.java:181)
    at com.pegarules.generated.pega_integrationengine_default.SendEmailMessage(pega_integrationengine_default.java:149)
    at com.pegarules.generated.activity.ra_action_sendemailnotification_e431bfe12e014fd73034ad04d8a4d15d.step6_circum0(ra_action_sendemailnotification_e431bfe12e014fd73034ad04d8a4d15d.java:998)
    at com.pegarules.generated.activity.ra_action_sendemailnotification_e431bfe12e014fd73034ad04d8a4d15d.perform(ra_action_sendemailnotification_e431bfe12e014fd73034ad04d8a4d15d.java:170)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3040)
    at com.pegarules.generated.activity.ra_action_sendemailnotificationwithattachments_4554269142c8e444ca5d88648e1fd450.step1_circum0(ra_action_sendemailnotificationwithattachments_4554269142c8e444ca5d88648e1fd450.java:197)
    at com.pegarules.generated.activity.ra_action_sendemailnotificationwithattachments_4554269142c8e444ca5d88648e1fd450.perform(ra_action_sendemailnotificationwithattachments_4554269142c8e444ca5d88648e1fd450.java:72)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3040)
...


The configuration in this instance was using SMPTS which should have been passing the user credentials in the hashmap that was passed to the sendMessage call.

RESOLUTION

Apply HFix-20458.
 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us