Blue Screen of Death (BSOD) when printing

We have been using SQL 2005 reporting services for a while but recently when
some one tries to print a report they will get a BSOD and the machine reboots.
Any Ideas'?We are also having the same problem when printing, blue screen with error
message 0X80070709.
"Eric Wainz" wrote:
> We have been using SQL 2005 reporting services for a while but recently when
> some one tries to print a report they will get a BSOD and the machine reboots.
> Any Ideas'?
>|||On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> We are also having the same problem when printing, blue screen with error
> message 0X80070709.
> "Eric Wainz" wrote:
> > We have been using SQL 2005 reporting services for a while but recently when
> > some one tries to print a report they will get a BSOD and the machine reboots.
> > Any Ideas'?
It sounds kind of like a printer driver issue. Does this occur when
exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
etc) and then printing?
Enrique Martinez
Sr. Software Consultant|||No, It does not happen when you export the report.
But, We have been able to narrow it down to PCL6 print drivers.
"EMartinez" wrote:
> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> > We are also having the same problem when printing, blue screen with error
> > message 0X80070709.
> >
> > "Eric Wainz" wrote:
> > > We have been using SQL 2005 reporting services for a while but recently when
> > > some one tries to print a report they will get a BSOD and the machine reboots.
> >
> > > Any Ideas'?
>
> It sounds kind of like a printer driver issue. Does this occur when
> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
> etc) and then printing?
> Enrique Martinez
> Sr. Software Consultant
>|||It isn't a printer driver issue, it is the ActiveX control RSClientPrint
Class that is causing the problem. It seems to be happening after a recent
Windows Update, but I have not attributed it to any particular one. Go to
C:\windows\downloaded program files and delete the RSClientPrint Class and
run your report again. It should prompt you to download the control again
and printing should resume after that.
Wish I could flag this so MS could figure out why it is happening. It has
happened to two of my users and I am sure there will be more to follow.
"Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
> No, It does not happen when you export the report.
> But, We have been able to narrow it down to PCL6 print drivers.
> "EMartinez" wrote:
>> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
>> > We are also having the same problem when printing, blue screen with
>> > error
>> > message 0X80070709.
>> >
>> > "Eric Wainz" wrote:
>> > > We have been using SQL 2005 reporting services for a while but
>> > > recently when
>> > > some one tries to print a report they will get a BSOD and the machine
>> > > reboots.
>> >
>> > > Any Ideas'?
>>
>> It sounds kind of like a printer driver issue. Does this occur when
>> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
>> etc) and then printing?
>> Enrique Martinez
>> Sr. Software Consultant
>>|||I did that and still is rebooting.
"Rockn" wrote:
> It isn't a printer driver issue, it is the ActiveX control RSClientPrint
> Class that is causing the problem. It seems to be happening after a recent
> Windows Update, but I have not attributed it to any particular one. Go to
> C:\windows\downloaded program files and delete the RSClientPrint Class and
> run your report again. It should prompt you to download the control again
> and printing should resume after that.
> Wish I could flag this so MS could figure out why it is happening. It has
> happened to two of my users and I am sure there will be more to follow.
>
> "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
> news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
> > No, It does not happen when you export the report.
> >
> > But, We have been able to narrow it down to PCL6 print drivers.
> >
> > "EMartinez" wrote:
> >
> >> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> >> > We are also having the same problem when printing, blue screen with
> >> > error
> >> > message 0X80070709.
> >> >
> >> > "Eric Wainz" wrote:
> >> > > We have been using SQL 2005 reporting services for a while but
> >> > > recently when
> >> > > some one tries to print a report they will get a BSOD and the machine
> >> > > reboots.
> >> >
> >> > > Any Ideas'?
> >>
> >>
> >> It sounds kind of like a printer driver issue. Does this occur when
> >> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
> >> etc) and then printing?
> >>
> >> Enrique Martinez
> >> Sr. Software Consultant
> >>
> >>
>
>|||I am almost positive it is not a printer problem and I can almost bet the
problem started after a recent Windows Update. I tried my solution on one
person in the office and it seemed to fix it. I tried it on another
computer, but I wasn't logged on under his user account and it BSOD'd and
restarted.
"Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
news:3CEBEA69-C6F9-4B28-BE47-C8CF01A76118@.microsoft.com...
> I did that and still is rebooting.
> "Rockn" wrote:
> > It isn't a printer driver issue, it is the ActiveX control RSClientPrint
> > Class that is causing the problem. It seems to be happening after a
recent
> > Windows Update, but I have not attributed it to any particular one. Go
to
> > C:\windows\downloaded program files and delete the RSClientPrint Class
and
> > run your report again. It should prompt you to download the control
again
> > and printing should resume after that.
> >
> > Wish I could flag this so MS could figure out why it is happening. It
has
> > happened to two of my users and I am sure there will be more to follow.
> >
> >
> > "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
> > news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
> > > No, It does not happen when you export the report.
> > >
> > > But, We have been able to narrow it down to PCL6 print drivers.
> > >
> > > "EMartinez" wrote:
> > >
> > >> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> > >> > We are also having the same problem when printing, blue screen with
> > >> > error
> > >> > message 0X80070709.
> > >> >
> > >> > "Eric Wainz" wrote:
> > >> > > We have been using SQL 2005 reporting services for a while but
> > >> > > recently when
> > >> > > some one tries to print a report they will get a BSOD and the
machine
> > >> > > reboots.
> > >> >
> > >> > > Any Ideas'?
> > >>
> > >>
> > >> It sounds kind of like a printer driver issue. Does this occur when
> > >> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
> > >> etc) and then printing?
> > >>
> > >> Enrique Martinez
> > >> Sr. Software Consultant
> > >>
> > >>
> >
> >
> >|||What programs are installed on the computer getting the BSOD? Acrobat Pro,
IM? Others?
"Rockn" <Rockn@.newsgroups.nospam> wrote in message
news:eAXDzH8eHHA.4188@.TK2MSFTNGP02.phx.gbl...
>I am almost positive it is not a printer problem and I can almost bet the
> problem started after a recent Windows Update. I tried my solution on one
> person in the office and it seemed to fix it. I tried it on another
> computer, but I wasn't logged on under his user account and it BSOD'd and
> restarted.
>
> "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
> news:3CEBEA69-C6F9-4B28-BE47-C8CF01A76118@.microsoft.com...
>> I did that and still is rebooting.
>> "Rockn" wrote:
>> > It isn't a printer driver issue, it is the ActiveX control
>> > RSClientPrint
>> > Class that is causing the problem. It seems to be happening after a
> recent
>> > Windows Update, but I have not attributed it to any particular one. Go
> to
>> > C:\windows\downloaded program files and delete the RSClientPrint Class
> and
>> > run your report again. It should prompt you to download the control
> again
>> > and printing should resume after that.
>> >
>> > Wish I could flag this so MS could figure out why it is happening. It
> has
>> > happened to two of my users and I am sure there will be more to follow.
>> >
>> >
>> > "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
>> > news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
>> > > No, It does not happen when you export the report.
>> > >
>> > > But, We have been able to narrow it down to PCL6 print drivers.
>> > >
>> > > "EMartinez" wrote:
>> > >
>> > >> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
>> > >> > We are also having the same problem when printing, blue screen
>> > >> > with
>> > >> > error
>> > >> > message 0X80070709.
>> > >> >
>> > >> > "Eric Wainz" wrote:
>> > >> > > We have been using SQL 2005 reporting services for a while but
>> > >> > > recently when
>> > >> > > some one tries to print a report they will get a BSOD and the
> machine
>> > >> > > reboots.
>> > >> >
>> > >> > > Any Ideas'?
>> > >>
>> > >>
>> > >> It sounds kind of like a printer driver issue. Does this occur when
>> > >> exporting to any SSRS supported format (Excel, PDF, CSV, Web
>> > >> Archive,
>> > >> etc) and then printing?
>> > >>
>> > >> Enrique Martinez
>> > >> Sr. Software Consultant
>> > >>
>> > >>
>> >
>> >
>> >
>|||We are getting the same problem!
Just started happening a few days ago.
"Eric Wainz" wrote:
> We have been using SQL 2005 reporting services for a while but recently when
> some one tries to print a report they will get a BSOD and the machine reboots.
> Any Ideas'?
>|||I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
"Eric Wainz" wrote:
> We have been using SQL 2005 reporting services for a while but recently when
> some one tries to print a report they will get a BSOD and the machine reboots.
> Any Ideas'?
>|||I fixed one of the computers using System Restore to a date before the
errors and it took care of his. I haven't narrowed it down yet, but I have
also tried removing all Windows updates for today and it still didn't fix
another users issue. I'll keep plugging away at it.
"ana9" <ana9@.discussions.microsoft.com> wrote in message
news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
> "Eric Wainz" wrote:
>> We have been using SQL 2005 reporting services for a while but recently
>> when
>> some one tries to print a report they will get a BSOD and the machine
>> reboots.
>> Any Ideas'?|||I rolled back the security updates and re-installed the active x driver to no
avail. All the printers use the PCL6 driver but crashes only occur when
trying to print to an HP4250...
"Rockn" wrote:
> I fixed one of the computers using System Restore to a date before the
> errors and it took care of his. I haven't narrowed it down yet, but I have
> also tried removing all Windows updates for today and it still didn't fix
> another users issue. I'll keep plugging away at it.
> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> > I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
> >
> > "Eric Wainz" wrote:
> >
> >> We have been using SQL 2005 reporting services for a while but recently
> >> when
> >> some one tries to print a report they will get a BSOD and the machine
> >> reboots.
> >>
> >> Any Ideas'?
> >>
>
>|||Is that a PLC 5e driver or something else?
"ana9" <ana9@.discussions.microsoft.com> wrote in message
news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
>I rolled back the security updates and re-installed the active x driver to
>no
> avail. All the printers use the PCL6 driver but crashes only occur when
> trying to print to an HP4250...
>
> "Rockn" wrote:
>> I fixed one of the computers using System Restore to a date before the
>> errors and it took care of his. I haven't narrowed it down yet, but I
>> have
>> also tried removing all Windows updates for today and it still didn't fix
>> another users issue. I'll keep plugging away at it.
>> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
>> > I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
>> >
>> > "Eric Wainz" wrote:
>> >
>> >> We have been using SQL 2005 reporting services for a while but
>> >> recently
>> >> when
>> >> some one tries to print a report they will get a BSOD and the machine
>> >> reboots.
>> >>
>> >> Any Ideas'?
>> >>
>>|||It appears to be a print driver issue due to some recent update. If you
change your print drivers to PCL 5e it won't crash any longer.
ana9 had the answer, but the reason is still not figured out.
"Rockn" <Rockn@.newsgroups.nospam> wrote in message
news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> Is that a PLC 5e driver or something else?
>
> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
>>I rolled back the security updates and re-installed the active x driver to
>>no
>> avail. All the printers use the PCL6 driver but crashes only occur when
>> trying to print to an HP4250...
>>
>> "Rockn" wrote:
>> I fixed one of the computers using System Restore to a date before the
>> errors and it took care of his. I haven't narrowed it down yet, but I
>> have
>> also tried removing all Windows updates for today and it still didn't
>> fix
>> another users issue. I'll keep plugging away at it.
>> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
>> > I'm having the same issue with RS 2000. Microsoft, we need a
>> > hotfix...
>> >
>> > "Eric Wainz" wrote:
>> >
>> >> We have been using SQL 2005 reporting services for a while but
>> >> recently
>> >> when
>> >> some one tries to print a report they will get a BSOD and the machine
>> >> reboots.
>> >>
>> >> Any Ideas'?
>> >>
>>
>|||It doesn't appear to be a general print driver issue. As I said, only the HP
4250's have this problem. Do you see this as well, or does it effect all
your printers regardless of manufacturer?
"Rockn" wrote:
> It appears to be a print driver issue due to some recent update. If you
> change your print drivers to PCL 5e it won't crash any longer.
> ana9 had the answer, but the reason is still not figured out.
> "Rockn" <Rockn@.newsgroups.nospam> wrote in message
> news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> > Is that a PLC 5e driver or something else?
> >
> >
> > "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
> >>I rolled back the security updates and re-installed the active x driver to
> >>no
> >> avail. All the printers use the PCL6 driver but crashes only occur when
> >> trying to print to an HP4250...
> >>
> >>
> >> "Rockn" wrote:
> >>
> >> I fixed one of the computers using System Restore to a date before the
> >> errors and it took care of his. I haven't narrowed it down yet, but I
> >> have
> >> also tried removing all Windows updates for today and it still didn't
> >> fix
> >> another users issue. I'll keep plugging away at it.
> >>
> >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> >> > I'm having the same issue with RS 2000. Microsoft, we need a
> >> > hotfix...
> >> >
> >> > "Eric Wainz" wrote:
> >> >
> >> >> We have been using SQL 2005 reporting services for a while but
> >> >> recently
> >> >> when
> >> >> some one tries to print a report they will get a BSOD and the machine
> >> >> reboots.
> >> >>
> >> >> Any Ideas'?
> >> >>
> >>
> >>
> >>
> >
> >
>
>|||It only affects printers using the PCL 6 driver. If I print to any of the
others using a PCL 5e driver it works. All of our printers are HP.
"ana9" <ana9@.discussions.microsoft.com> wrote in message
news:7FEEEDFD-FBC1-45D8-915D-087F066D3108@.microsoft.com...
> It doesn't appear to be a general print driver issue. As I said, only the
HP
> 4250's have this problem. Do you see this as well, or does it effect all
> your printers regardless of manufacturer?
> "Rockn" wrote:
> > It appears to be a print driver issue due to some recent update. If you
> > change your print drivers to PCL 5e it won't crash any longer.
> > ana9 had the answer, but the reason is still not figured out.
> >
> > "Rockn" <Rockn@.newsgroups.nospam> wrote in message
> > news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> > > Is that a PLC 5e driver or something else?
> > >
> > >
> > > "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
> > >>I rolled back the security updates and re-installed the active x
driver to
> > >>no
> > >> avail. All the printers use the PCL6 driver but crashes only occur
when
> > >> trying to print to an HP4250...
> > >>
> > >>
> > >> "Rockn" wrote:
> > >>
> > >> I fixed one of the computers using System Restore to a date before
the
> > >> errors and it took care of his. I haven't narrowed it down yet, but
I
> > >> have
> > >> also tried removing all Windows updates for today and it still
didn't
> > >> fix
> > >> another users issue. I'll keep plugging away at it.
> > >>
> > >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> > >> > I'm having the same issue with RS 2000. Microsoft, we need a
> > >> > hotfix...
> > >> >
> > >> > "Eric Wainz" wrote:
> > >> >
> > >> >> We have been using SQL 2005 reporting services for a while but
> > >> >> recently
> > >> >> when
> > >> >> some one tries to print a report they will get a BSOD and the
machine
> > >> >> reboots.
> > >> >>
> > >> >> Any Ideas'?
> > >> >>
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> >|||Remove security patch KB925902 or MS07-017 related to GDI+. This was just
realeased. I understand a hot patch may be available as early as Monday.
As a pre-caution read why this security update was published before
removing. Might be more of a risk to remove that to have the end users export
to pdf then print which has been my work around.
John
"Rockn" wrote:
> It only affects printers using the PCL 6 driver. If I print to any of the
> others using a PCL 5e driver it works. All of our printers are HP.
> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> news:7FEEEDFD-FBC1-45D8-915D-087F066D3108@.microsoft.com...
> > It doesn't appear to be a general print driver issue. As I said, only the
> HP
> > 4250's have this problem. Do you see this as well, or does it effect all
> > your printers regardless of manufacturer?
> >
> > "Rockn" wrote:
> >
> > > It appears to be a print driver issue due to some recent update. If you
> > > change your print drivers to PCL 5e it won't crash any longer.
> > > ana9 had the answer, but the reason is still not figured out.
> > >
> > > "Rockn" <Rockn@.newsgroups.nospam> wrote in message
> > > news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> > > > Is that a PLC 5e driver or something else?
> > > >
> > > >
> > > > "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > > > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
> > > >>I rolled back the security updates and re-installed the active x
> driver to
> > > >>no
> > > >> avail. All the printers use the PCL6 driver but crashes only occur
> when
> > > >> trying to print to an HP4250...
> > > >>
> > > >>
> > > >> "Rockn" wrote:
> > > >>
> > > >> I fixed one of the computers using System Restore to a date before
> the
> > > >> errors and it took care of his. I haven't narrowed it down yet, but
> I
> > > >> have
> > > >> also tried removing all Windows updates for today and it still
> didn't
> > > >> fix
> > > >> another users issue. I'll keep plugging away at it.
> > > >>
> > > >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > > >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> > > >> > I'm having the same issue with RS 2000. Microsoft, we need a
> > > >> > hotfix...
> > > >> >
> > > >> > "Eric Wainz" wrote:
> > > >> >
> > > >> >> We have been using SQL 2005 reporting services for a while but
> > > >> >> recently
> > > >> >> when
> > > >> >> some one tries to print a report they will get a BSOD and the
> machine
> > > >> >> reboots.
> > > >> >>
> > > >> >> Any Ideas'?
> > > >> >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> > >
>
>|||That did the trick, you are the man!!
"John" <John@.discussions.microsoft.com> wrote in message
news:3B16020C-2B19-40F9-BF4D-811DC1995D95@.microsoft.com...
> Remove security patch KB925902 or MS07-017 related to GDI+. This was just
> realeased. I understand a hot patch may be available as early as Monday.
> As a pre-caution read why this security update was published before
> removing. Might be more of a risk to remove that to have the end users
> export
> to pdf then print which has been my work around.
> John
> "Rockn" wrote:
>> It only affects printers using the PCL 6 driver. If I print to any of the
>> others using a PCL 5e driver it works. All of our printers are HP.
>> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> news:7FEEEDFD-FBC1-45D8-915D-087F066D3108@.microsoft.com...
>> > It doesn't appear to be a general print driver issue. As I said, only
>> > the
>> HP
>> > 4250's have this problem. Do you see this as well, or does it effect
>> > all
>> > your printers regardless of manufacturer?
>> >
>> > "Rockn" wrote:
>> >
>> > > It appears to be a print driver issue due to some recent update. If
>> > > you
>> > > change your print drivers to PCL 5e it won't crash any longer.
>> > > ana9 had the answer, but the reason is still not figured out.
>> > >
>> > > "Rockn" <Rockn@.newsgroups.nospam> wrote in message
>> > > news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
>> > > > Is that a PLC 5e driver or something else?
>> > > >
>> > > >
>> > > > "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> > > > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
>> > > >>I rolled back the security updates and re-installed the active x
>> driver to
>> > > >>no
>> > > >> avail. All the printers use the PCL6 driver but crashes only
>> > > >> occur
>> when
>> > > >> trying to print to an HP4250...
>> > > >>
>> > > >>
>> > > >> "Rockn" wrote:
>> > > >>
>> > > >> I fixed one of the computers using System Restore to a date
>> > > >> before
>> the
>> > > >> errors and it took care of his. I haven't narrowed it down yet,
>> > > >> but
>> I
>> > > >> have
>> > > >> also tried removing all Windows updates for today and it still
>> didn't
>> > > >> fix
>> > > >> another users issue. I'll keep plugging away at it.
>> > > >>
>> > > >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> > > >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
>> > > >> > I'm having the same issue with RS 2000. Microsoft, we need a
>> > > >> > hotfix...
>> > > >> >
>> > > >> > "Eric Wainz" wrote:
>> > > >> >
>> > > >> >> We have been using SQL 2005 reporting services for a while but
>> > > >> >> recently
>> > > >> >> when
>> > > >> >> some one tries to print a report they will get a BSOD and the
>> machine
>> > > >> >> reboots.
>> > > >> >>
>> > > >> >> Any Ideas'?
>> > > >> >>
>> > > >>
>> > > >>
>> > > >>
>> > > >
>> > > >
>> > >
>> > >
>> > >
>>|||Please review this article http://support.microsoft.com/kb/935843/. It has two patches, one for Windows 2000 and another one for Windows XP. The crashing will stop after you apply this patch
From http://www.developmentnow.com/g/115_2007_4_0_0_955642/Blue-Screen-of-Death-BSOD-when-printing.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Blank pages when printing

Hi - I am generating a table with large amounts of data. When I generate the
report, the report looks fine but when I print preview it, every alternating
page is blank with only the header and footer being displayed on every page.
I have tried playing around with the page breaks with no luck. Is there a
way, maybe programmaticaly to set page breaks and stop my report from having
blank page between data page? Or what might be causing the alternate blank
pages with header/footer?
thanksHello ISGADMIN,
I had a real time myself at first with plank pages as I am sure a lot of
designers did, but all you need to do is make sure the design grid, margin
settings and data regions fall within boundaries when designing. If you have
a one inch margins on the R and L in Landscape settings (11 X 8.5 in the
Report Properties) for example, the design area and all objects on it need
to fall under 10 inches on the ruler. You may have to tweak with the
measurement for the actual grid to get it just right, but it will work.
--
Rodney Landrum - Author, "Pro SQL Server Reporting Services" (Apress)
http://www.apress.com
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:C1D58BC4-D257-4052-AAB6-10BE7BEE21E2@.microsoft.com...
> Hi - I am generating a table with large amounts of data. When I generate
> the
> report, the report looks fine but when I print preview it, every
> alternating
> page is blank with only the header and footer being displayed on every
> page.
> I have tried playing around with the page breaks with no luck. Is there a
> way, maybe programmaticaly to set page breaks and stop my report from
> having
> blank page between data page? Or what might be causing the alternate
> blank
> pages with header/footer?
> thanks|||Have you considered re-creating the report? Or copy & paste the RDL File,
and start deleting objects from it. Perhaps one of the objects is taking a
full new page.
"ItSGADMIN" wrote:
> Hi - I am generating a table with large amounts of data. When I generate the
> report, the report looks fine but when I print preview it, every alternating
> page is blank with only the header and footer being displayed on every page.
> I have tried playing around with the page breaks with no luck. Is there a
> way, maybe programmaticaly to set page breaks and stop my report from having
> blank page between data page? Or what might be causing the alternate blank
> pages with header/footer?
> thanks|||Hi isgadmin,
I wanted to post a quick note to see if you would like additional
assistance or information regarding this particular issue. We appreciate
your patience and look forward to hearing from you!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Blank pages in print preview for sub reports

Hi,

I have serveral subreports in main report. I have no problem print the orignal report but when I print them as subreport so get extra blank pages. I try to set the width of sub report in main report the max width value (19.6 cm width) without succeed. Any help would be appreiciate!

Hi,The extra blank page is coming for the Page Layout that you set for your report.Decrease the Left Margin and right margin percentage and try to move your Textbox fields bit closer to each other from right side and remove the extra space left on the right side of your report just draging it towards left.Hope this will solve your problem.|||Hi,In Sql report the preview take extra space for the extra width that you give to your report.So remove the extra width from your report.Do not increase the default width of the report by draging it towards right.Hope this will solve your problem.

Regards
Gelu

Blank pages in Print Layout version of report

Hi All

I have a report that looks and works fine in the native 'screen layout' but when I select the Print Layout option, a blank page is inserted after each page. These blank pages contain the header and footer, but not the body section of the report. Has anyone else seen this sort of thing? Is there something in my report layout causing this, or is it a bug in the Print Layout rendering?

Thanks much

On your report layout, is the white background width, plus the size of your right and left margins (in Report, Properties) greater than your page width in report, properties?

This will cause page breaks.

BobP

|||

I have the same or similiar question.

When I preview my report in Report Services I have no blank pages. When I print preview it there is one or two pages that are blank. Well they are half blank or partial blank.

My report has a header and body. I have the labels of the body in the header because I can't get the repeatwith Property to work(That's being addressed in another thread.). In the Body I have a list box and sub list box. I have it grouped by a field contained in the list box. Some the pages end where the grouping ends, but not all. It's strange. If I edit the size of the list box or somehow or decrease the size of the report the blank pages changes. Such as now it's half blank on page 4 and 3/4 blank on page 30. out of 50. I change the list box a little and it changes my blank pages to be on 15 and 22.

Anyone got a sufggestion for this?

Card Gunner

Blank Pages

When I print my report in SSRS it says there are 5 pages, when I print my
report to the printer, 22 pages comes out, every other page is blank. It
does the same when I print it to PDF.
I went to Report Properties>>Layout and have my settings as 10in Width, 8in
Height and margins are set to zero.
What is wrong here?
Thanks,
RyanOn Jun 14, 2:24 pm, Ryan Mcbee <RyanMc...@.discussions.microsoft.com>
wrote:
> When I print my report in SSRS it says there are 5 pages, when I print my
> report to the printer, 22 pages comes out, every other page is blank. It
> does the same when I print it to PDF.
> I went to Report Properties>>Layout and have my settings as 10in Width, 8in
> Height and margins are set to zero.
> What is wrong here?
> Thanks,
> Ryan
You want to make sure that you are not page breaking after groups,
etc. Also, I find that when exporting to PDF, a lot of times the extra
pages can be avoided by putting multiple table/matrix controls inside
a single rectangle control (where applicable). Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

blank pages

When I print my report, every other page is blank. I have resized everything
down to half the page, played with margins and object sizes to see if I just
had an oversized item, but to no avail. Is there a setting or somthing that
does this?
I am at my wits end!
thanks!Check the width of your report's Body - right-click on the body bar and
select properties - Size>width. This should be less than or equal to
Page width - (Left margin + Right margin) <- all in Report Properties
Layout tab
HTH,
Magendo_man
"Carl Henthorn" wrote:
> When I print my report, every other page is blank. I have resized everything
> down to half the page, played with margins and object sizes to see if I just
> had an oversized item, but to no avail. Is there a setting or somthing that
> does this?
> I am at my wits end!
> thanks!

Blank page at the end when printing

I am using RS2000 SP2, and I have created a simple report. Everything looks
fine on the screen, but when I print it, it always prints out a blank page at
the end. For example, on the screen the report has 10 pages. When I print the
report, it has 11 pages (with the last page only containing the header). Any
suggestion on how to resolve this? Thank You!
KCKC wrote:
> I am using RS2000 SP2, and I have created a simple report. Everything looks
> fine on the screen, but when I print it, it always prints out a blank page at
> the end. For example, on the screen the report has 10 pages. When I print the
> report, it has 11 pages (with the last page only containing the header). Any
> suggestion on how to resolve this? Thank You!
> KC
Hey,
I know how annoying this is.
What you need to do is to ensure that the actual report is not longer
than your page (21cm by 29.7cm). The way around it I found is to click
on the table so that it shows handles and then squeeze it so that it's
no bigger than specified page, then also you need to adjust the page
itself... Unfortunately this is bit of a trial and error game!
Good luck
AJ|||KC wrote:
> I am using RS2000 SP2, and I have created a simple report. Everything looks
> fine on the screen, but when I print it, it always prints out a blank page at
> the end. For example, on the screen the report has 10 pages. When I print the
> report, it has 11 pages (with the last page only containing the header). Any
> suggestion on how to resolve this? Thank You!
> KC
Hey,
I know how annoying this is.
What you need to do is to ensure that the actual report is not longer
than your page (21cm by 29.7cm). The way around it I found is to click
on the table so that it shows handles and then squeeze it so that it's
no bigger than specified page, then also you need to adjust the page
itself... Unfortunately this is bit of a trial and error game!
Good luck
AJ

Black Reports in Print Layout

Hello all,
We have an issue with reports we created using the VS 2005 Team System. When
we open a report everything looks fine and report prints fine as well.
The problem is that when we click the Print Layout button on the report we
get a black page and only report title and group headers are visible. Mind
you, the report still prints fine on the printer but none of the data is
visible in the report.
Any ideas and solutions appreciated.
BR,
GAZOn Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> Hello all,
> We have an issue with reports we created using the VS 2005 Team System. When
> we open a report everything looks fine and report prints fine as well.
> The problem is that when we click the Print Layout button on the report we
> get a black page and only report title and group headers are visible. Mind
> you, the report still prints fine on the printer but none of the data is
> visible in the report.
> Any ideas and solutions appreciated.
> BR,
> GAZ
This should help.
http://support.microsoft.com/kb/935356/en-us
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
> On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
>> Hello all,
>> We have an issue with reports we created using the VS 2005 Team System.
>> When
>> we open a report everything looks fine and report prints fine as well.
>> The problem is that when we click the Print Layout button on the report
>> we
>> get a black page and only report title and group headers are visible.
>> Mind
>> you, the report still prints fine on the printer but none of the data is
>> visible in the report.
>> Any ideas and solutions appreciated.
>> BR,
>> GAZ
>
> This should help.
> http://support.microsoft.com/kb/935356/en-us
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Thanks for the info. Got it but it won't install. Every single hotfix
reports a failure to install. Has anyone else had any problems with the
installation of the said hotfix?
BR,
GAZ|||On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
>
> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> >> Hello all,
> >> We have an issue with reports we created using the VS 2005 Team System.
> >> When
> >> we open a report everything looks fine and report prints fine as well.
> >> The problem is that when we click the Print Layout button on the report
> >> we
> >> get a black page and only report title and group headers are visible.
> >> Mind
> >> you, the report still prints fine on the printer but none of the data is
> >> visible in the report.
> >> Any ideas and solutions appreciated.
> >> BR,
> >> GAZ
> > This should help.
> >http://support.microsoft.com/kb/935356/en-us
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks for the info. Got it but it won't install. Every single hotfix
> reports a failure to install. Has anyone else had any problems with the
> installation of the said hotfix?
> BR,
> GAZ
You're welcome. You may have to install the Hot fixes in a particular
order. Have you tried verifying the order in which the hot fixes must
be installed? Hope this helps further.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
> On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
>> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
>>
>> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
>> >> Hello all,
>> >> We have an issue with reports we created using the VS 2005 Team
>> >> System.
>> >> When
>> >> we open a report everything looks fine and report prints fine as well.
>> >> The problem is that when we click the Print Layout button on the
>> >> report
>> >> we
>> >> get a black page and only report title and group headers are visible.
>> >> Mind
>> >> you, the report still prints fine on the printer but none of the data
>> >> is
>> >> visible in the report.
>> >> Any ideas and solutions appreciated.
>> >> BR,
>> >> GAZ
>> > This should help.
>> >http://support.microsoft.com/kb/935356/en-us
>> > Regards,
>> > Enrique Martinez
>> > Sr. Software Consultant
>> Thanks for the info. Got it but it won't install. Every single hotfix
>> reports a failure to install. Has anyone else had any problems with the
>> installation of the said hotfix?
>> BR,
>> GAZ
>
> You're welcome. You may have to install the Hot fixes in a particular
> order. Have you tried verifying the order in which the hot fixes must
> be installed? Hope this helps further.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Thanks for your answer.
The hotfixes are acutally rolled into one package which does not give you an
option to choose a particular order for installation. When we start the
installation it always asks for the SQL installation disk and then it reads
files from it and reports that the hotfix installation failed. And so on for
each of the components.
Well, I guess that we'll have to wait for the SP3 to have the issue
resolved.
Thanks again for your help.
BR,
GAZ|||On Dec 26, 1:58 am, "GAZ" <g...@.gaz.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
>
> > On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >>news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
> >> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> >> >> Hello all,
> >> >> We have an issue with reports we created using the VS 2005 Team
> >> >> System.
> >> >> When
> >> >> we open a report everything looks fine and report prints fine as well.
> >> >> The problem is that when we click the Print Layout button on the
> >> >> report
> >> >> we
> >> >> get a black page and only report title and group headers are visible.
> >> >> Mind
> >> >> you, the report still prints fine on the printer but none of the data
> >> >> is
> >> >> visible in the report.
> >> >> Any ideas and solutions appreciated.
> >> >> BR,
> >> >> GAZ
> >> > This should help.
> >> >http://support.microsoft.com/kb/935356/en-us
> >> > Regards,
> >> > Enrique Martinez
> >> > Sr. Software Consultant
> >> Thanks for the info. Got it but it won't install. Every single hotfix
> >> reports a failure to install. Has anyone else had any problems with the
> >> installation of the said hotfix?
> >> BR,
> >> GAZ
> > You're welcome. You may have to install the Hot fixes in a particular
> > order. Have you tried verifying the order in which the hot fixes must
> > be installed? Hope this helps further.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks for your answer.
> The hotfixes are acutally rolled into one package which does not give you an
> option to choose a particular order for installation. When we start the
> installation it always asks for the SQL installation disk and then it reads
> files from it and reports that the hotfix installation failed. And so on for
> each of the components.
> Well, I guess that we'll have to wait for the SP3 to have the issue
> resolved.
> Thanks again for your help.
> BR,
> GAZ
You're welcome. Have you checked the Event Viewer for errors that
might be logged during the process? That might provide some better
details. Hope this helps further.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:7c2d5ac2-a280-4fe0-9a51-a53e315ea7dd@.1g2000hsl.googlegroups.com...
> On Dec 26, 1:58 am, "GAZ" <g...@.gaz.com> wrote:
>> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
>>
>> > On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
>> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> >>news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
>> >> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
>> >> >> Hello all,
>> >> >> We have an issue with reports we created using the VS 2005 Team
>> >> >> System.
>> >> >> When
>> >> >> we open a report everything looks fine and report prints fine as
>> >> >> well.
>> >> >> The problem is that when we click the Print Layout button on the
>> >> >> report
>> >> >> we
>> >> >> get a black page and only report title and group headers are
>> >> >> visible.
>> >> >> Mind
>> >> >> you, the report still prints fine on the printer but none of the
>> >> >> data
>> >> >> is
>> >> >> visible in the report.
>> >> >> Any ideas and solutions appreciated.
>> >> >> BR,
>> >> >> GAZ
>> >> > This should help.
>> >> >http://support.microsoft.com/kb/935356/en-us
>> >> > Regards,
>> >> > Enrique Martinez
>> >> > Sr. Software Consultant
>> >> Thanks for the info. Got it but it won't install. Every single hotfix
>> >> reports a failure to install. Has anyone else had any problems with
>> >> the
>> >> installation of the said hotfix?
>> >> BR,
>> >> GAZ
>> > You're welcome. You may have to install the Hot fixes in a particular
>> > order. Have you tried verifying the order in which the hot fixes must
>> > be installed? Hope this helps further.
>> > Regards,
>> > Enrique Martinez
>> > Sr. Software Consultant
>> Thanks for your answer.
>> The hotfixes are acutally rolled into one package which does not give you
>> an
>> option to choose a particular order for installation. When we start the
>> installation it always asks for the SQL installation disk and then it
>> reads
>> files from it and reports that the hotfix installation failed. And so on
>> for
>> each of the components.
>> Well, I guess that we'll have to wait for the SP3 to have the issue
>> resolved.
>> Thanks again for your help.
>> BR,
>> GAZ
>
> You're welcome. Have you checked the Event Viewer for errors that
> might be logged during the process? That might provide some better
> details. Hope this helps further.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Thanks for your help. Unfortunatelly the Event Log is of no help as it does
not provide any useful information. The logs created by the installation
process say that the hotfix package could not be found but i have no idea
what to do with that information as the package physically exists on the
hard drive where the setup process extracted it.
Well, I can only wait for the next SP i guess.
BR,
GAZ|||On Dec 27, 12:06 pm, "GAZ" <g...@.gaz.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:7c2d5ac2-a280-4fe0-9a51-a53e315ea7dd@.1g2000hsl.googlegroups.com...
>
> > On Dec 26, 1:58 am, "GAZ" <g...@.gaz.com> wrote:
> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >>news:3d431f4b-bd40-49c7-bb5f-c0f2b2c4b64e@.21g2000hsj.googlegroups.com...
> >> > On Dec 25, 3:41 am, "GAZ" <g...@.gaz.com> wrote:
> >> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >> >>news:d2fc2115-efce-4d3e-9ee2-4965bd60ec77@.f52g2000hsa.googlegroups.com...
> >> >> > On Dec 24, 8:33 am, "GAZ" <g...@.gaz.com> wrote:
> >> >> >> Hello all,
> >> >> >> We have an issue with reports we created using the VS 2005 Team
> >> >> >> System.
> >> >> >> When
> >> >> >> we open a report everything looks fine and report prints fine as
> >> >> >> well.
> >> >> >> The problem is that when we click the Print Layout button on the
> >> >> >> report
> >> >> >> we
> >> >> >> get a black page and only report title and group headers are
> >> >> >> visible.
> >> >> >> Mind
> >> >> >> you, the report still prints fine on the printer but none of the
> >> >> >> data
> >> >> >> is
> >> >> >> visible in the report.
> >> >> >> Any ideas and solutions appreciated.
> >> >> >> BR,
> >> >> >> GAZ
> >> >> > This should help.
> >> >> >http://support.microsoft.com/kb/935356/en-us
> >> >> > Regards,
> >> >> > Enrique Martinez
> >> >> > Sr. Software Consultant
> >> >> Thanks for the info. Got it but it won't install. Every single hotfix
> >> >> reports a failure to install. Has anyone else had any problems with
> >> >> the
> >> >> installation of the said hotfix?
> >> >> BR,
> >> >> GAZ
> >> > You're welcome. You may have to install the Hot fixes in a particular
> >> > order. Have you tried verifying the order in which the hot fixes must
> >> > be installed? Hope this helps further.
> >> > Regards,
> >> > Enrique Martinez
> >> > Sr. Software Consultant
> >> Thanks for your answer.
> >> The hotfixes are acutally rolled into one package which does not give you
> >> an
> >> option to choose a particular order for installation. When we start the
> >> installation it always asks for the SQL installation disk and then it
> >> reads
> >> files from it and reports that the hotfix installation failed. And so on
> >> for
> >> each of the components.
> >> Well, I guess that we'll have to wait for the SP3 to have the issue
> >> resolved.
> >> Thanks again for your help.
> >> BR,
> >> GAZ
> > You're welcome. Have you checked the Event Viewer for errors that
> > might be logged during the process? That might provide some better
> > details. Hope this helps further.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks for your help. Unfortunatelly the Event Log is of no help as it does
> not provide any useful information. The logs created by the installation
> process say that the hotfix package could not be found but i have no idea
> what to do with that information as the package physically exists on the
> hard drive where the setup process extracted it.
> Well, I can only wait for the next SP i guess.
> BR,
> GAZ
You're welcome. Do you have SQL Server and/or Reporting Services
installed in a non-standard location (i.e., on a D or E partition)? If
that is the case, this could be the problem.
Regards,
Enrique Martinez
Sr. Software Consultant

Bizarre zero suppression on print

Hi All,

I have a report (using CR XI) that uses conditional suppression.

Simple stuff, it prints out a few data values if at least one of the values is not null but prints a row of text (made up of the appropriate number of .00s in the right places) if all data values for the line are null.

In print preview on the screen it works perfectly but when I print it out, all the zeroes disappear and all that is left is the dot!

In case anyone is wondering why I doing it this way at all and not simply unselecting the suppress when zero checkbox it is because this report is a subreport of another report and if all the data values are null in the sub then the main just has a blank patch (rather than zeroes).

Anyway, any ideas re how to get the printer to print out what the preview says it will?

Thanks,

HywelCHello again,

I tried to export the report as a PDF and that works perfectly too. The problem just seems to be with the printer...very odd.

HywelC|||Did you set the page setup correctly?