Failure sending mail: The transport lost its connection to the server

More and more often, I am seeing this error message in RS subscriptions. I would assume it means the IIS server can't connect to the corporate exchange server. However I was wondering if there is some timeout setting/configuration in RS or the IIS server (or any other kind of setting) I can change to help alleviate this problem.

Has anyone else experienced this? Or know how to fix it?

Thanks,

Jeff

UPDATE: After looking closer at the subscriptions, I have noticed that subscriptions set up by a RS Admin (who is also a server admin) seem to be working fine. It is the subscriptions that are set up by ordinary users that are failing...

We are getting this error for large reports being sent as Excel files. I think it's actually doing what it says: it's losing it's connection to the Exchange Server. I would think that makes it an Exchange configuration problem. Not sure tho. Any ideas?
|||I checked the log on this. It's an actual "no response" from the email server (0x800ccc13).Error sending email. System.Runtime.InteropServices.COMException (0x80040211): The message could not be sent to the SMTP server. The transport error code was 0x800ccc13. The server response was not available at ReportingServicesCDOInterop.MessageClass.Send() at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.Deliver(Notification notification)|||

This looks like an email server availability issue. Have you checked with your IT folks about the availability of the server?

There should be no difference between subscriptions created by administrators and those created by end users. All E-mail messages are sent to the email server using the same account.

-Lukasz

|||It's not the email server - according the the logs. It appears to be a problem exporting huge reports to Excel. The email server is not even receiving a HELO request. Reports scheduled just before and after are being sent, and if we reduce the date span or switch the format to CSV, it sends successfully.
|||

There are a number of threads on exporting large reports to excel and other formats.

For a run down of some of the solution vectors you can look at the posts from Brian and Bruce on this thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=22652&SiteID=1

Hope that helps,

-Lukasz

|||Thanks, but none of them actually provide a solution...that works.
|||

Are you able to make the export to excel fail when you render the report interactively? How much data are you putting in your excel file?

-Lukasz

|||I have the same problem, I have a large report that renders 26,301 rows for Excel. When I setup the subscription in Report Services with the Excel render option, I get the status message - 'Failure sending mail: The transport lost its connection to the server', even though it renders the report interactively just fine. Any idea on what is causing this problem or how to fix it?|||

Check the email server your using for timeouts on sending messages or size restrictions on outbound messages. It could be that your 20K+ row excel doc maxes out the email server capability. You may be able to find information in the email server logs related to the request. From the error, it appears report server was successfully communicating with the email server, but then the connection was lost part way through the send.

-Lukasz