Monday, February 20, 2012

large excel reports not being emailed

*this was also posted on the web forum
sql 2005 sp2
exchange 2003 sp2
i've got the report server setup to relay through the exchange server for
delivering reports. all reports are exported to excel and emailed
successfully with the exception of the largest report at about 16mb. the smtp
logs on the exchange server show the report server starting a session but no
"DATA" is every sent for this report and emails do not arrive. i am assuming
due to the size of the report there is some timeout out issue between the
smtp client and server. any ideas on how to resolve this issue? maybe a
timeout setting on the exchange smtp server? i'm trying to avoid installing a
local smtp server on the report server.
thanks in advance
nitzOn Oct 9, 12:33 pm, nitz <n...@.discussions.microsoft.com> wrote:
> *this was also posted on the web forum
> sql 2005 sp2
> exchange 2003 sp2
> i've got the report server setup to relay through the exchange server for
> delivering reports. all reports are exported to excel and emailed
> successfully with the exception of the largest report at about 16mb. the smtp
> logs on the exchange server show the report server starting a session but no
> "DATA" is every sent for this report and emails do not arrive. i am assuming
> due to the size of the report there is some timeout out issue between the
> smtp client and server. any ideas on how to resolve this issue? maybe a
> timeout setting on the exchange smtp server? i'm trying to avoid installing a
> local smtp server on the report server.
> thanks in advance
> nitz
You might want to start w/the root of IIS at the Default Website level
(right-click My Computer >> select Manage >> select Services and
Applications >> Internet Information Services >> Web Sites >> Default
Web Site >> right-click >> select Properties) and increase the timeout
value (Connection Timeout). Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||i've already increased the timeout value for previous reports. this might
have been a good idea if this report was experiencing a timeout when executed
from a web browser and exported to excel. however, it executes just fine with
the current webconfig settings. any other ideas?
i will note that when symantec AV internet email auto-protect option is
checked (this scans any outgoing smtp mail orginating from the client, not
just in outlook per say) it would log error stating the exhange server
disconnected the session. i did also try with AV disabled to make sure with
the same result.
thanks
"EMartinez" wrote:
> On Oct 9, 12:33 pm, nitz <n...@.discussions.microsoft.com> wrote:
> > *this was also posted on the web forum
> >
> > sql 2005 sp2
> >
> > exchange 2003 sp2
> >
> > i've got the report server setup to relay through the exchange server for
> > delivering reports. all reports are exported to excel and emailed
> > successfully with the exception of the largest report at about 16mb. the smtp
> > logs on the exchange server show the report server starting a session but no
> > "DATA" is every sent for this report and emails do not arrive. i am assuming
> > due to the size of the report there is some timeout out issue between the
> > smtp client and server. any ideas on how to resolve this issue? maybe a
> > timeout setting on the exchange smtp server? i'm trying to avoid installing a
> > local smtp server on the report server.
> >
> > thanks in advance
> >
> > nitz
>
> You might want to start w/the root of IIS at the Default Website level
> (right-click My Computer >> select Manage >> select Services and
> Applications >> Internet Information Services >> Web Sites >> Default
> Web Site >> right-click >> select Properties) and increase the timeout
> value (Connection Timeout). Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||It's possible the email is getting blocked due to it's size. Is there a
maximum email size defined in your exchange or filtering server (eg.
Mailmarshal) ? Also note, that due to smtp mime encoding, files sent out via
email are 20-30% larger than the actual file size due to the encoding.
"nitz" wrote:
> i've already increased the timeout value for previous reports. this might
> have been a good idea if this report was experiencing a timeout when executed
> from a web browser and exported to excel. however, it executes just fine with
> the current webconfig settings. any other ideas?
> i will note that when symantec AV internet email auto-protect option is
> checked (this scans any outgoing smtp mail orginating from the client, not
> just in outlook per say) it would log error stating the exhange server
> disconnected the session. i did also try with AV disabled to make sure with
> the same result.
> thanks
> "EMartinez" wrote:
> > On Oct 9, 12:33 pm, nitz <n...@.discussions.microsoft.com> wrote:
> > > *this was also posted on the web forum
> > >
> > > sql 2005 sp2
> > >
> > > exchange 2003 sp2
> > >
> > > i've got the report server setup to relay through the exchange server for
> > > delivering reports. all reports are exported to excel and emailed
> > > successfully with the exception of the largest report at about 16mb. the smtp
> > > logs on the exchange server show the report server starting a session but no
> > > "DATA" is every sent for this report and emails do not arrive. i am assuming
> > > due to the size of the report there is some timeout out issue between the
> > > smtp client and server. any ideas on how to resolve this issue? maybe a
> > > timeout setting on the exchange smtp server? i'm trying to avoid installing a
> > > local smtp server on the report server.
> > >
> > > thanks in advance
> > >
> > > nitz
> >
> >
> > You might want to start w/the root of IIS at the Default Website level
> > (right-click My Computer >> select Manage >> select Services and
> > Applications >> Internet Information Services >> Web Sites >> Default
> > Web Site >> right-click >> select Properties) and increase the timeout
> > value (Connection Timeout). Hope this helps.
> >
> > Regards,
> >
> > Enrique Martinez
> > Sr. Software Consultant
> >
> >

No comments:

Post a Comment