Print Layout feature showing black

Today I received a Windows Update that included SQL 2005 SP2. Since
that time whenever I try to use the "Print Layout" feature in
Reporting Services, it shows nothing but black. Does anyone know of a
fix for this?Here you go: http://support.microsoft.com/kb/935356/en-us
This is the new cumulative update that should fix your issue. You'll need
to follow the steps on the page to request the fix.
This is one of the bugs fixed:
50001105 After you apply SQL Server 2005 SP2, the Print Preview feature in
Reporting Services may show a solid black page.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: cphite@.gmail.com
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: Print Layout feature showing black
> Date: Thu, 04 Oct 2007 13:17:24 -0700
> Today I received a Windows Update that included SQL 2005 SP2. Since
> that time whenever I try to use the "Print Layout" feature in
> Reporting Services, it shows nothing but black. Does anyone know of a
> fix for this?
>|||On Oct 4, 4:52 pm, cal...@.online.microsoft.com (Chris Alton [MSFT])
wrote:
> Here you go:http://support.microsoft.com/kb/935356/en-us
> This is the new cumulative update that should fix your issue. You'll need
> to follow the steps on the page to request the fix.
Thanks, Chris - that worked perfectly.|||Great. You wern't the only person I've seen that had that problem.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: cphite@.gmail.com
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: Re: Print Layout feature showing black
> Date: Fri, 05 Oct 2007 07:56:08 -0700
> Organization: http://groups.google.com
> On Oct 4, 4:52 pm, cal...@.online.microsoft.com (Chris Alton [MSFT])
> wrote:
> > Here you go:http://support.microsoft.com/kb/935356/en-us
> >
> > This is the new cumulative update that should fix your issue. You'll
need
> > to follow the steps on the page to request the fix.
> Thanks, Chris - that worked perfectly.
>