"Tao Zuo" <TaoZuo@discussions.microsoft.com> wrote in message
news:5B418E2D-DB3C-4ACB-87CC-2A562D1BD643@microsoft.com...
> I posted this message below 11/18. Hope the hotfix (872774) can fix your
> problem?
>
> Tao
>
> The hotfix actually fixed a similiar issue of ours:
>
> Server A: Window 2003
> Reporting Server: SP1 8.00.878.00
> Issue: Excel Subscription Email Attachment Corrupted
> Email Server: Novell Netware
>
> Our two other environments/servers do not have problem:
> Server B: Windows 2000
> Reporting Server: RTM 8.00.743.00
>
> Server C: Windows 2000
> Reporting Server: SP1 8.00.878.00
>
> So I think there is something to do with Windows2003 and Non-Exchange mail
> server?
>
> Tao
>
> "Brian Welcker [MSFT]" wrote:
>
> > You can now download a hotfix that addresses this problem. See
> > http://support.microsoft.com/default.aspx?scid=kb;[LN];872774.
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Dennis Redfield" <dennis.redfield@acadia-ins.com> wrote in message
> > news:u%23hSrFWgEHA.4092@TK2MSFTNGP10.phx.gbl...
> > > OK, I am looking for help on how to break this problem up for
debugging.
> > > I
> > > am testing Email report schedules. We are working with files of type:
> > > TIF,PDF & EXCEL. I am able to schedule rendering reports to a FILE
SHARE
> > > successfully. I am able to email LINKS to reports successfully. When
I
> > > send files of these three types as Email ATTACHMENTS they arrive
corupted.
> > > The HEX dump is really ugly. Mostly FF bytes.... I am passing from RS
to
> > > a
> > > SMTP server is external to the RS server, which then passes the
reports
> > > to
> > > a NOTES server and then to me. The log file for RS shows nothing
unusual.
> > > How would you approach debuging this issue?
> > >
> > > thanks.
> > >
> > > dlr
> > >
> > >
> >
> >
> >
>
>
>
>
> Printer-Friendly Version Send This Page Add to Favorites Comments
>
>
> "Jean-Marc PUGIN" wrote:
>
> > Yes SP1 has been installed especially to target Excel 97 which is still
> > largely used in Main Corporations.
> >
> > The SAME Excel file is OK when send to a provider and KO when send to
> > another.
> >
> > We are searching Excel File characteristic that could put in trouble the
> > Corporation mail.
> >
> > Best Regards,
> >
> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message
> > news:e5sHU5I2EHA.1188@tk2msftngp13.phx.gbl...
> > > For #2, do you have SP1 installed. The format changed with SP1
allowing
> > > support for Excel 97/2000. If the customer server does not have SP1
and
> > they
> > > have Excel 97/2000 then that would account for the problem.
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Jean-Marc PUGIN" <jmpugin@mobileworkers.com> wrote in message
> > > news:%23WlET2I2EHA.1452@TK2MSFTNGP11.phx.gbl...
> > > > Hi,
> > > >
> > > > We are using Data Driven Subscription to deliver Excel files using
SMTP.
> > > >
> > > > Everything works fine on our Intranet.
> > > >
> > > > However we have problems to put in in Production for some customer
> > sites.
> > > >
> > > > We have several VERY STRANGE behavior:
> > > >
> > > > 1. the Excel file when read on the customer PC is "nearly" EMPTY (78
> > bytes
> > > > for example)
> > > > AND the file is INCORRECT for Excel (unable to load it into Excel).
> > > >
> > > > 2. the Excel file when read on the customer PC has the right size
(44 Ko
> > > for
> > > > example)
> > > > AND the file is INCORRECT for Excel (unable to load it into Excel).
> > > >
> > > > There is NEARLY zero info on RS books we have (excellent books btw)
so
> > > >
> > > > ANY help will be appreciated.
> > > >
> > > > Many Thanks
> > > >
> > > >
> > >
> > >
> >
> >
> >