can't see print messages during the running a of stored procedure

I have a stored procedure running from Query Analyzer that runs for a long
time and would like to have status messages print out during the procedure.
They all seem to come when the procedure is complete - is there any way to
have them print while it is running. I 've actually tried having the main
SP call a smaller SP with prints, but they don't come out till the end as
well.
Help to a new Transact SQL writer,
Thanks
TW
TW,
I don't know how to do just what you want, but you could try pumping your
messages into a trace table. Then you could query that table while the
long-running stored procedure continues. Transaction isolation levels would
affect how this works for you.
Russell Fields
"Weave" <tweaver60@.suscom.net> wrote in message
news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the
procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>
|||You could use RAISERROR and the NOWAIT option instead of PRINT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Weave" <tweaver60@.suscom.net> wrote in message news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>

Can't see print button

Hi. I'm starting with Reporting Services 2005 and I need to use it in a web
application.
I followed the steps I found in the MSDN. I create a datasource, create the
report and then I use it in a report viewer control.
I found some problems:
1) I see no print button, and it's set to true in the viewer
2) I only can export to Excel. No other alternatives are possible.
3) I have compilation errors adding some columns from the dataset.
Can you help me to solve some of these problems?
Thank you in advance.
--
Regards,
Diego F.For #1, print is not supported in local mode processing, that is why there
is no button.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Diego F." <diegofrNO@.terra.es> wrote in message
news:%23kin1HREGHA.344@.TK2MSFTNGP11.phx.gbl...
> Hi. I'm starting with Reporting Services 2005 and I need to use it in a
> web application.
> I followed the steps I found in the MSDN. I create a datasource, create
> the report and then I use it in a report viewer control.
> I found some problems:
> 1) I see no print button, and it's set to true in the viewer
> 2) I only can export to Excel. No other alternatives are possible.
> 3) I have compilation errors adding some columns from the dataset.
> Can you help me to solve some of these problems?
> Thank you in advance.
> --
> Regards,
> Diego F.
>
>

cant print variable

Hi,
In the query analyser if I type the following:

DECLARE @.SortOrder integer
exec pr_Admin_SetFieldSortOrder @.SortOrder
print @.SortOrder

@.SortOrder is never printed. I just get the message saying that the
Query Batch Completed.

Why ?

RegardsI guess @.SortOrder is an output parameter? If so, you need to add
OUTPUT:

exec pr_Admin_SetFieldSortOrder @.SortOrder OUTPUT

Simon|||cool
thx

Can't print from SSRS on Citrix

Hi,
We have SSRS 2005 running on SQL Server 2000 on a Citrix network. When I
click the print icon in SSRS, I get an Internet Explorer Security Warning
asking if I want to install Microsoft SQL Server. When I click "Don't
Install" I get the message, "Unable to load client print control." It seems
like there's a component that needs to be installed to enable printing from
SSRS, but I don't know what it is. Can anyone point me in the right
direction here?
--
Thanks,
JeffI think the IE security Warning refers to installing SSRS's report
preview/print activeX control, not the SQL Server itself. When you use IE to
open a report and try to print it the first time, that preview/print ActiveX
control must be downloaded to the computer where IE run and installed. So,
you need to go ahead to allow the installation once for all.
"Jeff Stroope" <JeffStroope@.discussions.microsoft.com> wrote in message
news:6C241737-15F5-4A8C-9FD5-724D650105DC@.microsoft.com...
> Hi,
> We have SSRS 2005 running on SQL Server 2000 on a Citrix network. When I
> click the print icon in SSRS, I get an Internet Explorer Security Warning
> asking if I want to install Microsoft SQL Server. When I click "Don't
> Install" I get the message, "Unable to load client print control." It
> seems
> like there's a component that needs to be installed to enable printing
> from
> SSRS, but I don't know what it is. Can anyone point me in the right
> direction here?
> --
> Thanks,
> Jeff|||Thanks Norman!
--
Thanks,
Jeff
"Norman Yuan" wrote:
> I think the IE security Warning refers to installing SSRS's report
> preview/print activeX control, not the SQL Server itself. When you use IE to
> open a report and try to print it the first time, that preview/print ActiveX
> control must be downloaded to the computer where IE run and installed. So,
> you need to go ahead to allow the installation once for all.
> "Jeff Stroope" <JeffStroope@.discussions.microsoft.com> wrote in message
> news:6C241737-15F5-4A8C-9FD5-724D650105DC@.microsoft.com...
> > Hi,
> >
> > We have SSRS 2005 running on SQL Server 2000 on a Citrix network. When I
> > click the print icon in SSRS, I get an Internet Explorer Security Warning
> > asking if I want to install Microsoft SQL Server. When I click "Don't
> > Install" I get the message, "Unable to load client print control." It
> > seems
> > like there's a component that needs to be installed to enable printing
> > from
> > SSRS, but I don't know what it is. Can anyone point me in the right
> > direction here?
> > --
> > Thanks,
> >
> > Jeff
>
>

Can't get reports to print

Hello,
We have never been able to get the printing to work on any of our reports
using SQL Server Reporting Services SP2.
During the time we have been fighting to get this to work we had added on
the SP, so we totally rebuilt the machine from scratch, that didn't help. In
addition a couple of months ago we bought a totally new machine to host our
reports and the fresh install on that machine didn't yeild any results.
At some point I found some posts in the newsgroup about needing to uninstall
an old ActiveX control used for printing, I did this and installed the new
one but that didn't help either.
We can print to things like the "Microsoft Office Document Image Writer"
without problem, only when we try to print to a real printer does it bomb out.
It doesn't matter how big the report is, 100 pages or 1/4 of a page, same
problem.
We do the following:
Run the report
Click the print button
Select a printer and press ok
"Printing Now..." dialog box appears
"Print Error" dialog appears showing "An error occured during printing.
(0x80004005). The misspelling of "occured" is how it is displayed in the
message.
Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied Error".
This is the result on every computer we have ever used in trying to access
the report server.
Any help?Are you printing to a local or network printer? Printing from IE, Firefox,
<insert other browser here>? I've had the best luck printing from IE to a
local printer.
--
Floyd
"msmolarek@.community.nospam"
<msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> Hello,
> We have never been able to get the printing to work on any of our reports
> using SQL Server Reporting Services SP2.
> During the time we have been fighting to get this to work we had added on
> the SP, so we totally rebuilt the machine from scratch, that didn't help.
> In
> addition a couple of months ago we bought a totally new machine to host
> our
> reports and the fresh install on that machine didn't yeild any results.
> At some point I found some posts in the newsgroup about needing to
> uninstall
> an old ActiveX control used for printing, I did this and installed the new
> one but that didn't help either.
> We can print to things like the "Microsoft Office Document Image Writer"
> without problem, only when we try to print to a real printer does it bomb
> out.
> It doesn't matter how big the report is, 100 pages or 1/4 of a page, same
> problem.
> We do the following:
> Run the report
> Click the print button
> Select a printer and press ok
> "Printing Now..." dialog box appears
> "Print Error" dialog appears showing "An error occured during printing.
> (0x80004005). The misspelling of "occured" is how it is displayed in the
> message.
> Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> Error".
>
> This is the result on every computer we have ever used in trying to access
> the report server.
> Any help?|||We are printing to network printers from IE.
I hooked up a local printer to a computer just to try, and it prints the
first page OK, and then pops up the same error message as usual: "0x80004005"
Even if it worked on a local printer, this is supposed to be an enterprise
solution. 99% of our employees print to network printers.
"Floyd Burger" wrote:
> Are you printing to a local or network printer? Printing from IE, Firefox,
> <insert other browser here>? I've had the best luck printing from IE to a
> local printer.
> --
> Floyd
> "msmolarek@.community.nospam"
> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> > Hello,
> >
> > We have never been able to get the printing to work on any of our reports
> > using SQL Server Reporting Services SP2.
> >
> > During the time we have been fighting to get this to work we had added on
> > the SP, so we totally rebuilt the machine from scratch, that didn't help.
> > In
> > addition a couple of months ago we bought a totally new machine to host
> > our
> > reports and the fresh install on that machine didn't yeild any results.
> >
> > At some point I found some posts in the newsgroup about needing to
> > uninstall
> > an old ActiveX control used for printing, I did this and installed the new
> > one but that didn't help either.
> >
> > We can print to things like the "Microsoft Office Document Image Writer"
> > without problem, only when we try to print to a real printer does it bomb
> > out.
> >
> > It doesn't matter how big the report is, 100 pages or 1/4 of a page, same
> > problem.
> >
> > We do the following:
> >
> > Run the report
> > Click the print button
> > Select a printer and press ok
> > "Printing Now..." dialog box appears
> > "Print Error" dialog appears showing "An error occured during printing.
> > (0x80004005). The misspelling of "occured" is how it is displayed in the
> > message.
> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> > Error".
> >
> >
> > This is the result on every computer we have ever used in trying to access
> > the report server.
> >
> > Any help?
>
>|||I print exclusively to network printers. We do not have local printers at
work.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"msmolarek@.community.nospam"
<msmolarekcommunitynospam@.discussions.microsoft.com> wrote in message
news:5378230C-8CCE-43BE-9868-D1BC12940358@.microsoft.com...
> We are printing to network printers from IE.
> I hooked up a local printer to a computer just to try, and it prints the
> first page OK, and then pops up the same error message as usual:
> "0x80004005"
> Even if it worked on a local printer, this is supposed to be an enterprise
> solution. 99% of our employees print to network printers.
>
> "Floyd Burger" wrote:
>> Are you printing to a local or network printer? Printing from IE,
>> Firefox,
>> <insert other browser here>? I've had the best luck printing from IE to
>> a
>> local printer.
>> --
>> Floyd
>> "msmolarek@.community.nospam"
>> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
>> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
>> > Hello,
>> >
>> > We have never been able to get the printing to work on any of our
>> > reports
>> > using SQL Server Reporting Services SP2.
>> >
>> > During the time we have been fighting to get this to work we had added
>> > on
>> > the SP, so we totally rebuilt the machine from scratch, that didn't
>> > help.
>> > In
>> > addition a couple of months ago we bought a totally new machine to host
>> > our
>> > reports and the fresh install on that machine didn't yeild any results.
>> >
>> > At some point I found some posts in the newsgroup about needing to
>> > uninstall
>> > an old ActiveX control used for printing, I did this and installed the
>> > new
>> > one but that didn't help either.
>> >
>> > We can print to things like the "Microsoft Office Document Image
>> > Writer"
>> > without problem, only when we try to print to a real printer does it
>> > bomb
>> > out.
>> >
>> > It doesn't matter how big the report is, 100 pages or 1/4 of a page,
>> > same
>> > problem.
>> >
>> > We do the following:
>> >
>> > Run the report
>> > Click the print button
>> > Select a printer and press ok
>> > "Printing Now..." dialog box appears
>> > "Print Error" dialog appears showing "An error occured during printing.
>> > (0x80004005). The misspelling of "occured" is how it is displayed in
>> > the
>> > message.
>> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
>> > Error".
>> >
>> >
>> > This is the result on every computer we have ever used in trying to
>> > access
>> > the report server.
>> >
>> > Any help?
>>|||How can I find the disconnect here then?
I have read that this error indicates "Access is denied", and others have
mentioned that maybe I don't have printer rights.
I am logged into my machine as a domain admin. I have no printing problems
in any program to any printer, except when using Reporting Services.
"Bruce L-C [MVP]" wrote:
> I print exclusively to network printers. We do not have local printers at
> work.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "msmolarek@.community.nospam"
> <msmolarekcommunitynospam@.discussions.microsoft.com> wrote in message
> news:5378230C-8CCE-43BE-9868-D1BC12940358@.microsoft.com...
> > We are printing to network printers from IE.
> >
> > I hooked up a local printer to a computer just to try, and it prints the
> > first page OK, and then pops up the same error message as usual:
> > "0x80004005"
> >
> > Even if it worked on a local printer, this is supposed to be an enterprise
> > solution. 99% of our employees print to network printers.
> >
> >
> > "Floyd Burger" wrote:
> >
> >> Are you printing to a local or network printer? Printing from IE,
> >> Firefox,
> >> <insert other browser here>? I've had the best luck printing from IE to
> >> a
> >> local printer.
> >>
> >> --
> >> Floyd
> >>
> >> "msmolarek@.community.nospam"
> >> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
> >> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> >> > Hello,
> >> >
> >> > We have never been able to get the printing to work on any of our
> >> > reports
> >> > using SQL Server Reporting Services SP2.
> >> >
> >> > During the time we have been fighting to get this to work we had added
> >> > on
> >> > the SP, so we totally rebuilt the machine from scratch, that didn't
> >> > help.
> >> > In
> >> > addition a couple of months ago we bought a totally new machine to host
> >> > our
> >> > reports and the fresh install on that machine didn't yeild any results.
> >> >
> >> > At some point I found some posts in the newsgroup about needing to
> >> > uninstall
> >> > an old ActiveX control used for printing, I did this and installed the
> >> > new
> >> > one but that didn't help either.
> >> >
> >> > We can print to things like the "Microsoft Office Document Image
> >> > Writer"
> >> > without problem, only when we try to print to a real printer does it
> >> > bomb
> >> > out.
> >> >
> >> > It doesn't matter how big the report is, 100 pages or 1/4 of a page,
> >> > same
> >> > problem.
> >> >
> >> > We do the following:
> >> >
> >> > Run the report
> >> > Click the print button
> >> > Select a printer and press ok
> >> > "Printing Now..." dialog box appears
> >> > "Print Error" dialog appears showing "An error occured during printing.
> >> > (0x80004005). The misspelling of "occured" is how it is displayed in
> >> > the
> >> > message.
> >> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> >> > Error".
> >> >
> >> >
> >> > This is the result on every computer we have ever used in trying to
> >> > access
> >> > the report server.
> >> >
> >> > Any help?
> >>
> >>
> >>
>
>|||I have the same error on network printers..Anyone have any more advise on
this issue. I can add that the event log on the machine spits out event error
3, 4,8 in order when you issue the print command.
--
Ron Hatfield
Senior Consultant
I.B.I.S., Inc.
"msmolarek@.community.nospam" wrote:
> How can I find the disconnect here then?
> I have read that this error indicates "Access is denied", and others have
> mentioned that maybe I don't have printer rights.
> I am logged into my machine as a domain admin. I have no printing problems
> in any program to any printer, except when using Reporting Services.
>
> "Bruce L-C [MVP]" wrote:
> > I print exclusively to network printers. We do not have local printers at
> > work.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "msmolarek@.community.nospam"
> > <msmolarekcommunitynospam@.discussions.microsoft.com> wrote in message
> > news:5378230C-8CCE-43BE-9868-D1BC12940358@.microsoft.com...
> > > We are printing to network printers from IE.
> > >
> > > I hooked up a local printer to a computer just to try, and it prints the
> > > first page OK, and then pops up the same error message as usual:
> > > "0x80004005"
> > >
> > > Even if it worked on a local printer, this is supposed to be an enterprise
> > > solution. 99% of our employees print to network printers.
> > >
> > >
> > > "Floyd Burger" wrote:
> > >
> > >> Are you printing to a local or network printer? Printing from IE,
> > >> Firefox,
> > >> <insert other browser here>? I've had the best luck printing from IE to
> > >> a
> > >> local printer.
> > >>
> > >> --
> > >> Floyd
> > >>
> > >> "msmolarek@.community.nospam"
> > >> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
> > >> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> > >> > Hello,
> > >> >
> > >> > We have never been able to get the printing to work on any of our
> > >> > reports
> > >> > using SQL Server Reporting Services SP2.
> > >> >
> > >> > During the time we have been fighting to get this to work we had added
> > >> > on
> > >> > the SP, so we totally rebuilt the machine from scratch, that didn't
> > >> > help.
> > >> > In
> > >> > addition a couple of months ago we bought a totally new machine to host
> > >> > our
> > >> > reports and the fresh install on that machine didn't yeild any results.
> > >> >
> > >> > At some point I found some posts in the newsgroup about needing to
> > >> > uninstall
> > >> > an old ActiveX control used for printing, I did this and installed the
> > >> > new
> > >> > one but that didn't help either.
> > >> >
> > >> > We can print to things like the "Microsoft Office Document Image
> > >> > Writer"
> > >> > without problem, only when we try to print to a real printer does it
> > >> > bomb
> > >> > out.
> > >> >
> > >> > It doesn't matter how big the report is, 100 pages or 1/4 of a page,
> > >> > same
> > >> > problem.
> > >> >
> > >> > We do the following:
> > >> >
> > >> > Run the report
> > >> > Click the print button
> > >> > Select a printer and press ok
> > >> > "Printing Now..." dialog box appears
> > >> > "Print Error" dialog appears showing "An error occured during printing.
> > >> > (0x80004005). The misspelling of "occured" is how it is displayed in
> > >> > the
> > >> > message.
> > >> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> > >> > Error".
> > >> >
> > >> >
> > >> > This is the result on every computer we have ever used in trying to
> > >> > access
> > >> > the report server.
> > >> >
> > >> > Any help?
> > >>
> > >>
> > >>
> >
> >
> >