Books, articles on printing reports

I am a developer. I current have the Developer Edition of SQL Server 2000 on
my desktop and I am installing VB.Net 2003 and Reporting Services so that a
report, that uses data from a SQL Server 2000 database, can be printed.
I seek the minimal education available that will enable me to design this
report that my customers, who using the database, will print. Are there
suggestions for books or articles that meet this need?
Thanks.
JimMicrosoft SQL Server 2000 Reporting Services is pretty straight forward if
you avoid the filler about how the engine works (actually to be fair all the
books I've seen spend a lot of time on this), there is a better book but its
quite a bit more techy - hitch hikers guide to reporting services.
Phil
"James_101" <James101@.discussions.microsoft.com> wrote in message
news:F730DE37-5437-4E9C-BB8B-BA7776BDEBC9@.microsoft.com...
>I am a developer. I current have the Developer Edition of SQL Server 2000
>on
> my desktop and I am installing VB.Net 2003 and Reporting Services so that
> a
> report, that uses data from a SQL Server 2000 database, can be printed.
> I seek the minimal education available that will enable me to design this
> report that my customers, who using the database, will print. Are there
> suggestions for books or articles that meet this need?
> Thanks.
> Jim|||'Hitchhiker's Guide to SQL Server 2000 Reporting Services' is a very good
book on the subject ...
http://www.sqlreportingservices.net/
There are lot's of on-line resources here ...
http://msdn.microsoft.com/sql/2000/learn/bi/reporting/default.aspx
--
Brendan Reynolds
"James_101" <James101@.discussions.microsoft.com> wrote in message
news:F730DE37-5437-4E9C-BB8B-BA7776BDEBC9@.microsoft.com...
>I am a developer. I current have the Developer Edition of SQL Server 2000
>on
> my desktop and I am installing VB.Net 2003 and Reporting Services so that
> a
> report, that uses data from a SQL Server 2000 database, can be printed.
> I seek the minimal education available that will enable me to design this
> report that my customers, who using the database, will print. Are there
> suggestions for books or articles that meet this need?
> Thanks.
> Jim|||Best book I've read on RS is "CodeFez Guide to Reporting Services". They
released a PDF version a few weeks ago, PDF version is about $20. I found
it a lot easier to read than the others.
http://www.falafel.com/Products/tabid/58/CatalogItemID/19/CatalogID/1/psnavcmd/CatalogItemDetails/Default.aspx
--
Floyd
"James_101" <James101@.discussions.microsoft.com> wrote in message
news:F730DE37-5437-4E9C-BB8B-BA7776BDEBC9@.microsoft.com...
>I am a developer. I current have the Developer Edition of SQL Server 2000
>on
> my desktop and I am installing VB.Net 2003 and Reporting Services so that
> a
> report, that uses data from a SQL Server 2000 database, can be printed.
> I seek the minimal education available that will enable me to design this
> report that my customers, who using the database, will print. Are there
> suggestions for books or articles that meet this need?
> Thanks.
> Jim

Books Online Updated

Hi,
While installing the SQL Server 2000 Eval, I skipped Books Online since I
had previously downloaded the Books Online (Updated). I then installed the
updated version of Books Online. Now, when I try to access help from any of
the SQL Server tools like Query Analyzer, etc, nothing happens and no help
window comes up. I'd appreciate information on how to connect the SQL Server
installation to the updated Books Online.
Thanks for any help!
YogiFirst simply try re-installing the updated books on line..
If that doesn't work, go back to the SQL install, and do a custom install
and simply select ONLY install books.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Yogi PG" <yogipgNOSPAM@.NOSPAMhotmail.com> wrote in message
news:%23pNfXMXFEHA.712@.tk2msftngp13.phx.gbl...
> Hi,
> While installing the SQL Server 2000 Eval, I skipped Books Online since I
> had previously downloaded the Books Online (Updated). I then installed the
> updated version of Books Online. Now, when I try to access help from any
of
> the SQL Server tools like Query Analyzer, etc, nothing happens and no help
> window comes up. I'd appreciate information on how to connect the SQL
Server
> installation to the updated Books Online.
> Thanks for any help!
> Yogi
>

Books Online

Is there anywhere I can get Books Online for SQL Server 2005 without
installing the software?Not having seen it,
My guess would be to copy the .CHM files to your hard drive.
Rick Sawtell
MCT, MCSD, MCDBA
"Roy" <Roy@.discussions.microsoft.com> wrote in message
news:BA2E0FDF-668C-4B64-8F5D-EFCD8C24BA44@.microsoft.com...
> Is there anywhere I can get Books Online for SQL Server 2005 without
> installing the software?

blocking

I have seen spids blocking it self alot, after installing sql sp4.
As anyone notiice this?
Thanks,
Peter
yup
"peter" <peter@.discussions.microsoft.com> wrote in message
news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
>I have seen spids blocking it self alot, after installing sql sp4.
> As anyone notiice this?
> Thanks,
> Peter
|||Thanks for the response.
Is this a bug or does this cause performance issue?
"David J. Cartwright" wrote:

> yup
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
>
>
|||dont know if bug and i have not seen any performance degridation...although
i do not have a big transactional db...more of a warehouse type situation
with bulk inserts, which his where i have seen this occur, but they have not
slowed or taken more time
what have you seen ?
"peter" <peter@.discussions.microsoft.com> wrote in message
news:61F37E3E-9152-47C9-A2CB-5E5C03F3CA59@.microsoft.com...[vbcol=seagreen]
> Thanks for the response.
> Is this a bug or does this cause performance issue?
>
> "David J. Cartwright" wrote:
|||I have seen alot of blocking, which I did not see when I had sp3a.
"David J. Cartwright" wrote:

> dont know if bug and i have not seen any performance degridation...although
> i do not have a big transactional db...more of a warehouse type situation
> with bulk inserts, which his where i have seen this occur, but they have not
> slowed or taken more time
> what have you seen ?
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:61F37E3E-9152-47C9-A2CB-5E5C03F3CA59@.microsoft.com...
>
>

blocking

I have seen spids blocking it self alot, after installing sql sp4.
As anyone notiice this?
Thanks,
Peteryup
"peter" <peter@.discussions.microsoft.com> wrote in message
news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
>I have seen spids blocking it self alot, after installing sql sp4.
> As anyone notiice this?
> Thanks,
> Peter|||Thanks for the response.
Is this a bug or does this cause performance issue?
"David J. Cartwright" wrote:

> yup
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
>
>|||dont know if bug and i have not seen any performance degridation...although
i do not have a big transactional db...more of a warehouse type situation
with bulk inserts, which his where i have seen this occur, but they have not
slowed or taken more time
what have you seen ?
"peter" <peter@.discussions.microsoft.com> wrote in message
news:61F37E3E-9152-47C9-A2CB-5E5C03F3CA59@.microsoft.com...[vbcol=seagreen]
> Thanks for the response.
> Is this a bug or does this cause performance issue?
>
> "David J. Cartwright" wrote:
>|||I have seen alot of blocking, which I did not see when I had sp3a.
"David J. Cartwright" wrote:

> dont know if bug and i have not seen any performance degridation...althou
gh
> i do not have a big transactional db...more of a warehouse type situation
> with bulk inserts, which his where i have seen this occur, but they have n
ot
> slowed or taken more time
> what have you seen ?
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:61F37E3E-9152-47C9-A2CB-5E5C03F3CA59@.microsoft.com...
>
>

blocking

I have seen spids blocking it self alot, after installing sql sp4.
As anyone notiice this?
Thanks,
Peteryup
"peter" <peter@.discussions.microsoft.com> wrote in message
news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
>I have seen spids blocking it self alot, after installing sql sp4.
> As anyone notiice this?
> Thanks,
> Peter|||Thanks for the response.
Is this a bug or does this cause performance issue?
"David J. Cartwright" wrote:
> yup
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
> >I have seen spids blocking it self alot, after installing sql sp4.
> >
> > As anyone notiice this?
> >
> > Thanks,
> > Peter
>
>|||dont know if bug and i have not seen any performance degridation...although
i do not have a big transactional db...more of a warehouse type situation
with bulk inserts, which his where i have seen this occur, but they have not
slowed or taken more time
what have you seen ?
"peter" <peter@.discussions.microsoft.com> wrote in message
news:61F37E3E-9152-47C9-A2CB-5E5C03F3CA59@.microsoft.com...
> Thanks for the response.
> Is this a bug or does this cause performance issue?
>
> "David J. Cartwright" wrote:
>> yup
>> "peter" <peter@.discussions.microsoft.com> wrote in message
>> news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
>> >I have seen spids blocking it self alot, after installing sql sp4.
>> >
>> > As anyone notiice this?
>> >
>> > Thanks,
>> > Peter
>>|||I have seen alot of blocking, which I did not see when I had sp3a.
"David J. Cartwright" wrote:
> dont know if bug and i have not seen any performance degridation...although
> i do not have a big transactional db...more of a warehouse type situation
> with bulk inserts, which his where i have seen this occur, but they have not
> slowed or taken more time
> what have you seen ?
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:61F37E3E-9152-47C9-A2CB-5E5C03F3CA59@.microsoft.com...
> > Thanks for the response.
> >
> > Is this a bug or does this cause performance issue?
> >
> >
> > "David J. Cartwright" wrote:
> >
> >> yup
> >>
> >> "peter" <peter@.discussions.microsoft.com> wrote in message
> >> news:BCB6734A-0F85-46E8-B476-8F55C13A1132@.microsoft.com...
> >> >I have seen spids blocking it self alot, after installing sql sp4.
> >> >
> >> > As anyone notiice this?
> >> >
> >> > Thanks,
> >> > Peter
> >>
> >>
> >>
>
>

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.

Black server reports after installing SP2

After installing SQL Server 2005 SP2 all of our server reports are being rendered with a black background and white text, which needless to say is reversed of how they were being drawn before installing SP2. This only happens when the report viewer is displaying the report in “Print Layout” mode. Normal mode shows the report as expected.

Has anyone else had this problem or suggest a solution? Thanks in advance.

It turned out that this is an issue introduced with SP2 that affects certain video cards. I am also experiencing the same problem but t never occurred to me that this could be actually a bug during the SP2 testing so I never reported it back . The RS team is reviewing currently this issue. Please contact product support and request a hotfix when available.|||

user hotfix :

Replace the "Microsoft.ReportingServices.ImageRendering.dll" from SP2 with "Microsoft.ReportingServices.ImageRendering.dll" from SP1.
The directory is "x:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer\bin"

|||

Thanks for the feedback on this Michael. I thought this might work but afer replacing the ImageRendering.dll I get the following error:

"An attempt has been made to use a rendering extension that is not registered for this report server."

Did you get a similar result when you replaced this DLL with the original from SP1?

|||

I am having the same problem: Reports in Print Layout are rendered in a black background

|||As a workaround, you should be able to fix this issue by changing the background color to White instead of Transparent.|||

Yes, this work.

Tanks

|||Hi,

Does anyone know if there's a list yet of cards that have not been affected?

Cheers,
Martin
|||

I haven't heard of a resolution that is acceptable yet, with the exception of geting back through all the server reports and deliberatly making the background color white. I'm not too convinced this is nessesarily a video card issue, since every single machine we have seen this on is doing the back background.

Does anyone know if some sort of hotfix has been made available? Just copying in the old DLL from SP1 dosen't work.

|||

Hello,

This issue was indeed introduced in Yukon SP2. It only affects Report Designer preview, it doesn't matter what video card you have, the workaround is to specify background = white in the RDL, and we're working on a QFE.

Regards.

Mike

|||

I am also having the problem ;(

I was a beta tester for SP2, how did we let this slip through? I guess I don't normally use the print preview mode in the report viewer, but apparently my users do!

|||By the way, I have tried making the background white on these reports but there is still a lot of ugly black showing thorugh. I only see options to make the body, header, and footer white. Is there some other background property that I'm missing that would make the entire background of the report white including the margins?|||It didn't resolve the issue for me either. I am also getting blank pages on reports that worked fine before.|||Is there any timeframe for the hotfix on this? There seems to be nothing that we can do to eliminate the black in the margins of the reports and cannot roll back to SP1 in any way. Seems like the only open we have is to completely remove SQL Server and reinstall with SP1.|||I've contacted Microsoft Support about this and they said they couldn't offer a hotfix until there was a KB article number to go by. Is there any work being done to get this fixed? Our clients have been suffering with this problem for weeks now and the response from Microsoft has been mute. Any information would help.