I created a data driven subscription for a report that will email a copy of the report based on a parameter passed from a table. The report runs successfully as indicated in Report Manager but the email is not delivered. I checked the ReportServerService log file and a message states that the report was sent to the proper email address. There is another log, ReportServerWebApp, that shows the message "The extension Report Server Email does not have a LocalizedNameAttribute" .
I created a regular subscription and it emails the report successfully so it can't be the SMTP server.
Any ideas how I can fix this problem with the Data Driven Subscription? Thank you.
David
I did some further checking. If I send off a second job, it delivers the emailed reports. However, the problem persists with the second job.That is, Reporting Services indicates that the job ran successfully and delivered the reports, but some of the reports are getting stuck in a queue somewhere between the reporting server, the remote SMTP server and Microsoft Exchange.
Is there anyone else having problems with Reporting Services reports not getting fully delivered by a remote SMTP server? Would using a local SMTP server fix the problem?
David
|||Sorry for the delay with replying this. From the SSRS prospective your data driven subscription has been delivered to SMTP server successfully. Then SMTP server failed to deliver e-mal. Any chance that e-mail TO address is build off a data-driven subscription query results and is incorrect? Per every successfully sent e-mail SSRS will write into the service logfile ReportServerService__<Date>.log a line: Email successfully sent to {0}. Can you double check that TO addresses are correct for the cases that you thin are failing?|||All of the reports are being sent to the same email address. Some get there successfully, others don't make it out of the queue.
David
|||Then it really looks like a problem with SMTP server. It’s likely not related to SSRS.
-Igor
No comments:
Post a Comment