Hi,
I'm actually in trouble with some of my reports. Those reports are randomly
producing corrupted PDF files in subscriptions.
The only way for me to avoid those errors is to remove report caching.
Here is my original post which explains tests i have made and patches i have
applied
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5e36216a-766a-40db-b230-997cdcba97a0
I'm really stuck right now and desesperatly looking for help.
Thanks in advance.
Grégory.What happens if you use the export feature to export the report? Does tha
produce a corrupted file?
What is the error that the Acrobat reader outputs when reading the file?
What version of the report server are you running - are you at SP1?
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Greg - NEOS" <GregNEOS@.discussions.microsoft.com> wrote in message
news:E14E2070-1887-4F69-955A-B1AD0CE8D3FD@.microsoft.com...
> Hi,
> I'm actually in trouble with some of my reports. Those reports are
> randomly
> producing corrupted PDF files in subscriptions.
> The only way for me to avoid those errors is to remove report caching.
> Here is my original post which explains tests i have made and patches i
> have
> applied:
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5e36216a-766a-40db-b230-997cdcba97a0
> I'm really stuck right now and desesperatly looking for help.
> Thanks in advance.
> Grégory.|||Hi Lukasz,
When I use export feature, the file isn't corrupted.
The error produced by Acrobat is: "An error happened when opening documents.
The file is corrupted and can't be repared".
I'm actually using Reporting Services SP1.
Best Regards,
Grégory.
"Lukasz Pawlowski [MSFT]" wrote:
> What happens if you use the export feature to export the report? Does tha
> produce a corrupted file?
> What is the error that the Acrobat reader outputs when reading the file?
> What version of the report server are you running - are you at SP1?
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Greg - NEOS" <GregNEOS@.discussions.microsoft.com> wrote in message
> news:E14E2070-1887-4F69-955A-B1AD0CE8D3FD@.microsoft.com...
> > Hi,
> >
> > I'm actually in trouble with some of my reports. Those reports are
> > randomly
> > producing corrupted PDF files in subscriptions.
> > The only way for me to avoid those errors is to remove report caching.
> >
> > Here is my original post which explains tests i have made and patches i
> > have
> > applied:
> > http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5e36216a-766a-40db-b230-997cdcba97a0
> >
> > I'm really stuck right now and desesperatly looking for help.
> >
> > Thanks in advance.
> > Grégory.
>
>
Showing posts with label pdf. Show all posts
Showing posts with label pdf. Show all posts
Tuesday, February 14, 2012
Corrupted PDF attachments in Reporting Services
We use subscriptions to send a list of people the same report in PDF format.
Most are our own employees (using Microsoft Exchange/Outlook) and the report
is fine. We are, however, having problems sending the report to Yahoo, AOL
and Hotmail users. Here are some tests we've done...
Test #1: I have run the report and exported it as a PDF, opening it
directly into Adobe fine.
Test #2: I then exported it, saved it to my drive, then emailed the report
as a attachment using Outlook /Exchange to my Hotmail account and the report
opens fine.
Test #3: I set up a subscription to email it to simultaneously to both my
Hotmail and Exchange accounts. The report attachment that went to my
Exchange account opens fine in Adobe. The one that arrived attached to the
email to my Hotmail account arrived in a format that Adobe does not
recognize. ("... either not a supported file type or because the file has
been corrupted. For example, it was sent as an email attachment and wasn't
corrected decoded.")
The problem isn't my computer nor a problem with my Adobe Reader. It's not
my Exchange server that is delivering it to my Exchange account (it's the
same server). It's not my Outlook email with attachment sent by Exchange to
Hotmail.
Considering the common path that each of these tests followed and
determining which one didn't work, it appears to me that most likely the
Report Server is not submitting the report to Exchange as an attachment in a
way that services such as Hotmail, AOL, Yahoo, etc can work with or it's
interaction with my mail server when preparing it to send outside my mail
server.
Any help on this? Is this acknowledged by Microsoft?
JonThere is a known issue with a Unicode byte order mark being written out to
the attachment part of the email. This has been fixed in a QFE posted here:
http://support.microsoft.com/default.aspx?scid=kb;[LN];872774
Please note, this fix fixes an attachment problem and not merely a problem
with LOTUS so don't be fooled by the title.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:ug8%23kLH5EHA.1192@.tk2msftngp13.phx.gbl...
> We use subscriptions to send a list of people the same report in PDF
> format. Most are our own employees (using Microsoft Exchange/Outlook) and
> the report is fine. We are, however, having problems sending the report
> to Yahoo, AOL and Hotmail users. Here are some tests we've done...
> Test #1: I have run the report and exported it as a PDF, opening it
> directly into Adobe fine.
> Test #2: I then exported it, saved it to my drive, then emailed the
> report as a attachment using Outlook /Exchange to my Hotmail account and
> the report opens fine.
> Test #3: I set up a subscription to email it to simultaneously to both
> my Hotmail and Exchange accounts. The report attachment that went to my
> Exchange account opens fine in Adobe. The one that arrived attached to
> the email to my Hotmail account arrived in a format that Adobe does not
> recognize. ("... either not a supported file type or because the file has
> been corrupted. For example, it was sent as an email attachment and
> wasn't corrected decoded.")
> The problem isn't my computer nor a problem with my Adobe Reader. It's
> not my Exchange server that is delivering it to my Exchange account (it's
> the same server). It's not my Outlook email with attachment sent by
> Exchange to Hotmail.
> Considering the common path that each of these tests followed and
> determining which one didn't work, it appears to me that most likely the
> Report Server is not submitting the report to Exchange as an attachment in
> a way that services such as Hotmail, AOL, Yahoo, etc can work with or it's
> interaction with my mail server when preparing it to send outside my mail
> server.
> Any help on this? Is this acknowledged by Microsoft?
> Jon
>|||Thanks, Daniel.
I've downloaded, installed, and tested the package. I works great now!
I wish the package ended with a message that it was successful, though. It
just closes and doesn't leave me feeling that it even completed, much less
successfully.
The DLLs in the .NET Framework area (temporary ASP.NET Files) were updated
but it worries me that the copies in the Reporting Serices folders
(..\ReportManager & ..\ReportServer) are still showing the old SP1 versions.
When will these get updated to versions 8.0.892?
Jon|||The QFE only updates the files necessary for the fix. You should notice
that the ReportingServicesEmailDeliveryProvider.dll assembly was updated.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:%23n3xu6H5EHA.2608@.TK2MSFTNGP10.phx.gbl...
> Thanks, Daniel.
> I've downloaded, installed, and tested the package. I works great now!
> I wish the package ended with a message that it was successful, though.
> It just closes and doesn't leave me feeling that it even completed, much
> less successfully.
> The DLLs in the .NET Framework area (temporary ASP.NET Files) were updated
> but it worries me that the copies in the Reporting Serices folders
> (..\ReportManager & ..\ReportServer) are still showing the old SP1
> versions. When will these get updated to versions 8.0.892?
> Jon
>|||Shouldn't I expect all instances of this dll to be updated?
I found that this .dll was updated in two places under the
C:\Windows\Microsoft.NET\Framework directory but not in the two places under
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\... The .dll
in the two \bin folders of both \ReportManager and \ReportServer still
reflected the older version, even after a reboot of the server.
Jon
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:eQvUOJI5EHA.4092@.TK2MSFTNGP14.phx.gbl...
> The QFE only updates the files necessary for the fix. You should notice
> that the ReportingServicesEmailDeliveryProvider.dll assembly was updated.
> --
> -Daniel|||I'm a little confused. Where exactly do you see the .dlls? There should
not be any at C:\Windows\Microsoft.NET\Framework (buried a little deeper are
some copies of the .dlls that live in the bin folders)
After the reboot, is the problem still fixed? If it is then that means the
correct .dlls should be installed.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:uQiGC5p5EHA.4040@.TK2MSFTNGP14.phx.gbl...
> Shouldn't I expect all instances of this dll to be updated?
> I found that this .dll was updated in two places under the
> C:\Windows\Microsoft.NET\Framework directory but not in the two places
> under C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\...
> The .dll in the two \bin folders of both \ReportManager and \ReportServer
> still reflected the older version, even after a reboot of the server.
> Jon
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:eQvUOJI5EHA.4092@.TK2MSFTNGP14.phx.gbl...
>> The QFE only updates the files necessary for the fix. You should notice
>> that the ReportingServicesEmailDeliveryProvider.dll assembly was updated.
>> --
>> -Daniel
>|||I just took a closer look and don't think I still have a problem. Still,
there are a couple of oddities.
First, there really are four copies of these files on my system:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager\Bin
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\Bin
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
> Files\reports\5fc3e315\219a7509\assembly\dl2\1463834f\0052e96b_be6ac401
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
> Files\reportserver\94eb9a55\49df36c9\assembly\dl2\3547c5bb\0052e96b_be6ac401
Second, the first two have a "date modified" of 07/15/04 and the last two
have dates of 12/17/04, the day I applied the patch. That was the confusing
part.
When I had initially looked at the file versions, the first two had older
file versions (ie, not the 8.0.892.0 that the new patch was to apply). When
I looked just now, however, (which is after a reboot), all the file versions
are 8.0.892.0, which is great.
Sorry to get us chasing what is apparently not an issue. I really
appreciate the quickness and accuracy of your replies.
Jon|||The last two files are the shadow copied files used by ASP.Net. By shadow
copying the files and using these files, this allows the original files to
be modified while the application is running. The modified dates are a
reflection of this copying.
I am not sure why you didn't see the new version info immediately after the
install. They should have been updated then.
Anyway, glad to hear that everything is up and running.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:%23leMrLs5EHA.3120@.TK2MSFTNGP12.phx.gbl...
>I just took a closer look and don't think I still have a problem. Still,
>there are a couple of oddities.
> First, there really are four copies of these files on my system:
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportManager\Bin
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\Bin
>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reports\5fc3e315\219a7509\assembly\dl2\1463834f\0052e96b_be6ac401
>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\assembly\dl2\3547c5bb\0052e96b_be6ac401
> Second, the first two have a "date modified" of 07/15/04 and the last two
> have dates of 12/17/04, the day I applied the patch. That was the
> confusing part.
> When I had initially looked at the file versions, the first two had older
> file versions (ie, not the 8.0.892.0 that the new patch was to apply).
> When I looked just now, however, (which is after a reboot), all the file
> versions are 8.0.892.0, which is great.
> Sorry to get us chasing what is apparently not an issue. I really
> appreciate the quickness and accuracy of your replies.
> Jon
>
Most are our own employees (using Microsoft Exchange/Outlook) and the report
is fine. We are, however, having problems sending the report to Yahoo, AOL
and Hotmail users. Here are some tests we've done...
Test #1: I have run the report and exported it as a PDF, opening it
directly into Adobe fine.
Test #2: I then exported it, saved it to my drive, then emailed the report
as a attachment using Outlook /Exchange to my Hotmail account and the report
opens fine.
Test #3: I set up a subscription to email it to simultaneously to both my
Hotmail and Exchange accounts. The report attachment that went to my
Exchange account opens fine in Adobe. The one that arrived attached to the
email to my Hotmail account arrived in a format that Adobe does not
recognize. ("... either not a supported file type or because the file has
been corrupted. For example, it was sent as an email attachment and wasn't
corrected decoded.")
The problem isn't my computer nor a problem with my Adobe Reader. It's not
my Exchange server that is delivering it to my Exchange account (it's the
same server). It's not my Outlook email with attachment sent by Exchange to
Hotmail.
Considering the common path that each of these tests followed and
determining which one didn't work, it appears to me that most likely the
Report Server is not submitting the report to Exchange as an attachment in a
way that services such as Hotmail, AOL, Yahoo, etc can work with or it's
interaction with my mail server when preparing it to send outside my mail
server.
Any help on this? Is this acknowledged by Microsoft?
JonThere is a known issue with a Unicode byte order mark being written out to
the attachment part of the email. This has been fixed in a QFE posted here:
http://support.microsoft.com/default.aspx?scid=kb;[LN];872774
Please note, this fix fixes an attachment problem and not merely a problem
with LOTUS so don't be fooled by the title.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:ug8%23kLH5EHA.1192@.tk2msftngp13.phx.gbl...
> We use subscriptions to send a list of people the same report in PDF
> format. Most are our own employees (using Microsoft Exchange/Outlook) and
> the report is fine. We are, however, having problems sending the report
> to Yahoo, AOL and Hotmail users. Here are some tests we've done...
> Test #1: I have run the report and exported it as a PDF, opening it
> directly into Adobe fine.
> Test #2: I then exported it, saved it to my drive, then emailed the
> report as a attachment using Outlook /Exchange to my Hotmail account and
> the report opens fine.
> Test #3: I set up a subscription to email it to simultaneously to both
> my Hotmail and Exchange accounts. The report attachment that went to my
> Exchange account opens fine in Adobe. The one that arrived attached to
> the email to my Hotmail account arrived in a format that Adobe does not
> recognize. ("... either not a supported file type or because the file has
> been corrupted. For example, it was sent as an email attachment and
> wasn't corrected decoded.")
> The problem isn't my computer nor a problem with my Adobe Reader. It's
> not my Exchange server that is delivering it to my Exchange account (it's
> the same server). It's not my Outlook email with attachment sent by
> Exchange to Hotmail.
> Considering the common path that each of these tests followed and
> determining which one didn't work, it appears to me that most likely the
> Report Server is not submitting the report to Exchange as an attachment in
> a way that services such as Hotmail, AOL, Yahoo, etc can work with or it's
> interaction with my mail server when preparing it to send outside my mail
> server.
> Any help on this? Is this acknowledged by Microsoft?
> Jon
>|||Thanks, Daniel.
I've downloaded, installed, and tested the package. I works great now!
I wish the package ended with a message that it was successful, though. It
just closes and doesn't leave me feeling that it even completed, much less
successfully.
The DLLs in the .NET Framework area (temporary ASP.NET Files) were updated
but it worries me that the copies in the Reporting Serices folders
(..\ReportManager & ..\ReportServer) are still showing the old SP1 versions.
When will these get updated to versions 8.0.892?
Jon|||The QFE only updates the files necessary for the fix. You should notice
that the ReportingServicesEmailDeliveryProvider.dll assembly was updated.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:%23n3xu6H5EHA.2608@.TK2MSFTNGP10.phx.gbl...
> Thanks, Daniel.
> I've downloaded, installed, and tested the package. I works great now!
> I wish the package ended with a message that it was successful, though.
> It just closes and doesn't leave me feeling that it even completed, much
> less successfully.
> The DLLs in the .NET Framework area (temporary ASP.NET Files) were updated
> but it worries me that the copies in the Reporting Serices folders
> (..\ReportManager & ..\ReportServer) are still showing the old SP1
> versions. When will these get updated to versions 8.0.892?
> Jon
>|||Shouldn't I expect all instances of this dll to be updated?
I found that this .dll was updated in two places under the
C:\Windows\Microsoft.NET\Framework directory but not in the two places under
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\... The .dll
in the two \bin folders of both \ReportManager and \ReportServer still
reflected the older version, even after a reboot of the server.
Jon
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:eQvUOJI5EHA.4092@.TK2MSFTNGP14.phx.gbl...
> The QFE only updates the files necessary for the fix. You should notice
> that the ReportingServicesEmailDeliveryProvider.dll assembly was updated.
> --
> -Daniel|||I'm a little confused. Where exactly do you see the .dlls? There should
not be any at C:\Windows\Microsoft.NET\Framework (buried a little deeper are
some copies of the .dlls that live in the bin folders)
After the reboot, is the problem still fixed? If it is then that means the
correct .dlls should be installed.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:uQiGC5p5EHA.4040@.TK2MSFTNGP14.phx.gbl...
> Shouldn't I expect all instances of this dll to be updated?
> I found that this .dll was updated in two places under the
> C:\Windows\Microsoft.NET\Framework directory but not in the two places
> under C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\...
> The .dll in the two \bin folders of both \ReportManager and \ReportServer
> still reflected the older version, even after a reboot of the server.
> Jon
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:eQvUOJI5EHA.4092@.TK2MSFTNGP14.phx.gbl...
>> The QFE only updates the files necessary for the fix. You should notice
>> that the ReportingServicesEmailDeliveryProvider.dll assembly was updated.
>> --
>> -Daniel
>|||I just took a closer look and don't think I still have a problem. Still,
there are a couple of oddities.
First, there really are four copies of these files on my system:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager\Bin
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\Bin
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
> Files\reports\5fc3e315\219a7509\assembly\dl2\1463834f\0052e96b_be6ac401
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
> Files\reportserver\94eb9a55\49df36c9\assembly\dl2\3547c5bb\0052e96b_be6ac401
Second, the first two have a "date modified" of 07/15/04 and the last two
have dates of 12/17/04, the day I applied the patch. That was the confusing
part.
When I had initially looked at the file versions, the first two had older
file versions (ie, not the 8.0.892.0 that the new patch was to apply). When
I looked just now, however, (which is after a reboot), all the file versions
are 8.0.892.0, which is great.
Sorry to get us chasing what is apparently not an issue. I really
appreciate the quickness and accuracy of your replies.
Jon|||The last two files are the shadow copied files used by ASP.Net. By shadow
copying the files and using these files, this allows the original files to
be modified while the application is running. The modified dates are a
reflection of this copying.
I am not sure why you didn't see the new version info immediately after the
install. They should have been updated then.
Anyway, glad to hear that everything is up and running.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Limmer" <jlimmer@.gmbeverage.com> wrote in message
news:%23leMrLs5EHA.3120@.TK2MSFTNGP12.phx.gbl...
>I just took a closer look and don't think I still have a problem. Still,
>there are a couple of oddities.
> First, there really are four copies of these files on my system:
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportManager\Bin
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\Bin
>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reports\5fc3e315\219a7509\assembly\dl2\1463834f\0052e96b_be6ac401
>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> Files\reportserver\94eb9a55\49df36c9\assembly\dl2\3547c5bb\0052e96b_be6ac401
> Second, the first two have a "date modified" of 07/15/04 and the last two
> have dates of 12/17/04, the day I applied the patch. That was the
> confusing part.
> When I had initially looked at the file versions, the first two had older
> file versions (ie, not the 8.0.892.0 that the new patch was to apply).
> When I looked just now, however, (which is after a reboot), all the file
> versions are 8.0.892.0, which is great.
> Sorry to get us chasing what is apparently not an issue. I really
> appreciate the quickness and accuracy of your replies.
> Jon
>
Corrupted PDF attachments
Hi,
I'm running into a problem with PDF attachments on a specific report. It
happens that the attached PDF file is low-sized and Acrobat tells me that the
file is corrupted.
I've tried to apply the following fix on my RS server
http://support.microsoft.com/default.aspx?scid=kb;[LN];872774
But it changed nothing...
Is there another way to fix it ?
I'm using RS SP1 on a WIN2K3 server.
Thanx in advance.In addition to that, i've noticed following line in the log files, when
subscriptions are launched:
ReportingServicesService!chunks!1c08!12/07/2004-07:30:10:: i INFO: ###
GetReportChunk('RenderingInfo_PDF', 2), chunk was not found!
this=90ae42e5-8b6b-49f3-b13f-481b10c2fd93
"Greg - NEOS" wrote:
> Hi,
> I'm running into a problem with PDF attachments on a specific report. It
> happens that the attached PDF file is low-sized and Acrobat tells me that the
> file is corrupted.
> I've tried to apply the following fix on my RS server
> http://support.microsoft.com/default.aspx?scid=kb;[LN];872774
> But it changed nothing...
> Is there another way to fix it ?
> I'm using RS SP1 on a WIN2K3 server.
> Thanx in advance.|||Greg - NEOS wrote:
> I'm running into a problem with PDF attachments on a specific report. It
> happens that the attached PDF file is low-sized and Acrobat tells me that the
> file is corrupted.
If you view the PDF in notepad, do you see an html error near the
bottom? If so, what is that error? Also, take a look at the log files
in the LogFiles directory. Do a search for lines labeled as "e ERROR".
What do you find?
Donovan Smith
--
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Donovan
There's no error visible in the PDF file when i open it with notepad.
There are no errors in the logfiles either.
If it can help, targeted report is a snapshot.
Thanks for you support.
Best Regards,
Grégory.
"Donovan R. Smith [MS]" wrote:
> Greg - NEOS wrote:
> > I'm running into a problem with PDF attachments on a specific report. It
> > happens that the attached PDF file is low-sized and Acrobat tells me that the
> > file is corrupted.
> If you view the PDF in notepad, do you see an html error near the
> bottom? If so, what is that error? Also, take a look at the log files
> in the LogFiles directory. Do a search for lines labeled as "e ERROR".
> What do you find?
> Donovan Smith
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Greg - NEOS wrote:
> There's no error visible in the PDF file when i open it with notepad.
> There are no errors in the logfiles either.
If you render the file to a share vs as an email attachment, is the PDF
still corrupted?
Donovan Smith
--
This posting is provided "AS IS" with no warranties, and confers no rights.|||Donovan,
Files rendered to a share are corrupted too.
I've tried to change execution mode for this report. PDF attachments are
still corrupted when i enable temporary cache copy for this report.
But if i change it to render this report without any cache... everything
goes fine!
We send in PDF format other reports on our server using cache or snapshot
mecanism without problems.
Could it be something in this specific report structure preventing it from
being correctly rendered to a PDF file when report is cached or snapshoted ?
Best Regards,
Gregory.
"Donovan R. Smith [MS]" wrote:
> Greg - NEOS wrote:
> > There's no error visible in the PDF file when i open it with notepad.
> > There are no errors in the logfiles either.
> If you render the file to a share vs as an email attachment, is the PDF
> still corrupted?
> Donovan Smith
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi,
I'm still stuck with those corrupted PDF attachments.
Any Idea ?
Thanks in advance.
Grégory.
"Greg - NEOS" wrote:
> Donovan,
> Files rendered to a share are corrupted too.
> I've tried to change execution mode for this report. PDF attachments are
> still corrupted when i enable temporary cache copy for this report.
> But if i change it to render this report without any cache... everything
> goes fine!
> We send in PDF format other reports on our server using cache or snapshot
> mecanism without problems.
> Could it be something in this specific report structure preventing it from
> being correctly rendered to a PDF file when report is cached or snapshoted ?
> Best Regards,
> Gregory.
> "Donovan R. Smith [MS]" wrote:
> > Greg - NEOS wrote:
> > > There's no error visible in the PDF file when i open it with notepad.
> > > There are no errors in the logfiles either.
> >
> > If you render the file to a share vs as an email attachment, is the PDF
> > still corrupted?
> >
> > Donovan Smith
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >|||Hi,
I'm still stuck with those corrupted PDF attachments.
Any Idea ?
Thanks in advance.
Grégory.
"Greg - NEOS" wrote:
> Donovan,
> Files rendered to a share are corrupted too.
> I've tried to change execution mode for this report. PDF attachments are
> still corrupted when i enable temporary cache copy for this report.
> But if i change it to render this report without any cache... everything
> goes fine!
> We send in PDF format other reports on our server using cache or snapshot
> mecanism without problems.
> Could it be something in this specific report structure preventing it from
> being correctly rendered to a PDF file when report is cached or snapshoted ?
> Best Regards,
> Gregory.
> "Donovan R. Smith [MS]" wrote:
> > Greg - NEOS wrote:
> > > There's no error visible in the PDF file when i open it with notepad.
> > > There are no errors in the logfiles either.
> >
> > If you render the file to a share vs as an email attachment, is the PDF
> > still corrupted?
> >
> > Donovan Smith
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
I'm running into a problem with PDF attachments on a specific report. It
happens that the attached PDF file is low-sized and Acrobat tells me that the
file is corrupted.
I've tried to apply the following fix on my RS server
http://support.microsoft.com/default.aspx?scid=kb;[LN];872774
But it changed nothing...
Is there another way to fix it ?
I'm using RS SP1 on a WIN2K3 server.
Thanx in advance.In addition to that, i've noticed following line in the log files, when
subscriptions are launched:
ReportingServicesService!chunks!1c08!12/07/2004-07:30:10:: i INFO: ###
GetReportChunk('RenderingInfo_PDF', 2), chunk was not found!
this=90ae42e5-8b6b-49f3-b13f-481b10c2fd93
"Greg - NEOS" wrote:
> Hi,
> I'm running into a problem with PDF attachments on a specific report. It
> happens that the attached PDF file is low-sized and Acrobat tells me that the
> file is corrupted.
> I've tried to apply the following fix on my RS server
> http://support.microsoft.com/default.aspx?scid=kb;[LN];872774
> But it changed nothing...
> Is there another way to fix it ?
> I'm using RS SP1 on a WIN2K3 server.
> Thanx in advance.|||Greg - NEOS wrote:
> I'm running into a problem with PDF attachments on a specific report. It
> happens that the attached PDF file is low-sized and Acrobat tells me that the
> file is corrupted.
If you view the PDF in notepad, do you see an html error near the
bottom? If so, what is that error? Also, take a look at the log files
in the LogFiles directory. Do a search for lines labeled as "e ERROR".
What do you find?
Donovan Smith
--
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Donovan
There's no error visible in the PDF file when i open it with notepad.
There are no errors in the logfiles either.
If it can help, targeted report is a snapshot.
Thanks for you support.
Best Regards,
Grégory.
"Donovan R. Smith [MS]" wrote:
> Greg - NEOS wrote:
> > I'm running into a problem with PDF attachments on a specific report. It
> > happens that the attached PDF file is low-sized and Acrobat tells me that the
> > file is corrupted.
> If you view the PDF in notepad, do you see an html error near the
> bottom? If so, what is that error? Also, take a look at the log files
> in the LogFiles directory. Do a search for lines labeled as "e ERROR".
> What do you find?
> Donovan Smith
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Greg - NEOS wrote:
> There's no error visible in the PDF file when i open it with notepad.
> There are no errors in the logfiles either.
If you render the file to a share vs as an email attachment, is the PDF
still corrupted?
Donovan Smith
--
This posting is provided "AS IS" with no warranties, and confers no rights.|||Donovan,
Files rendered to a share are corrupted too.
I've tried to change execution mode for this report. PDF attachments are
still corrupted when i enable temporary cache copy for this report.
But if i change it to render this report without any cache... everything
goes fine!
We send in PDF format other reports on our server using cache or snapshot
mecanism without problems.
Could it be something in this specific report structure preventing it from
being correctly rendered to a PDF file when report is cached or snapshoted ?
Best Regards,
Gregory.
"Donovan R. Smith [MS]" wrote:
> Greg - NEOS wrote:
> > There's no error visible in the PDF file when i open it with notepad.
> > There are no errors in the logfiles either.
> If you render the file to a share vs as an email attachment, is the PDF
> still corrupted?
> Donovan Smith
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi,
I'm still stuck with those corrupted PDF attachments.
Any Idea ?
Thanks in advance.
Grégory.
"Greg - NEOS" wrote:
> Donovan,
> Files rendered to a share are corrupted too.
> I've tried to change execution mode for this report. PDF attachments are
> still corrupted when i enable temporary cache copy for this report.
> But if i change it to render this report without any cache... everything
> goes fine!
> We send in PDF format other reports on our server using cache or snapshot
> mecanism without problems.
> Could it be something in this specific report structure preventing it from
> being correctly rendered to a PDF file when report is cached or snapshoted ?
> Best Regards,
> Gregory.
> "Donovan R. Smith [MS]" wrote:
> > Greg - NEOS wrote:
> > > There's no error visible in the PDF file when i open it with notepad.
> > > There are no errors in the logfiles either.
> >
> > If you render the file to a share vs as an email attachment, is the PDF
> > still corrupted?
> >
> > Donovan Smith
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >|||Hi,
I'm still stuck with those corrupted PDF attachments.
Any Idea ?
Thanks in advance.
Grégory.
"Greg - NEOS" wrote:
> Donovan,
> Files rendered to a share are corrupted too.
> I've tried to change execution mode for this report. PDF attachments are
> still corrupted when i enable temporary cache copy for this report.
> But if i change it to render this report without any cache... everything
> goes fine!
> We send in PDF format other reports on our server using cache or snapshot
> mecanism without problems.
> Could it be something in this specific report structure preventing it from
> being correctly rendered to a PDF file when report is cached or snapshoted ?
> Best Regards,
> Gregory.
> "Donovan R. Smith [MS]" wrote:
> > Greg - NEOS wrote:
> > > There's no error visible in the PDF file when i open it with notepad.
> > > There are no errors in the logfiles either.
> >
> > If you render the file to a share vs as an email attachment, is the PDF
> > still corrupted?
> >
> > Donovan Smith
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
Subscribe to:
Posts (Atom)