CLR Stored procedure

Can I create a CLR stored procedure in VB or C# to print a file. Please give the code sample

All you would need to do it create a SQL Server project, add a stored procedure class, write your printing code inside there, and then deploy it to the database.

You probably shouldn't be doing this though. Any CLR stored procedures or functions should abide by the same principles as the database, which is to not rely on any resources which may not be there. Communicating with a printer is prone to this type of problem as the network may be down, or the printer may be off or out of paper etc. Therefore it shouldn't really be a stored procedure.

Client-side printing hangs IE

Hi,
When I try to print a report using client-side printing in SP2, I get the
Print dialog fine, then when I click 'OK' I get the 'Printing now...' popup,
but IE hangs instantly. I've tried removing the ActiveX component and
reregistering it but to no avail. However, it works fine on other machines
that we have. Rendering to PDF works fine, so the report itself must be OK.
Is anyone else seeing the same problem, or have any ideas about what could
be causing it?
Thanks,
Chris.I found that being logged in as Administrator works perfectly, so it seems
to be some sort of permissions issue on the server. Do I need to change any
security settings in IIS or folder security on the report server?
Interestingly, the Export feature doesn't work unless the user has
administrative rights on the local machine.
Any ideas?
Chris.
"Chris Childs" <chris@.nospam.nowhere.com> wrote in message
news:d4qc2t$3ni$1$8302bc10@.news.demon.co.uk...
> Hi,
> When I try to print a report using client-side printing in SP2, I get the
> Print dialog fine, then when I click 'OK' I get the 'Printing now...'
> popup, but IE hangs instantly. I've tried removing the ActiveX component
> and reregistering it but to no avail. However, it works fine on other
> machines that we have. Rendering to PDF works fine, so the report itself
> must be OK.
> Is anyone else seeing the same problem, or have any ideas about what could
> be causing it?
> Thanks,
> Chris.
>|||It sounds like a permissions issue. Can you export to Web Archive as a non
admin? Both of these features use the users temp directory for storing some
data, can you see if the users has write permission on his %temp% directory?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Childs" <chris@.nospam.nowhere.com> wrote in message
news:d4qeda$h40$1$8300dec7@.news.demon.co.uk...
>I found that being logged in as Administrator works perfectly, so it seems
>to be some sort of permissions issue on the server. Do I need to change
>any security settings in IIS or folder security on the report server?
> Interestingly, the Export feature doesn't work unless the user has
> administrative rights on the local machine.
> Any ideas?
> Chris.
> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
> news:d4qc2t$3ni$1$8302bc10@.news.demon.co.uk...
>> Hi,
>> When I try to print a report using client-side printing in SP2, I get the
>> Print dialog fine, then when I click 'OK' I get the 'Printing now...'
>> popup, but IE hangs instantly. I've tried removing the ActiveX component
>> and reregistering it but to no avail. However, it works fine on other
>> machines that we have. Rendering to PDF works fine, so the report itself
>> must be OK.
>> Is anyone else seeing the same problem, or have any ideas about what
>> could be causing it?
>> Thanks,
>> Chris.
>>
>|||Even when the user has full administrative rights on the local machine,
client-side printing still doesn't work. The user has full access to the
temp directory, and can export to both PDF and Web Archive formats.
Client-side printing only works when the user has administrative rights to
the domain. Maybe it is a setting in IIS, any ideas?
"Daniel Reib (MSFT)" <danreib@.online.microsoft.com> wrote in message
news:OkAdGcDTFHA.2520@.TK2MSFTNGP09.phx.gbl...
> It sounds like a permissions issue. Can you export to Web Archive as a
> non admin? Both of these features use the users temp directory for
> storing some data, can you see if the users has write permission on his
> %temp% directory?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
> news:d4qeda$h40$1$8300dec7@.news.demon.co.uk...
>>I found that being logged in as Administrator works perfectly, so it seems
>>to be some sort of permissions issue on the server. Do I need to change
>>any security settings in IIS or folder security on the report server?
>> Interestingly, the Export feature doesn't work unless the user has
>> administrative rights on the local machine.
>> Any ideas?
>> Chris.
>> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
>> news:d4qc2t$3ni$1$8302bc10@.news.demon.co.uk...
>> Hi,
>> When I try to print a report using client-side printing in SP2, I get
>> the Print dialog fine, then when I click 'OK' I get the 'Printing
>> now...' popup, but IE hangs instantly. I've tried removing the ActiveX
>> component and reregistering it but to no avail. However, it works fine
>> on other machines that we have. Rendering to PDF works fine, so the
>> report itself must be OK.
>> Is anyone else seeing the same problem, or have any ideas about what
>> could be causing it?
>> Thanks,
>> Chris.
>>
>>
>|||It is doubtful that it is an IIS setting. Are there any policies that block
ActiveX controls?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Childs" <chris@.nospam.nowhere.com> wrote in message
news:d4sq3p$od8$1$8302bc10@.news.demon.co.uk...
> Even when the user has full administrative rights on the local machine,
> client-side printing still doesn't work. The user has full access to the
> temp directory, and can export to both PDF and Web Archive formats.
> Client-side printing only works when the user has administrative rights to
> the domain. Maybe it is a setting in IIS, any ideas?
> "Daniel Reib (MSFT)" <danreib@.online.microsoft.com> wrote in message
> news:OkAdGcDTFHA.2520@.TK2MSFTNGP09.phx.gbl...
>> It sounds like a permissions issue. Can you export to Web Archive as a
>> non admin? Both of these features use the users temp directory for
>> storing some data, can you see if the users has write permission on his
>> %temp% directory?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
>> news:d4qeda$h40$1$8300dec7@.news.demon.co.uk...
>>I found that being logged in as Administrator works perfectly, so it
>>seems to be some sort of permissions issue on the server. Do I need to
>>change any security settings in IIS or folder security on the report
>>server?
>> Interestingly, the Export feature doesn't work unless the user has
>> administrative rights on the local machine.
>> Any ideas?
>> Chris.
>> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
>> news:d4qc2t$3ni$1$8302bc10@.news.demon.co.uk...
>> Hi,
>> When I try to print a report using client-side printing in SP2, I get
>> the Print dialog fine, then when I click 'OK' I get the 'Printing
>> now...' popup, but IE hangs instantly. I've tried removing the ActiveX
>> component and reregistering it but to no avail. However, it works fine
>> on other machines that we have. Rendering to PDF works fine, so the
>> report itself must be OK.
>> Is anyone else seeing the same problem, or have any ideas about what
>> could be causing it?
>> Thanks,
>> Chris.
>>
>>
>>
>|||No, the ActiveX control installs fine, and I get the print dialog, but then
it hangs when I print (or print preview) after that. We have no problems
with other ActiveX controls.
Chris.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:e$CvMMNTFHA.3848@.TK2MSFTNGP10.phx.gbl...
> It is doubtful that it is an IIS setting. Are there any policies that
> block ActiveX controls?
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
> news:d4sq3p$od8$1$8302bc10@.news.demon.co.uk...
>> Even when the user has full administrative rights on the local machine,
>> client-side printing still doesn't work. The user has full access to the
>> temp directory, and can export to both PDF and Web Archive formats.
>> Client-side printing only works when the user has administrative rights
>> to the domain. Maybe it is a setting in IIS, any ideas?
>> "Daniel Reib (MSFT)" <danreib@.online.microsoft.com> wrote in message
>> news:OkAdGcDTFHA.2520@.TK2MSFTNGP09.phx.gbl...
>> It sounds like a permissions issue. Can you export to Web Archive as a
>> non admin? Both of these features use the users temp directory for
>> storing some data, can you see if the users has write permission on his
>> %temp% directory?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
>> news:d4qeda$h40$1$8300dec7@.news.demon.co.uk...
>>I found that being logged in as Administrator works perfectly, so it
>>seems to be some sort of permissions issue on the server. Do I need to
>>change any security settings in IIS or folder security on the report
>>server?
>> Interestingly, the Export feature doesn't work unless the user has
>> administrative rights on the local machine.
>> Any ideas?
>> Chris.
>> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
>> news:d4qc2t$3ni$1$8302bc10@.news.demon.co.uk...
>> Hi,
>> When I try to print a report using client-side printing in SP2, I get
>> the Print dialog fine, then when I click 'OK' I get the 'Printing
>> now...' popup, but IE hangs instantly. I've tried removing the
>> ActiveX component and reregistering it but to no avail. However, it
>> works fine on other machines that we have. Rendering to PDF works
>> fine, so the report itself must be OK.
>> Is anyone else seeing the same problem, or have any ideas about what
>> could be causing it?
>> Thanks,
>> Chris.
>>
>>
>>
>>
>|||Try this...I think you may be missing RSClientPrint.Authenticate = false;
function Print()
{
RSClientPrint.MarginLeft = .5 * 25.4;
RSClientPrint.MarginTop = .5 * 25.4;
RSClientPrint.MarginRight = .5 * 25.4;
RSClientPrint.MarginBottom = .5 * 25.4;
RSClientPrint.Culture = 1033;
RSClientPrint.UICulture = 1033;
RSClientPrint.PageWidth = 11 * 25.4;
RSClientPrint.PageHeight = 8.5 * 25.4;
RSClientPrint.Authenticate = false;
RSClientPrint.Print('http://unisys1/reportserver',
'/Test/LMMISInquiry/RECIPIENTREIMBURSEMENT/ReportsAndLetters/AvgTurnaroundTime', 'AvgTurnaroundTime');
}
"Chris Childs" wrote:
> No, the ActiveX control installs fine, and I get the print dialog, but then
> it hangs when I print (or print preview) after that. We have no problems
> with other ActiveX controls.
> Chris.
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:e$CvMMNTFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > It is doubtful that it is an IIS setting. Are there any policies that
> > block ActiveX controls?
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> > "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
> > news:d4sq3p$od8$1$8302bc10@.news.demon.co.uk...
> >> Even when the user has full administrative rights on the local machine,
> >> client-side printing still doesn't work. The user has full access to the
> >> temp directory, and can export to both PDF and Web Archive formats.
> >> Client-side printing only works when the user has administrative rights
> >> to the domain. Maybe it is a setting in IIS, any ideas?
> >>
> >> "Daniel Reib (MSFT)" <danreib@.online.microsoft.com> wrote in message
> >> news:OkAdGcDTFHA.2520@.TK2MSFTNGP09.phx.gbl...
> >> It sounds like a permissions issue. Can you export to Web Archive as a
> >> non admin? Both of these features use the users temp directory for
> >> storing some data, can you see if the users has write permission on his
> >> %temp% directory?
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
> >> news:d4qeda$h40$1$8300dec7@.news.demon.co.uk...
> >>I found that being logged in as Administrator works perfectly, so it
> >>seems to be some sort of permissions issue on the server. Do I need to
> >>change any security settings in IIS or folder security on the report
> >>server?
> >>
> >> Interestingly, the Export feature doesn't work unless the user has
> >> administrative rights on the local machine.
> >>
> >> Any ideas?
> >>
> >> Chris.
> >>
> >> "Chris Childs" <chris@.nospam.nowhere.com> wrote in message
> >> news:d4qc2t$3ni$1$8302bc10@.news.demon.co.uk...
> >> Hi,
> >>
> >> When I try to print a report using client-side printing in SP2, I get
> >> the Print dialog fine, then when I click 'OK' I get the 'Printing
> >> now...' popup, but IE hangs instantly. I've tried removing the
> >> ActiveX component and reregistering it but to no avail. However, it
> >> works fine on other machines that we have. Rendering to PDF works
> >> fine, so the report itself must be OK.
> >>
> >> Is anyone else seeing the same problem, or have any ideas about what
> >> could be causing it?
> >>
> >> Thanks,
> >>
> >> Chris.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>

Client-side Printing and page hesitation

When printing reports from my normal computer to my default printer, all but
one report print without any hesitation between pages. My boss prints
reports and gets a lot of hesitation between pages for most of the reports.
If I print to a differnt printer I too get a lot of hesitation betwen pages.
Does SRS print pages as graphics or as text? Are there any settings on the
server that can alter printing performance? Anyone else having issues with
print hesitation and found a solution to the problem?When u want 2 controll the print properties u should set them at the Report
Properties->layout.
All properties in this tab are 4 the print setting.
"Rob 'Spike' Stevens" wrote:
> When printing reports from my normal computer to my default printer, all but
> one report print without any hesitation between pages. My boss prints
> reports and gets a lot of hesitation between pages for most of the reports.
> If I print to a differnt printer I too get a lot of hesitation betwen pages.
> Does SRS print pages as graphics or as text? Are there any settings on the
> server that can alter printing performance? Anyone else having issues with
> print hesitation and found a solution to the problem?

Client Side Printing SQL Report

Can anyone explain and maybe post some code on how to print a SQL Report in asp .net - I'm using SQL Reporting sp2 and I just can't find anything that works out there. Your help would be greatly appreciated... I tried RSClientprint.dll and had no luck...

thanks
rich

We're using "OfficeWriter" by a company called SoftArtisans. Note, it's not cheap.|||

I see - I'm looking for the ability to print the report only no need for all the other features - Thanks for your reply...

rich

|||

rperreta wrote:

Can anyone explain and maybe post some code on how to print a SQL Report in asp .net - I'm using SQL Reporting sp2 and I just can't find anything that works out there. Your help would be greatly appreciated... I tried RSClientprint.dll and had no luck...

thanks
rich

Why aren't you using the exporting features from RS? The client can preview and then export to the available formats, with the capability to save them AND print them.|||You can try Windows Script Host for clientside object creation and printing. It is Free by Microsoft.
http://msdn.microsoft.com/library/en-us/script56/html/wsconswitchingnetworkedprintersonoff.asp?frame=true
Regards,
Hemchand|||Hello!
I may not understand on "How To Print a Report in SQL Report in Asp.Net" but in the latest Service Pack 2 for Reporting Services there was an Active X control that displays an Icon on the toolbar that provides for direct printing of a Reporting Services report directly to any printer on your network.
From MS www site:
Key Functional EnhancementsReports can now be printed directly from within Internet Explorer. A Microsoft ActiveX control is provided to support a rich client-side printing experience including full page preview.|||

hi,

i would like to check where do u find the RSClientprint.dll? i try search my pc for the dll file but invalid.

if any1 can tell mi where to find it..greatly appreciated

your regards

angela

|||Hello:
There is a CAB file RSCLIENTPRINT in
(at least on my server) c:\Program files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin
I just then moved the dll's to the bin directory within the same directory structure above.
Best Reagrds,
|||hi,
i know of the active x print that will call the print frm RSClientPrint but the main issue that i concern is how can i not display the print dialog box where by it prompt the user to select the printer and print. Because i want to print the report automatically once i evoke a print button on my .net application. is there any ways to do it?
cheers
Angela|||

hooligannes97 wrote:

rperreta wrote:

Can anyone explain and maybe post some code on how to print a SQL Report in asp .net - I'm using SQL Reporting sp2 and I just can't find anything that works out there. Your help would be greatly appreciated... I tried RSClientprint.dll and had no luck...

thanks
rich

Why aren't you using the exporting features from RS? The client can preview and then export to the available formats, with the capability to save them AND print them.

RS? Microsoft Reporting Services?|||

rperreta wrote:

RS? Microsoft Reporting Services?

Correct

Client side printing

Hi
I am trying to print Query Result directly to the printer from Client
machine. I managed to do this on Server machine. Where I had written SP whic
h
accepts SQL as parameter and using osql and xp_cmdShell command I am
outputting CSV file to printer. I want to do same from client machine but I
want print out should get printed on client printer not on Server.
Any ideas or suggestions'
Many thanks in advance.
Regards,
Santoshxp_cmdshell is executed on the server machine, which has no knowledge of the
client who submitted
the SQL command. Perhaps you can specify the printer name using UNC naming s
o the print is done on
the server machine, but the destination is specified as the client?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Santosh" <Santosh@.discussions.microsoft.com> wrote in message
news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
> Hi
> I am trying to print Query Result directly to the printer from Client
> machine. I managed to do this on Server machine. Where I had written SP wh
ich
> accepts SQL as parameter and using osql and xp_cmdShell command I am
> outputting CSV file to printer. I want to do same from client machine but
I
> want print out should get printed on client printer not on Server.
> Any ideas or suggestions'
> Many thanks in advance.
> Regards,
> Santosh
>|||Thanks Tibor, yes what you are suggesting, makes sense.
But I feel it will be better if I drop this idea and look for some different
option. Because if we want to specify UNC naming for printer. I need to make
printer as shared and need to give permissions so it can be accessible from
server by other users. Since printers are getting cheaper and cheaper, almos
t
everyone at client-side got there own printers, so I doubt if client admin
will accept this solution.
"Tibor Karaszi" wrote:

> xp_cmdshell is executed on the server machine, which has no knowledge of t
he client who submitted
> the SQL command. Perhaps you can specify the printer name using UNC naming
so the print is done on
> the server machine, but the destination is specified as the client?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Santosh" <Santosh@.discussions.microsoft.com> wrote in message
> news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
>
>|||I agree with your assessment. Can you do the printing from the client app (w
hich I assume is running
on the client machine already)?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"sansaw80" <sansaw80@.discussions.microsoft.com> wrote in message
news:E7FB20CE-CDA7-4334-BA6F-AEAEDA694852@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor, yes what you are suggesting, makes sense.
> But I feel it will be better if I drop this idea and look for some differe
nt
> option. Because if we want to specify UNC naming for printer. I need to ma
ke
> printer as shared and need to give permissions so it can be accessible fro
m
> server by other users. Since printers are getting cheaper and cheaper, alm
ost
> everyone at client-side got there own printers, so I doubt if client admin
> will accept this solution.
>
>
> "Tibor Karaszi" wrote:
>|||Yup I can Print Crystal reports on local client printer through client app.
Now I have written small code in Vb.net which accepts SQL from client PC and
prints result in CSV format on local client printer.
"Tibor Karaszi" wrote:

> I agree with your assessment. Can you do the printing from the client app
(which I assume is running
> on the client machine already)?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "sansaw80" <sansaw80@.discussions.microsoft.com> wrote in message
> news:E7FB20CE-CDA7-4334-BA6F-AEAEDA694852@.microsoft.com...
>
>

Client Side Printing

Ok, for the life of me I can't seem to get this to work. Whenever I used the client-side print for SRS2000 SP2 it will always print out a blank page at the end.

At first I thought it was the margins, because not matter what I did the right-most column would always get chopped off. It would preview and look great, but as soon as I printed the page the last column would be chopped in half and print on a separate page.

So to troubleshoot I created a table that had only one column that was placed in the center of the page (using padding). Event after doing this the column STILL got chopped in half and printed out in two pages. Yet previewed and looked like it would print out ok.

Any help would be greatly appreciated. This one is driving me crazy.

Ok scratch this one. Turns out I wasn't accounting for the margins that were being set somewere. Once I reduced the body and table width by .1 inch then the right hand column isn't chopped and the correct number of pages prints out (no blanks).

There report has no margin and when printing I was sure to set the margins to 0 there as well.

Anyone tell me where this margin is coming from? Is this printer specific?

Thanks

|||

Have you tried to go to REPORT PROPERTIES for the specific report?

and establish the width in CM or inches?

Did you also look at report headers and footers

How large is your "print frame"

Are you using RS 2000 or RS 2005?

Can Help u!

|||

RS 2000.

The body of the report is 8.5" x 11". In the report properties->layout the page width is also 8.5" x 11". In the same section all margins are set to 0. My table is the entire width of the body (i.e. also 8.5" wide).

Now when I print the report using the Active X client side print component there is a margin added to the report that I hadn't accounted for. This margin was chopping the right column off and having it print on a separate page. This margin exists even though no margins are set for the report and when printing there are no margins set there as well.

What had been confusing me was that no matter how wide I made the table it still printed two pages. What I didn't realize is that I had to reduce the width of the body as well.

So by setting the width of the body to 8.45" and the width of the table to the same 8.45" the report prints on one page as expected.

Now, that we are on the same page, where did this margin come from knowing that I did not set it anywhere? The printer, RS2000, the client side Active X control...?

Thanks

|||

Hi,
I rather experience a very peculiar problem. I have developed a page in asp.net, which has a Print button by itself. It has to take the user to the printer window (I have used window.print()). When the user selects the printer and says print the first and the third page ( third page being the last page) gets printed properly where as the second page will have problems with the right side margin. This page is getting created on the run depending on the user's inputs. When I view the print preview, I found that the text in the next line of the page also comes to the previous page resulting in the loss of datain the II page content alone.

For example,

In the actual page, if I have

When a page from the web is printed, sometimes the right
hand side centremeter will be cut off.
Microsoft has a knowledge base article about this problem:

The text in the print preview would be,

When a page from the web is printed, sometimes the right hand side centremeter will be cut off. Microsoft has a
knowledge base article about this problem:

therefore resulting in the loss of data. I have tried adjusting the right and left side margins, but without luck.

This happens even if i print it with/without back to back option.
Even if i ask for the II page alone to be printed twice instead of the whole web page content, both the pages have the right side margin lost.

The same content that appears in the II page if made to appear in the III page does not affect the right margin of the III page. Thus, it does not have any content related issues.

Printing with landscape option wont be a reasonable option for the user. So, that can be ruled out.

Please advise what could be the work around at teh earliest as i have to get back to the user.

Client side printing

Hi
I am trying to print Query Result directly to the printer from Client
machine. I managed to do this on Server machine. Where I had written SP which
accepts SQL as parameter and using osql and xp_cmdShell command I am
outputting CSV file to printer. I want to do same from client machine but I
want print out should get printed on client printer not on Server.
Any ideas or suggestions?
Many thanks in advance.
Regards,
Santosh
xp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted
the SQL command. Perhaps you can specify the printer name using UNC naming so the print is done on
the server machine, but the destination is specified as the client?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Santosh" <Santosh@.discussions.microsoft.com> wrote in message
news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
> Hi
> I am trying to print Query Result directly to the printer from Client
> machine. I managed to do this on Server machine. Where I had written SP which
> accepts SQL as parameter and using osql and xp_cmdShell command I am
> outputting CSV file to printer. I want to do same from client machine but I
> want print out should get printed on client printer not on Server.
> Any ideas or suggestions?
> Many thanks in advance.
> Regards,
> Santosh
>
|||Thanks Tibor, yes what you are suggesting, makes sense.
But I feel it will be better if I drop this idea and look for some different
option. Because if we want to specify UNC naming for printer. I need to make
printer as shared and need to give permissions so it can be accessible from
server by other users. Since printers are getting cheaper and cheaper, almost
everyone at client-side got there own printers, so I doubt if client admin
will accept this solution.
"Tibor Karaszi" wrote:

> xp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted
> the SQL command. Perhaps you can specify the printer name using UNC naming so the print is done on
> the server machine, but the destination is specified as the client?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Santosh" <Santosh@.discussions.microsoft.com> wrote in message
> news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
>
>
|||I agree with your assessment. Can you do the printing from the client app (which I assume is running
on the client machine already)?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"sansaw80" <sansaw80@.discussions.microsoft.com> wrote in message
news:E7FB20CE-CDA7-4334-BA6F-AEAEDA694852@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor, yes what you are suggesting, makes sense.
> But I feel it will be better if I drop this idea and look for some different
> option. Because if we want to specify UNC naming for printer. I need to make
> printer as shared and need to give permissions so it can be accessible from
> server by other users. Since printers are getting cheaper and cheaper, almost
> everyone at client-side got there own printers, so I doubt if client admin
> will accept this solution.
>
>
> "Tibor Karaszi" wrote:
|||Yup I can Print Crystal reports on local client printer through client app.
Now I have written small code in Vb.net which accepts SQL from client PC and
prints result in CSV format on local client printer.
"Tibor Karaszi" wrote:

> I agree with your assessment. Can you do the printing from the client app (which I assume is running
> on the client machine already)?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "sansaw80" <sansaw80@.discussions.microsoft.com> wrote in message
> news:E7FB20CE-CDA7-4334-BA6F-AEAEDA694852@.microsoft.com...
>
>

Client side printing

Hi
I am trying to print Query Result directly to the printer from Client
machine. I managed to do this on Server machine. Where I had written SP which
accepts SQL as parameter and using osql and xp_cmdShell command I am
outputting CSV file to printer. I want to do same from client machine but I
want print out should get printed on client printer not on Server.
Any ideas or suggestions'
Many thanks in advance.
Regards,
Santoshxp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted
the SQL command. Perhaps you can specify the printer name using UNC naming so the print is done on
the server machine, but the destination is specified as the client?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Santosh" <Santosh@.discussions.microsoft.com> wrote in message
news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
> Hi
> I am trying to print Query Result directly to the printer from Client
> machine. I managed to do this on Server machine. Where I had written SP which
> accepts SQL as parameter and using osql and xp_cmdShell command I am
> outputting CSV file to printer. I want to do same from client machine but I
> want print out should get printed on client printer not on Server.
> Any ideas or suggestions'
> Many thanks in advance.
> Regards,
> Santosh
>|||Thanks Tibor, yes what you are suggesting, makes sense.
But I feel it will be better if I drop this idea and look for some different
option. Because if we want to specify UNC naming for printer. I need to make
printer as shared and need to give permissions so it can be accessible from
server by other users. Since printers are getting cheaper and cheaper, almost
everyone at client-side got there own printers, so I doubt if client admin
will accept this solution.
"Tibor Karaszi" wrote:
> xp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted
> the SQL command. Perhaps you can specify the printer name using UNC naming so the print is done on
> the server machine, but the destination is specified as the client?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Santosh" <Santosh@.discussions.microsoft.com> wrote in message
> news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
> > Hi
> >
> > I am trying to print Query Result directly to the printer from Client
> > machine. I managed to do this on Server machine. Where I had written SP which
> > accepts SQL as parameter and using osql and xp_cmdShell command I am
> > outputting CSV file to printer. I want to do same from client machine but I
> > want print out should get printed on client printer not on Server.
> >
> > Any ideas or suggestions'
> >
> > Many thanks in advance.
> >
> > Regards,
> > Santosh
> >
>
>|||I agree with your assessment. Can you do the printing from the client app (which I assume is running
on the client machine already)?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"sansaw80" <sansaw80@.discussions.microsoft.com> wrote in message
news:E7FB20CE-CDA7-4334-BA6F-AEAEDA694852@.microsoft.com...
> Thanks Tibor, yes what you are suggesting, makes sense.
> But I feel it will be better if I drop this idea and look for some different
> option. Because if we want to specify UNC naming for printer. I need to make
> printer as shared and need to give permissions so it can be accessible from
> server by other users. Since printers are getting cheaper and cheaper, almost
> everyone at client-side got there own printers, so I doubt if client admin
> will accept this solution.
>
>
> "Tibor Karaszi" wrote:
>> xp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted
>> the SQL command. Perhaps you can specify the printer name using UNC naming so the print is done
>> on
>> the server machine, but the destination is specified as the client?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "Santosh" <Santosh@.discussions.microsoft.com> wrote in message
>> news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
>> > Hi
>> >
>> > I am trying to print Query Result directly to the printer from Client
>> > machine. I managed to do this on Server machine. Where I had written SP which
>> > accepts SQL as parameter and using osql and xp_cmdShell command I am
>> > outputting CSV file to printer. I want to do same from client machine but I
>> > want print out should get printed on client printer not on Server.
>> >
>> > Any ideas or suggestions'
>> >
>> > Many thanks in advance.
>> >
>> > Regards,
>> > Santosh
>> >
>>|||Yup I can Print Crystal reports on local client printer through client app.
Now I have written small code in Vb.net which accepts SQL from client PC and
prints result in CSV format on local client printer.
"Tibor Karaszi" wrote:
> I agree with your assessment. Can you do the printing from the client app (which I assume is running
> on the client machine already)?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "sansaw80" <sansaw80@.discussions.microsoft.com> wrote in message
> news:E7FB20CE-CDA7-4334-BA6F-AEAEDA694852@.microsoft.com...
> > Thanks Tibor, yes what you are suggesting, makes sense.
> >
> > But I feel it will be better if I drop this idea and look for some different
> > option. Because if we want to specify UNC naming for printer. I need to make
> > printer as shared and need to give permissions so it can be accessible from
> > server by other users. Since printers are getting cheaper and cheaper, almost
> > everyone at client-side got there own printers, so I doubt if client admin
> > will accept this solution.
> >
> >
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> xp_cmdshell is executed on the server machine, which has no knowledge of the client who submitted
> >> the SQL command. Perhaps you can specify the printer name using UNC naming so the print is done
> >> on
> >> the server machine, but the destination is specified as the client?
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> http://www.sqlug.se/
> >>
> >>
> >> "Santosh" <Santosh@.discussions.microsoft.com> wrote in message
> >> news:A37189CF-9AFE-403A-97FC-2586C96C275B@.microsoft.com...
> >> > Hi
> >> >
> >> > I am trying to print Query Result directly to the printer from Client
> >> > machine. I managed to do this on Server machine. Where I had written SP which
> >> > accepts SQL as parameter and using osql and xp_cmdShell command I am
> >> > outputting CSV file to printer. I want to do same from client machine but I
> >> > want print out should get printed on client printer not on Server.
> >> >
> >> > Any ideas or suggestions'
> >> >
> >> > Many thanks in advance.
> >> >
> >> > Regards,
> >> > Santosh
> >> >
> >>
> >>
> >>
>
>

client side print button not visible even in SQL Server 2005 Express SP 2.0

Hi All!

i installed SQL Server 2005 express edition Service Pack 2.0, SQL server Advance Services, and Toolkit . Still Print button in client side report is not visible in web form.

please help me.

thanks in advance.

rkraju:

Hi All!

i installed SQL Server 2005 express edition Service Pack 2.0, SQL server Advance Services, and Toolkit . Still Print button in client side report is not visible in web form.

please help me.

thanks in advance.

Wel I guess we cannot do that...printing is not available on client SSRS...Too bad...And just to let you know, if you need to send query parameters to the report forget the client SSRS again...it sucks...you have to install the report on the Web server and that way yes you can print and send query parameters and so long...other way no solution...

Read here...I'm feeling frustrated on this...

http://blogs.msdn.com/mohamed_sharafs_blog/archive/2005/12/20/LocalReportCustomCode.aspx

However if you've found another solution please let me know!!!Thanks a lot!

Client Side Print - An error occured during printing. (ox80070006)

When trying to print a report using the ActiveX control in Internet
Explorer I get the following error:
An error occured during printing. (ox80070006)
After some experimenting I found I was able to print (same client
computer / same server) to a file using the Generic / Text Only printer
driver and the Microsoft Office Document Image Writer.
So based on that I assumed the problem wasn't with the server.
Next I tried hooking my printer directly to my computer. The same
error occured.
I then tried a separate computer that printed to a separeate computer
and it worked.
Based on this I am assuming there is a issue with my printer / printer
driver and the ActiveX control.
My printer is a Samsung ML-1430.
I wanted to report this to the Reporting Services Team and see if
anyone else had any similar problems with other printers.
Thanks,
Warren Hales
P.S. I am new to Reporting Services and I have to say I am VERY
impressed. The Reporting Services Team has done a great job (IMHO).
It is an excellent example of an application with a SOA.Have you tried making sure you have a recent print driver? There have been
reports about printing problems going away once they updated the print
drivers.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Warren Hales" <warrenhales@.hotmail.com> wrote in message
news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
> When trying to print a report using the ActiveX control in Internet
> Explorer I get the following error:
> An error occured during printing. (ox80070006)
> After some experimenting I found I was able to print (same client
> computer / same server) to a file using the Generic / Text Only printer
> driver and the Microsoft Office Document Image Writer.
> So based on that I assumed the problem wasn't with the server.
> Next I tried hooking my printer directly to my computer. The same
> error occured.
> I then tried a separate computer that printed to a separeate computer
> and it worked.
> Based on this I am assuming there is a issue with my printer / printer
> driver and the ActiveX control.
> My printer is a Samsung ML-1430.
> I wanted to report this to the Reporting Services Team and see if
> anyone else had any similar problems with other printers.
> Thanks,
> Warren Hales
> P.S. I am new to Reporting Services and I have to say I am VERY
> impressed. The Reporting Services Team has done a great job (IMHO).
> It is an excellent example of an application with a SOA.
>|||Hey Bruce.
I did download the latest print driver from Samsung and had the same
problem. I even tried a print driver from a compatible Samsung print
driver and that didn't work either.
One weird thing I found. If you click on the "printer" button in the
print dialog box, close it and then click print it gets a bit farther
along in the process. It prints a blank page and then shows the error
message.
Bruce L-C [MVP] wrote:
> Have you tried making sure you have a recent print driver? There have
been
> reports about printing problems going away once they updated the
print
> drivers.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
> news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
> > When trying to print a report using the ActiveX control in Internet
> > Explorer I get the following error:
> >
> > An error occured during printing. (ox80070006)
> >
> > After some experimenting I found I was able to print (same client
> > computer / same server) to a file using the Generic / Text Only
printer
> > driver and the Microsoft Office Document Image Writer.
> >
> > So based on that I assumed the problem wasn't with the server.
> >
> > Next I tried hooking my printer directly to my computer. The same
> > error occured.
> >
> > I then tried a separate computer that printed to a separeate
computer
> > and it worked.
> >
> > Based on this I am assuming there is a issue with my printer /
printer
> > driver and the ActiveX control.
> >
> > My printer is a Samsung ML-1430.
> >
> > I wanted to report this to the Reporting Services Team and see if
> > anyone else had any similar problems with other printers.
> >
> > Thanks,
> >
> > Warren Hales
> >
> > P.S. I am new to Reporting Services and I have to say I am VERY
> > impressed. The Reporting Services Team has done a great job
(IMHO).
> > It is an excellent example of an application with a SOA.
> >|||On of the problems might be the size of the print job that we send to the
printer. We are currently using a format called EMF + Dual which is pretty
hefty. We are looking whether we can trim it down in SQL 2005.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Warren Hales" <warrenhales@.hotmail.com> wrote in message
news:1116688171.637976.68360@.g47g2000cwa.googlegroups.com...
> Hey Bruce.
> I did download the latest print driver from Samsung and had the same
> problem. I even tried a print driver from a compatible Samsung print
> driver and that didn't work either.
> One weird thing I found. If you click on the "printer" button in the
> print dialog box, close it and then click print it gets a bit farther
> along in the process. It prints a blank page and then shows the error
> message.
> Bruce L-C [MVP] wrote:
>> Have you tried making sure you have a recent print driver? There have
> been
>> reports about printing problems going away once they updated the
> print
>> drivers.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
>> news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
>> > When trying to print a report using the ActiveX control in Internet
>> > Explorer I get the following error:
>> >
>> > An error occured during printing. (ox80070006)
>> >
>> > After some experimenting I found I was able to print (same client
>> > computer / same server) to a file using the Generic / Text Only
> printer
>> > driver and the Microsoft Office Document Image Writer.
>> >
>> > So based on that I assumed the problem wasn't with the server.
>> >
>> > Next I tried hooking my printer directly to my computer. The same
>> > error occured.
>> >
>> > I then tried a separate computer that printed to a separeate
> computer
>> > and it worked.
>> >
>> > Based on this I am assuming there is a issue with my printer /
> printer
>> > driver and the ActiveX control.
>> >
>> > My printer is a Samsung ML-1430.
>> >
>> > I wanted to report this to the Reporting Services Team and see if
>> > anyone else had any similar problems with other printers.
>> >
>> > Thanks,
>> >
>> > Warren Hales
>> >
>> > P.S. I am new to Reporting Services and I have to say I am VERY
>> > impressed. The Reporting Services Team has done a great job
> (IMHO).
>> > It is an excellent example of an application with a SOA.
>> >
>|||FYI - I am seeing the same problem from one of our servers. The strange
thing is that I can print fine on two other servers that have SP2 installed
from the same reports on the same printers. One of the servers where the
printing is working was recently built (with SP2) and the other was upgraded
from SP1 to SP2 recently, so I can't see any pattern of when, where and why
this error is happening. It is failing on most of our reports that span 1
page (small reports as well as large ones). Any help is appreciated,
Brad Peterman
"Brian Welcker [MSFT]" wrote:
> On of the problems might be the size of the print job that we send to the
> printer. We are currently using a format called EMF + Dual which is pretty
> hefty. We are looking whether we can trim it down in SQL 2005.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
> news:1116688171.637976.68360@.g47g2000cwa.googlegroups.com...
> > Hey Bruce.
> >
> > I did download the latest print driver from Samsung and had the same
> > problem. I even tried a print driver from a compatible Samsung print
> > driver and that didn't work either.
> >
> > One weird thing I found. If you click on the "printer" button in the
> > print dialog box, close it and then click print it gets a bit farther
> > along in the process. It prints a blank page and then shows the error
> > message.
> >
> > Bruce L-C [MVP] wrote:
> >> Have you tried making sure you have a recent print driver? There have
> > been
> >> reports about printing problems going away once they updated the
> > print
> >> drivers.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
> >> news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
> >> > When trying to print a report using the ActiveX control in Internet
> >> > Explorer I get the following error:
> >> >
> >> > An error occured during printing. (ox80070006)
> >> >
> >> > After some experimenting I found I was able to print (same client
> >> > computer / same server) to a file using the Generic / Text Only
> > printer
> >> > driver and the Microsoft Office Document Image Writer.
> >> >
> >> > So based on that I assumed the problem wasn't with the server.
> >> >
> >> > Next I tried hooking my printer directly to my computer. The same
> >> > error occured.
> >> >
> >> > I then tried a separate computer that printed to a separeate
> > computer
> >> > and it worked.
> >> >
> >> > Based on this I am assuming there is a issue with my printer /
> > printer
> >> > driver and the ActiveX control.
> >> >
> >> > My printer is a Samsung ML-1430.
> >> >
> >> > I wanted to report this to the Reporting Services Team and see if
> >> > anyone else had any similar problems with other printers.
> >> >
> >> > Thanks,
> >> >
> >> > Warren Hales
> >> >
> >> > P.S. I am new to Reporting Services and I have to say I am VERY
> >> > impressed. The Reporting Services Team has done a great job
> > (IMHO).
> >> > It is an excellent example of an application with a SOA.
> >> >
> >
>
>

Client Print To Dot Matrix Printer (Urgent)

I'm using ActiveX control to print report in client side, it's great for user. However, I have some reports which need to be printed to dotmatrix printer (Epson LQ 1600K III), they chould not be printed properly, all the fonts are always indouble width and half height.
But if I print those report to my laser printer or print them to dotmatrix printer in VS.NET, it's OK. See as below:
Print on laser priner
******************************
* * *
* * *
* *
* *
* *
******************************
Print on dotmatrix priner
======================================
= = =
= = =
= =
======================================

Is it a microsoft bug? Should I set something in my report or in printer driver (Printer Processer)?
Thanks in advance!

I'm having the same issue, did you get it working? Also wcich ActiveX control are you using?
Thanks
ma_flash

|||

No, I still have this issue, whatever I changed the processer in printer driver, it did not work.
I'm using new ActiveX Control in Reporting Service SP2, it is downloaded from report server when first time user load report. I think it is not consistent with VS.NET, because I can print reports to dotmatrix printer in VS.NET propoerly, but not in ActiveX Control.

|||

Can you kindly share the code of how to stream a report server directly to your local printer?

Thanks, Edmund

Clicking print from Reporting Services report cause computer to re

I have a report developed using Reporting Services 2005 with SQL Server 2005.
It runs just fine, and printed fine up until a few days ago. Now, after I
run the report and it displays on the screen, clicking print causes the
computer to reboot. Not all the reports do this, just this one. I don't
know of anything that has changed that could cause this problem. Anyone have
a similar experience? The report uses a stored procedure to build a table.
But, again it did work o.k. until a few days ago.
ThanksSAME PROBLEM HERE !!
Our client called us yesterday, everything worked fine and now clicking the
print button on 1 or 2 reports just REBOOT the computer !
We are using Reporting Services 2000 with SQL Server 2000.
Please help!
"Glenna" wrote:
> I have a report developed using Reporting Services 2005 with SQL Server 2005.
> It runs just fine, and printed fine up until a few days ago. Now, after I
> run the report and it displays on the screen, clicking print causes the
> computer to reboot. Not all the reports do this, just this one. I don't
> know of anything that has changed that could cause this problem. Anyone have
> a similar experience? The report uses a stored procedure to build a table.
> But, again it did work o.k. until a few days ago.
> Thanks|||We rae now having the same issues...SQL RS 2005, SQL 2000...any hotfixes or
patches?
"KhAoS" wrote:
> SAME PROBLEM HERE !!
> Our client called us yesterday, everything worked fine and now clicking the
> print button on 1 or 2 reports just REBOOT the computer !
> We are using Reporting Services 2000 with SQL Server 2000.
> Please help!
> "Glenna" wrote:
> > I have a report developed using Reporting Services 2005 with SQL Server 2005.
> > It runs just fine, and printed fine up until a few days ago. Now, after I
> > run the report and it displays on the screen, clicking print causes the
> > computer to reboot. Not all the reports do this, just this one. I don't
> > know of anything that has changed that could cause this problem. Anyone have
> > a similar experience? The report uses a stored procedure to build a table.
> > But, again it did work o.k. until a few days ago.
> >
> > Thanks|||On Apr 18, 10:36 am, pbriggsiberia
<pbriggsibe...@.discussions.microsoft.com> wrote:
> We rae now having the same issues...SQL RS 2005, SQL 2000...any hotfixes or
> patches?
>
> "KhAoS" wrote:
> > SAME PROBLEM HERE !!
> > Our client called us yesterday, everything worked fine and now clicking the
> >printbutton on 1 or 2 reports justREBOOTthe computer !
> > We are using Reporting Services 2000 with SQL Server 2000.
> > Please help!
> > "Glenna" wrote:
> > > I have a report developed using Reporting Services 2005 with SQL Server 2005.
> > > It runs just fine, and printed fine up until a few days ago. Now, after I
> > > run the report and it displays on the screen, clickingprintcausesthe
> > > computer toreboot. Not all the reports do this, just this one. I don't
> > > know of anything that has changed that could cause this problem. Anyone have
> > > a similar experience? The report uses a stored procedure to build a table.
> > > But, again it did work o.k. until a few days ago.
> > > Thanks- Hide quoted text -
> - Show quoted text -
I am having the same problem. Has anyone found the solution to this?|||Found the solution on another forum!!
The problem come from a recent update patch from microsoft that affects some
printers drivers.
To get rid of the problem, install this hotfix (KB935843) :
http://www.microsoft.com/downloads/details.aspx?familyid=69443B00-F831-4785-B292-DBF8CF002C6A&displaylang=en
More infos : http://support.microsoft.com/?kbid=935843
"jrichardson2@.chkenergy.com" wrote:
> On Apr 18, 10:36 am, pbriggsiberia
> <pbriggsibe...@.discussions.microsoft.com> wrote:
> > We rae now having the same issues...SQL RS 2005, SQL 2000...any hotfixes or
> > patches?
> >
> >
> >
> > "KhAoS" wrote:
> > > SAME PROBLEM HERE !!
> > > Our client called us yesterday, everything worked fine and now clicking the
> > >printbutton on 1 or 2 reports justREBOOTthe computer !
> > > We are using Reporting Services 2000 with SQL Server 2000.
> >
> > > Please help!
> >
> > > "Glenna" wrote:
> >
> > > > I have a report developed using Reporting Services 2005 with SQL Server 2005.
> > > > It runs just fine, and printed fine up until a few days ago. Now, after I
> > > > run the report and it displays on the screen, clickingprintcausesthe
> > > > computer toreboot. Not all the reports do this, just this one. I don't
> > > > know of anything that has changed that could cause this problem. Anyone have
> > > > a similar experience? The report uses a stored procedure to build a table.
> > > > But, again it did work o.k. until a few days ago.
> >
> > > > Thanks- Hide quoted text -
> >
> > - Show quoted text -
> I am having the same problem. Has anyone found the solution to this?
>