Excel - Unable to read file error

hello,
I have had a particular .rdl report for quite some time, with some changes.
Recently, when trying to export to excel, I started getting an "unable to
read file" error. I have tried to manipulate the definition as much as
possible, but I am unable to get it to work.
The report is accessed via web services and uses an aspx file to handle the
download to desktop. I have SP2 installed.
anyone have any ideas? This seems like a common error, but havent seen a
solution to it.
c61I have a couple of posts out there on this but for some reason the Microsoft
folks and the MVPs don't reply? I would think that they would want to fix
a fatal flaw with their excel generator? Maybe my annoying tone will get
them to respond?
There is a hot fix available which may apply...
http://support.microsoft.com/?kbid=905121
... but they have not posted the fix on the web site. You have to call to
get the patch.
comet61 wrote:
>hello,
>I have had a particular .rdl report for quite some time, with some changes.
>Recently, when trying to export to excel, I started getting an "unable to
>read file" error. I have tried to manipulate the definition as much as
>possible, but I am unable to get it to work.
>The report is accessed via web services and uses an aspx file to handle the
>download to desktop. I have SP2 installed.
>anyone have any ideas? This seems like a common error, but havent seen a
>solution to it.
>c61
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200511/1|||I still have an error with the hotfix in place for a matrix style report to
excel. No manipulation gets it to work.
Microsoft?
"William N via SQLMonster.com" wrote:
> I have a couple of posts out there on this but for some reason the Microsoft
> folks and the MVPs don't reply? I would think that they would want to fix
> a fatal flaw with their excel generator? Maybe my annoying tone will get
> them to respond?
> There is a hot fix available which may apply...
> http://support.microsoft.com/?kbid=905121
> ... but they have not posted the fix on the web site. You have to call to
> get the patch.
>
> comet61 wrote:
> >hello,
> >
> >I have had a particular .rdl report for quite some time, with some changes.
> >Recently, when trying to export to excel, I started getting an "unable to
> >read file" error. I have tried to manipulate the definition as much as
> >possible, but I am unable to get it to work.
> >
> >The report is accessed via web services and uses an aspx file to handle the
> >download to desktop. I have SP2 installed.
> >
> >anyone have any ideas? This seems like a common error, but havent seen a
> >solution to it.
> >
> >c61
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200511/1
>|||I finally figured out the problem. We had put gzip compression on, on our
production servers, so downloading from the page was corrupting the info.
"comet61" wrote:
> I still have an error with the hotfix in place for a matrix style report to
> excel. No manipulation gets it to work.
> Microsoft?
> "William N via SQLMonster.com" wrote:
> > I have a couple of posts out there on this but for some reason the Microsoft
> > folks and the MVPs don't reply? I would think that they would want to fix
> > a fatal flaw with their excel generator? Maybe my annoying tone will get
> > them to respond?
> >
> > There is a hot fix available which may apply...
> >
> > http://support.microsoft.com/?kbid=905121
> >
> > ... but they have not posted the fix on the web site. You have to call to
> > get the patch.
> >
> >
> > comet61 wrote:
> > >hello,
> > >
> > >I have had a particular .rdl report for quite some time, with some changes.
> > >Recently, when trying to export to excel, I started getting an "unable to
> > >read file" error. I have tried to manipulate the definition as much as
> > >possible, but I am unable to get it to work.
> > >
> > >The report is accessed via web services and uses an aspx file to handle the
> > >download to desktop. I have SP2 installed.
> > >
> > >anyone have any ideas? This seems like a common error, but havent seen a
> > >solution to it.
> > >
> > >c61
> >
> >
> > --
> > Message posted via SQLMonster.com
> > http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200511/1
> >sql