Jump to content
We've recently updated our Privacy Statement, available here ×

in report splitting , the property attribute ${net.sf.jasperreports.print.part.email} not fetching value in the scheduler


Ahmed Mostafa

Recommended Posts

I am using jasper report server 8.2.0 

I used also jasper studio 9 . I am using the report splitter features which is working well except for the part for email notification that  the variable ${net.sf.jasperreports.print.part.email} put in " to" field  which accepted but not fetching data and reads it as it is  which yields into the following error upon execution:

ERROR ReportExecutionJob,JasperServerScheduler_Worker-1:472 - The job error notification was not completed. An error occurred while sending it. (Error UID: 4f16bf6d-c35a-4d78-a871-15e093ff17ac) org.springframework.mail.MailSendException: Failed messages: com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0 <348437779.2.1708718445024@Monitoring.procare.com> [InternalId=87763361726465, Hostname=PROCARE-EXCH1.procare.com] Queued mail for delivery
;
  nested exception is:
    com.sun.mail.smtp.SMTPAddressFailedException: 501 5.1.3 Invalid address
; message exception details (1) are:
Failed message 1:
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0 <348437779.2.1708718445024@Monitoring.procare.com> [InternalId=87763361726465, Hostname=PROCARE-EXCH1.procare.com] Queued mail for delivery
;
  nested exception is:
    com.sun.mail.smtp.SMTPAddressFailedException: 501 5.1.3 Invalid address

Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

Hello,

By looking to error it seems that the issue is in SMTP configuration.
Check the SMTP server configuration in JasperReports Server to ensure that it is properly configured and accessible. Verify the SMTP server address, port, authentication credentials, and any other relevant settings.

The error also suggest that invalid email adress. Could you please make sure email address is valid, you can test by directly putting email id without vairable.

Link to comment
Share on other sites

  • 2 weeks later...

The email settings configured correctly and tested before many times. The issue is that jasper scheduler passing the variables not fetching the email value and pass the attribute as it is which is not valid email so it gives this error. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...