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

Blue Screen

Hello, I'm trying to restore a large database (350gb) to a sql server over the network. However after running for about 10 hours or so the target sql server crushes with a blue screen. Has anybody encountered similar problem or do you have an idea as to why this may happen. Thanks a lot for any help.Hello Wolv,

What sort of network are you running? If you are working on a gigabyte LAN/SAN, then you should have no problem depending on whether your SQL server hardware is up to scratch.

You are trying to move a big DB, therefore if you don't have the hardware to support that move then you may want to consider an alternative for moving the data.

Hope this helps, at least in understanding why...|||well, what kind of network would be helpful, but If you are restoring it, I would think that you've had it in the same place before, just something happened, and that's why you are restoring it...correct?

Blank Parameters

I am trying to use a stored procedure that can accept blank parameters to
return a complete set of data. when I use the preview screen in reporting
services, the sproc does not return anything, yet when i run the sproc from
anywhere else, it works. Is there a setting I am missing to be able pass
balnk values to a sproc from the report?
Yes, if i pass values to the report, not blanks, the sproc does run and
returns data.
--
John Cleveland
Network Manager
Urban systems LtdTry using SQL Profiler to find out what is actually sent to the stored
procedure. Blank might not be blank. Do you expect a NULL or a '' as a blank
in the sp? Anyway, SQL Profiler shows what is actually sent, so you can
modify either Parameter or Stored Procedure accordingly.
Kaisa M. Lindahl Lervik
"John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
news:EA34E0D4-7E12-4730-96F5-B783261CADF4@.microsoft.com...
>I am trying to use a stored procedure that can accept blank parameters to
> return a complete set of data. when I use the preview screen in reporting
> services, the sproc does not return anything, yet when i run the sproc
> from
> anywhere else, it works. Is there a setting I am missing to be able pass
> balnk values to a sproc from the report?
> Yes, if i pass values to the report, not blanks, the sproc does run and
> returns data.
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||When you click on preview, is it giving a small entry screen ? if yes dont
enter anything like double quotes etc.. before that is it giving a screen?
Amarnath
"John Cleveland" wrote:
> I am trying to use a stored procedure that can accept blank parameters to
> return a complete set of data. when I use the preview screen in reporting
> services, the sproc does not return anything, yet when i run the sproc from
> anywhere else, it works. Is there a setting I am missing to be able pass
> balnk values to a sproc from the report?
> Yes, if i pass values to the report, not blanks, the sproc does run and
> returns data.
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||I ran a trace in profiler and here is what I got:
exec spCostReport @.Project=N'', @.Phase=N''
These are the 2 params i am trying to send. I have default values set in
the sproc that should kick in if the params are blank. I exported the trace
to make sure there was nothing between the '', and there wasn't. Any thing
else to check for?
When I run this from the dataset screen in reporting services, it runs fine
leaving the params blank. it only seems to be when the report is run.
--
John Cleveland
Network Manager
Urban systems Ltd
"Kaisa M. Lindahl Lervik" wrote:
> Try using SQL Profiler to find out what is actually sent to the stored
> procedure. Blank might not be blank. Do you expect a NULL or a '' as a blank
> in the sp? Anyway, SQL Profiler shows what is actually sent, so you can
> modify either Parameter or Stored Procedure accordingly.
> Kaisa M. Lindahl Lervik
> "John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
> news:EA34E0D4-7E12-4730-96F5-B783261CADF4@.microsoft.com...
> >I am trying to use a stored procedure that can accept blank parameters to
> > return a complete set of data. when I use the preview screen in reporting
> > services, the sproc does not return anything, yet when i run the sproc
> > from
> > anywhere else, it works. Is there a setting I am missing to be able pass
> > balnk values to a sproc from the report?
> >
> > Yes, if i pass values to the report, not blanks, the sproc does run and
> > returns data.
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
> >
>
>

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

Blank page after specifying new parameter criteria.

I'm seeing an issue where, after changing the criteria in two date parameters
and clicking the "View Report" button, the screen is blanked out. If I click
the button again, the criteria is used, and the report is displayed.
Anyone else seeing this?
Is there any solution this?I've been having simular problems, although only on the preview pane, on the
report server it works fine
"Aaron" wrote:
> I'm seeing an issue where, after changing the criteria in two date parameters
> and clicking the "View Report" button, the screen is blanked out. If I click
> the button again, the criteria is used, and the report is displayed.
> Anyone else seeing this?
> Is there any solution this?|||I did notice that if I take out the default values I specified in my
parameters, it doesn't do this anymore. Weird...
Must be a bug.
"Antoon" wrote:
> I've been having simular problems, although only on the preview pane, on the
> report server it works fine
> "Aaron" wrote:
> > I'm seeing an issue where, after changing the criteria in two date parameters
> > and clicking the "View Report" button, the screen is blanked out. If I click
> > the button again, the criteria is used, and the report is displayed.
> >
> > Anyone else seeing this?
> >
> > Is there any solution this?

Blank IE screen

Hi everybody,
I have a problem with our new setup of RS 2005.
I can access de report manager an show reports fine.
I have the Bruce-workaround t.i. a "dummy"-report that refreshes itself
every few minutes to keep connections alive.
Still somtimes when I open up a report I get a blank IE window and have to
wait a full minute for "report is being generated" to appear. Although I ran
a report e few minutes earlier (certainly les than 20 minutes AND my dummy
report is running).
I ran a trace, but I can't really see the problem, could anybody please help.
I added the trace here below starting from the point I reqeusted the report
to the time that the "report is being generated" appeared. I can't add the
complete trace here (to long) I will put the rest in a next post.
Trace Start 2007-05-17 14:06:46.403
ExistingConnection -- network protocol: LPC
set quoted_identifier off
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
SQLAgent - Generic Refresher adminsql KLINA\adminsql 3232 51 2007-05-04
12:47:40.653
ExistingConnection -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 52 2007-05-17 12:54:29.373
ExistingConnection -- network protocol: TCP/IP
set quoted_identifier on
set arithabort on
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Toad for SQL Server sa 1364 55 2007-05-17 11:31:23.827
ExistingConnection -- network protocol: TCP/IP
set quoted_identifier off
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
SQLDMO_1 sa 1364 56 2007-05-17 11:31:25.890
ExistingConnection -- network protocol: LPC
set quoted_identifier off
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
SQLAgent - Job invocation
engine adminsql KLINA\adminsql 3232 58 2007-05-05 00:10:00.810
ExistingConnection -- network protocol: TCP/IP
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Microsoft® Visual Studio®
2005 vansinan KLINA\vansinan 1920 62 2007-05-10 20:23:44.327
ExistingConnection -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:04:29.090
ExistingConnection -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:42.717
Audit Logout Report
Server adminsql KLINA\adminsql 0 45 0 10000 2056 103 2007-05-17
14:06:42.717 2007-05-17 14:06:52.717
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:06:52.717 2007-05-17
14:06:52.717 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:52.717
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:52.717
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:06:52.717 2007-05-17 14:06:52.717
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:06:52.717
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:06:52.717 2007-05-17 14:06:52.717
Audit Logout Report
Server adminsql KLINA\adminsql 0 45 0 10250 2056 103 2007-05-17
14:06:52.717 2007-05-17 14:07:02.967
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:02.967 2007-05-17
14:07:02.967 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:02.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:02.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] = t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:02.967 2007-05-17 14:07:02.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:02.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] = t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:02.967 2007-05-17 14:07:02.967Here's the rest of it:
Audit Logout Report
Server adminsql KLINA\adminsql 0 45 0 10000 2056 103 2007-05-17
14:07:02.967 2007-05-17 14:07:12.967
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:12.967 2007-05-17
14:07:12.967 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:12.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:12.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:12.967 2007-05-17 14:07:12.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 103 2007-05-17 14:07:12.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 103 2007-05-17
14:07:12.967 2007-05-17 14:07:12.967
Audit Logout Report
Server adminsql KLINA\adminsql 0 9082 39 173876 2056 65 2007-05-17
14:04:29.090 2007-05-17 14:07:22.967
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:22.967 2007-05-17
14:07:22.967 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:22.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:22.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = NEWID()
UPDATE [Event] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] =GETUTCDATE()
FROM (
SELECT TOP 2 [EventID] FROM
[Event] WITH (TABLOCKX) WHERE [ProcessStart] is NULL ORDER BY [TimeEntered]
) AS t1
WHERE [Event].[EventID] =t1.[EventID]
select top 2
E.[EventID],
E.[EventType],
E.[EventData]
from
[Event] E WITH (TABLOCKX)
where
[BatchID] = @.BatchID
ORDER BY [TimeEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:22.967 2007-05-17 14:07:22.967
SQL:BatchStarting
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:22.967
SQL:BatchCompleted
declare @.BatchID uniqueidentifier
set @.BatchID = newid()
UPDATE [Notifications] WITH (TABLOCKX)
SET [BatchID] = @.BatchID,
[ProcessStart] = GETUTCDATE(),
[ProcessHeartbeat] = GETUTCDATE()
FROM (
SELECT TOP 2 [NotificationID] FROM
[Notifications] WITH (TABLOCKX) WHERE ProcessStart is NULL and
(ProcessAfter is NULL or ProcessAfter <
GETUTCDATE()) ORDER BY [NotificationEntered]
) AS t1
WHERE [Notifications].[NotificationID] =t1.[NotificationID]
select top 2
-- Notification data
N.[NotificationID],
N.[SubscriptionID],
N.[ActivationID],
N.[ReportID],
N.[SnapShotDate],
N.[DeliveryExtension],
N.[ExtensionSettings],
N.[Locale],
N.[Parameters],
N.[SubscriptionLastRunTime],
N.[ProcessStart],
N.[NotificationEntered],
N.[Attempt],
N.[IsDataDriven],
SUSER_SNAME(Owner.[Sid]),
Owner.[UserName],
-- Report Data
O.[Path],
O.[Type],
SD.NtSecDescPrimary,
N.[Version],
Owner.[AuthType]
from
[Notifications] N with (TABLOCKX)
inner join [Catalog] O on O.[ItemID] = N.[ReportID]
inner join [Users] Owner on
N.SubscriptionOwnerID = Owner.UserID
left outer join [SecData] SD on
O.[PolicyID] = SD.[PolicyID] AND SD.AuthType = Owner.AuthType
where
N.[BatchID] = @.BatchID
ORDER BY [NotificationEntered]
Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:22.967 2007-05-17 14:07:22.967
Audit Logout Report
Server adminsql KLINA\adminsql 0 9082 39 4970 2056 65 2007-05-17
14:07:22.967 2007-05-17 14:07:27.937
RPC:Completed exec sp_reset_connection Report
Server adminsql KLINA\adminsql 0 0 0 0 2056 65 2007-05-17
14:07:27.937 2007-05-17
14:07:27.937 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server adminsql KLINA\adminsql 2056 65 2007-05-17 14:07:27.937
RPC:Completed exec GetMyRunningJobs
@.ComputerName=N'REPORTSRV',@.JobType=1 Report
Server adminsql KLINA\adminsql 0 2 0 0 2056 65 2007-05-17
14:07:27.937 2007-05-17
14:07:27.937 0X000000000300000020004700650074004D007900520075006E006E0069006E0067004A006F00620073005200000082001600E7306E0076006100720063006800610072002800390029001A00400043006F006D00700075007400650072004E0061006D006500120000005200450050004F00520054005300520056002E00000002001000341073006D0061006C006C0069006E007400100040004A006F006200540079007000650001001400000003000600380469006E00740000000000
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 5324 53 2007-05-17 14:07:28.140
RPC:Completed exec GetOneConfigurationInfo
@.Name=N'SharePointIntegrated' Report Server NETWORK SERVICE NT
AUTHORITY\NETWORK SERVICE 0 2 0 0 5324 53 2007-05-17 14:07:28.140 2007-05-17
14:07:28.140 0X00000000020000002E004700650074004F006E00650043006F006E00660069006700750072006100740069006F006E0049006E0066006F005A00000082001800E7306E00760061007200630068006100720028003200300029000A0040004E0061006D006500280000005300680061007200650050006F0069006E00740049006E00740065006700720061007400650064001400000003000600380469006E00740000000000
Audit Logout Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 0 2 0 76 5324 53 2007-05-17 14:07:28.140 2007-05-17 14:07:28.217
RPC:Completed exec sp_reset_connection Report Server NETWORK SERVICE NT
AUTHORITY\NETWORK SERVICE 0 0 0 0 5324 53 2007-05-17 14:07:28.217 2007-05-17
14:07:28.217 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 5324 53 2007-05-17 14:07:28.217
SQL:BatchStarting SELECT SERVERPROPERTY('Edition') Report Server NETWORK
SERVICE NT AUTHORITY\NETWORK SERVICE 5324 53 2007-05-17 14:07:28.217
SQL:BatchCompleted SELECT SERVERPROPERTY('Edition') Report Server NETWORK
SERVICE NT AUTHORITY\NETWORK SERVICE 0 0 0 0 5324 53 2007-05-17
14:07:28.217 2007-05-17 14:07:28.217
RPC:Completed exec GetOneConfigurationInfo @.Name=N'EnableMyReports' Report
Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 0 2 0 0 5324 53 2007-05-17 14:07:28.233 2007-05-17
14:07:28.233 0X00000000020000002E004700650074004F006E00650043006F006E00660069006700750072006100740069006F006E0049006E0066006F005000000082001800E7306E00760061007200630068006100720028003100350029000A0040004E0061006D0065001E00000045006E00610062006C0065004D0079005200650070006F007200740073001400000003000600380469006E00740000000000
Audit Logout Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 0 4 0 16 5324 53 2007-05-17 14:07:28.217 2007-05-17 14:07:28.233
RPC:Completed exec sp_reset_connection Report Server NETWORK SERVICE NT
AUTHORITY\NETWORK SERVICE 0 0 0 0 5324 53 2007-05-17 14:07:28.233 2007-05-17
14:07:28.233 0X00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00
Audit Login -- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Report Server NETWORK SERVICE NT AUTHORITY\NETWORK
SERVICE 5324 53 2007-05-17 14:07:28.233