I get the following error when using the print button on the HTML view of a
report with reporting services 2005.
"An error occured during printing (0x8007F304)"
I have a windows application written in VS2003 .net 1.1 and it loads a
webcontrol to show and print the reports. I am using the URL syntax to view
the report. The report views ok, but when the user clicks the print button,
they get the error.
When I run the report via the report manager, I am able to print directly in
the browser.
Im running XP SP2.
The application I wrote is running under my windows credentials, And I have
rights to print to all the printers.
Also.. when I click print, the print dialog doesnt come up.. just get the
errorHi Sfboiler,
Welcome to MSDN newsgroup.
From your description, you use the IE WebBrowser control in your winform
application which navigate to a certain reporting service's report page and
let the winform app user print the report. However, you found that you'll
get an errro "An error occured during printing (0x8007F304)" when try
printing the reprot through the "printing" button on the page, but this
works well when we navigate the reprot through external IE window, yes?
Based on my local testing, seems a normal report can be printed correctly
both through the IE WebBrowser control and external IE window.... So this
problem is related to the specific envrionment or application. Since the
reporting service's reprot page's print button also use some script to
execute the print command, I'd suggest you also try directly using the
WebBrowser's print command to print the current document to see whether you
can correctly print it. e.g:
private void btnPrint_Click(object sender, System.EventArgs e)
{
mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
if(doc != null)
{
//doc.execCommand("Print", true, 0);
axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
OPT_PROMPTUSER);
}
}
If this also fails, I'm afraid there must have something incorrect with the
browser's script engine or else...
In addition, you can also check the reporting service's serverside log
(under ....\Reporting Services\LogFiles folder) to see whether there're
anything incorrectly for the reporter's generating....
If there're anything else found, please feel free to post here.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| Thread-Topic: An error occured during printing or An error occurred
during print
| thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==| X-WBNR-Posting-Host: 67.109.68.162
| From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
<sfboiler@.nospam.nospam>
| Subject: An error occured during printing or An error occurred during
print
| Date: Sun, 11 Dec 2005 08:55:02 -0800
| Lines: 20
| Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:64792
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| I get the following error when using the print button on the HTML view of
a
| report with reporting services 2005.
|
| "An error occured during printing (0x8007F304)"
|
| I have a windows application written in VS2003 .net 1.1 and it loads a
| webcontrol to show and print the reports. I am using the URL syntax to
view
| the report. The report views ok, but when the user clicks the print
button,
| they get the error.
|
| When I run the report via the report manager, I am able to print directly
in
| the browser.
|
| Im running XP SP2.
|
| The application I wrote is running under my windows credentials, And I
have
| rights to print to all the printers.
|
| Also.. when I click print, the print dialog doesnt come up.. just get the
| error
||||The error seem to be speficially with the print control.. In the same
application I am able to right click on the browser window and click print.
Everthing prints fine. But when I use the print button in the "Reporting
Services 2005" tool bar. I get the print error.
To reproduce this error..
1. create a report in RS 2005.
2. Create a windows Application in VS2003 .net framework 1.1 (I use c#)
3. Create a form that embeds the web broswer conrtol.
4. Call the navigate method to show the report in the browser
(Also I have the webserver set as local intranet site in security so that is
passes credentials automatically)
(Im also only showing the export / page / print toolbar)
5. click on the print icon on the report tool bar.
Thats where I get the error.
im usuing 2003 server with reporting services..
and XP sp2, IE 6.0.2900.2180
Bill
"Steven Cheng[MSFT]" wrote:
> Hi Sfboiler,
> Welcome to MSDN newsgroup.
> From your description, you use the IE WebBrowser control in your winform
> application which navigate to a certain reporting service's report page and
> let the winform app user print the report. However, you found that you'll
> get an errro "An error occured during printing (0x8007F304)" when try
> printing the reprot through the "printing" button on the page, but this
> works well when we navigate the reprot through external IE window, yes?
> Based on my local testing, seems a normal report can be printed correctly
> both through the IE WebBrowser control and external IE window.... So this
> problem is related to the specific envrionment or application. Since the
> reporting service's reprot page's print button also use some script to
> execute the print command, I'd suggest you also try directly using the
> WebBrowser's print command to print the current document to see whether you
> can correctly print it. e.g:
> private void btnPrint_Click(object sender, System.EventArgs e)
> {
> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
> if(doc != null)
> {
> //doc.execCommand("Print", true, 0);
> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
> OPT_PROMPTUSER);
> }
> }
>
> If this also fails, I'm afraid there must have something incorrect with the
> browser's script engine or else...
> In addition, you can also check the reporting service's serverside log
> (under ....\Reporting Services\LogFiles folder) to see whether there're
> anything incorrectly for the reporter's generating....
> If there're anything else found, please feel free to post here.
> Thanks,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> --
> | Thread-Topic: An error occured during printing or An error occurred
> during print
> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==> | X-WBNR-Posting-Host: 67.109.68.162
> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
> <sfboiler@.nospam.nospam>
> | Subject: An error occured during printing or An error occurred during
> print
> | Date: Sun, 11 Dec 2005 08:55:02 -0800
> | Lines: 20
> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:64792
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | I get the following error when using the print button on the HTML view of
> a
> | report with reporting services 2005.
> |
> | "An error occured during printing (0x8007F304)"
> |
> | I have a windows application written in VS2003 .net 1.1 and it loads a
> | webcontrol to show and print the reports. I am using the URL syntax to
> view
> | the report. The report views ok, but when the user clicks the print
> button,
> | they get the error.
> |
> | When I run the report via the report manager, I am able to print directly
> in
> | the browser.
> |
> | Im running XP SP2.
> |
> | The application I wrote is running under my windows credentials, And I
> have
> | rights to print to all the printers.
> |
> | Also.. when I click print, the print dialog doesnt come up.. just get the
> | error
> |
>|||The print control is not supported in a win forms hosted app. It also
sounds like you have a 2000 version of the print control. To get the 2005
version you will need to manually remove the ActiveX object. (Via
IE->Tools->Internet Option->Settings->View Objects). Then browse to RM and
click on the print icon again.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sfboiler@.nospam.nospam> wrote in message
news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> The error seem to be speficially with the print control.. In the same
> application I am able to right click on the browser window and click
> print.
> Everthing prints fine. But when I use the print button in the "Reporting
> Services 2005" tool bar. I get the print error.
> To reproduce this error..
> 1. create a report in RS 2005.
> 2. Create a windows Application in VS2003 .net framework 1.1 (I use c#)
> 3. Create a form that embeds the web broswer conrtol.
> 4. Call the navigate method to show the report in the browser
> (Also I have the webserver set as local intranet site in security so that
> is
> passes credentials automatically)
> (Im also only showing the export / page / print toolbar)
> 5. click on the print icon on the report tool bar.
> Thats where I get the error.
> im usuing 2003 server with reporting services..
> and XP sp2, IE 6.0.2900.2180
> Bill
> "Steven Cheng[MSFT]" wrote:
>> Hi Sfboiler,
>> Welcome to MSDN newsgroup.
>> From your description, you use the IE WebBrowser control in your winform
>> application which navigate to a certain reporting service's report page
>> and
>> let the winform app user print the report. However, you found that you'll
>> get an errro "An error occured during printing (0x8007F304)" when try
>> printing the reprot through the "printing" button on the page, but this
>> works well when we navigate the reprot through external IE window, yes?
>> Based on my local testing, seems a normal report can be printed correctly
>> both through the IE WebBrowser control and external IE window.... So
>> this
>> problem is related to the specific envrionment or application. Since the
>> reporting service's reprot page's print button also use some script to
>> execute the print command, I'd suggest you also try directly using the
>> WebBrowser's print command to print the current document to see whether
>> you
>> can correctly print it. e.g:
>> private void btnPrint_Click(object sender, System.EventArgs e)
>> {
>> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> if(doc != null)
>> {
>> //doc.execCommand("Print", true, 0);
>> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> OPT_PROMPTUSER);
>> }
>> }
>>
>> If this also fails, I'm afraid there must have something incorrect with
>> the
>> browser's script engine or else...
>> In addition, you can also check the reporting service's serverside log
>> (under ....\Reporting Services\LogFiles folder) to see whether there're
>> anything incorrectly for the reporter's generating....
>> If there're anything else found, please feel free to post here.
>> Thanks,
>> Steven Cheng
>> Microsoft Online Support
>> Get Secure! www.microsoft.com/security
>> (This posting is provided "AS IS", with no warranties, and confers no
>> rights.)
>>
>> --
>> | Thread-Topic: An error occured during printing or An error occurred
>> during print
>> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> | X-WBNR-Posting-Host: 67.109.68.162
>> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> <sfboiler@.nospam.nospam>
>> | Subject: An error occured during printing or An error occurred during
>> print
>> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> | Lines: 20
>> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> | MIME-Version: 1.0
>> | Content-Type: text/plain;
>> | charset="Utf-8"
>> | Content-Transfer-Encoding: 7bit
>> | X-Newsreader: Microsoft CDO for Windows 2000
>> | Content-Class: urn:content-classes:message
>> | Importance: normal
>> | Priority: normal
>> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> | Xref: TK2MSFTNGXA02.phx.gbl
>> microsoft.public.sqlserver.reportingsvcs:64792
>> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> |
>> | I get the following error when using the print button on the HTML view
>> of
>> a
>> | report with reporting services 2005.
>> |
>> | "An error occured during printing (0x8007F304)"
>> |
>> | I have a windows application written in VS2003 .net 1.1 and it loads a
>> | webcontrol to show and print the reports. I am using the URL syntax to
>> view
>> | the report. The report views ok, but when the user clicks the print
>> button,
>> | they get the error.
>> |
>> | When I run the report via the report manager, I am able to print
>> directly
>> in
>> | the browser.
>> |
>> | Im running XP SP2.
>> |
>> | The application I wrote is running under my windows credentials, And I
>> have
>> | rights to print to all the printers.
>> |
>> | Also.. when I click print, the print dialog doesnt come up.. just get
>> the
>> | error
>> |
>>|||I deleted and reinstalled the control..
Now I get this error:
"An error occured trying to get the current window"
"Daniel Reib [MSFT]" wrote:
> The print control is not supported in a win forms hosted app. It also
> sounds like you have a 2000 version of the print control. To get the 2005
> version you will need to manually remove the ActiveX object. (Via
> IE->Tools->Internet Option->Settings->View Objects). Then browse to RM and
> click on the print icon again.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <sfboiler@.nospam.nospam> wrote in message
> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> > The error seem to be speficially with the print control.. In the same
> > application I am able to right click on the browser window and click
> > print.
> > Everthing prints fine. But when I use the print button in the "Reporting
> > Services 2005" tool bar. I get the print error.
> >
> > To reproduce this error..
> > 1. create a report in RS 2005.
> > 2. Create a windows Application in VS2003 .net framework 1.1 (I use c#)
> > 3. Create a form that embeds the web broswer conrtol.
> > 4. Call the navigate method to show the report in the browser
> > (Also I have the webserver set as local intranet site in security so that
> > is
> > passes credentials automatically)
> >
> > (Im also only showing the export / page / print toolbar)
> >
> > 5. click on the print icon on the report tool bar.
> >
> > Thats where I get the error.
> >
> > im usuing 2003 server with reporting services..
> > and XP sp2, IE 6.0.2900.2180
> >
> > Bill
> >
> > "Steven Cheng[MSFT]" wrote:
> >
> >> Hi Sfboiler,
> >>
> >> Welcome to MSDN newsgroup.
> >> From your description, you use the IE WebBrowser control in your winform
> >> application which navigate to a certain reporting service's report page
> >> and
> >> let the winform app user print the report. However, you found that you'll
> >> get an errro "An error occured during printing (0x8007F304)" when try
> >> printing the reprot through the "printing" button on the page, but this
> >> works well when we navigate the reprot through external IE window, yes?
> >>
> >> Based on my local testing, seems a normal report can be printed correctly
> >> both through the IE WebBrowser control and external IE window.... So
> >> this
> >> problem is related to the specific envrionment or application. Since the
> >> reporting service's reprot page's print button also use some script to
> >> execute the print command, I'd suggest you also try directly using the
> >> WebBrowser's print command to print the current document to see whether
> >> you
> >> can correctly print it. e.g:
> >>
> >> private void btnPrint_Click(object sender, System.EventArgs e)
> >> {
> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
> >>
> >> if(doc != null)
> >> {
> >> //doc.execCommand("Print", true, 0);
> >>
> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
> >> OPT_PROMPTUSER);
> >> }
> >> }
> >>
> >>
> >> If this also fails, I'm afraid there must have something incorrect with
> >> the
> >> browser's script engine or else...
> >>
> >> In addition, you can also check the reporting service's serverside log
> >> (under ....\Reporting Services\LogFiles folder) to see whether there're
> >> anything incorrectly for the reporter's generating....
> >>
> >> If there're anything else found, please feel free to post here.
> >>
> >> Thanks,
> >>
> >> Steven Cheng
> >> Microsoft Online Support
> >>
> >> Get Secure! www.microsoft.com/security
> >> (This posting is provided "AS IS", with no warranties, and confers no
> >> rights.)
> >>
> >>
> >> --
> >> | Thread-Topic: An error occured during printing or An error occurred
> >> during print
> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==> >> | X-WBNR-Posting-Host: 67.109.68.162
> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
> >> <sfboiler@.nospam.nospam>
> >> | Subject: An error occured during printing or An error occurred during
> >> print
> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
> >> | Lines: 20
> >> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
> >> | MIME-Version: 1.0
> >> | Content-Type: text/plain;
> >> | charset="Utf-8"
> >> | Content-Transfer-Encoding: 7bit
> >> | X-Newsreader: Microsoft CDO for Windows 2000
> >> | Content-Class: urn:content-classes:message
> >> | Importance: normal
> >> | Priority: normal
> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> | Xref: TK2MSFTNGXA02.phx.gbl
> >> microsoft.public.sqlserver.reportingsvcs:64792
> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> |
> >> | I get the following error when using the print button on the HTML view
> >> of
> >> a
> >> | report with reporting services 2005.
> >> |
> >> | "An error occured during printing (0x8007F304)"
> >> |
> >> | I have a windows application written in VS2003 .net 1.1 and it loads a
> >> | webcontrol to show and print the reports. I am using the URL syntax to
> >> view
> >> | the report. The report views ok, but when the user clicks the print
> >> button,
> >> | they get the error.
> >> |
> >> | When I run the report via the report manager, I am able to print
> >> directly
> >> in
> >> | the browser.
> >> |
> >> | Im running XP SP2.
> >> |
> >> | The application I wrote is running under my windows credentials, And I
> >> have
> >> | rights to print to all the printers.
> >> |
> >> | Also.. when I click print, the print dialog doesnt come up.. just get
> >> the
> >> | error
> >> |
> >>
> >>
>
>|||That is correct. You are using the control in a Web Form app which hosts IE.
This is not a supported scenario. The print control will not open because
it can not find a handle to the current window.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sfboiler@.nospam.nospam> wrote in message
news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>I deleted and reinstalled the control..
> Now I get this error:
> "An error occured trying to get the current window"
>
> "Daniel Reib [MSFT]" wrote:
>> The print control is not supported in a win forms hosted app. It also
>> sounds like you have a 2000 version of the print control. To get the
>> 2005
>> version you will need to manually remove the ActiveX object. (Via
>> IE->Tools->Internet Option->Settings->View Objects). Then browse to RM
>> and
>> click on the print icon again.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> > The error seem to be speficially with the print control.. In the same
>> > application I am able to right click on the browser window and click
>> > print.
>> > Everthing prints fine. But when I use the print button in the
>> > "Reporting
>> > Services 2005" tool bar. I get the print error.
>> >
>> > To reproduce this error..
>> > 1. create a report in RS 2005.
>> > 2. Create a windows Application in VS2003 .net framework 1.1 (I use c#)
>> > 3. Create a form that embeds the web broswer conrtol.
>> > 4. Call the navigate method to show the report in the browser
>> > (Also I have the webserver set as local intranet site in security so
>> > that
>> > is
>> > passes credentials automatically)
>> >
>> > (Im also only showing the export / page / print toolbar)
>> >
>> > 5. click on the print icon on the report tool bar.
>> >
>> > Thats where I get the error.
>> >
>> > im usuing 2003 server with reporting services..
>> > and XP sp2, IE 6.0.2900.2180
>> >
>> > Bill
>> >
>> > "Steven Cheng[MSFT]" wrote:
>> >
>> >> Hi Sfboiler,
>> >>
>> >> Welcome to MSDN newsgroup.
>> >> From your description, you use the IE WebBrowser control in your
>> >> winform
>> >> application which navigate to a certain reporting service's report
>> >> page
>> >> and
>> >> let the winform app user print the report. However, you found that
>> >> you'll
>> >> get an errro "An error occured during printing (0x8007F304)" when try
>> >> printing the reprot through the "printing" button on the page, but
>> >> this
>> >> works well when we navigate the reprot through external IE window,
>> >> yes?
>> >>
>> >> Based on my local testing, seems a normal report can be printed
>> >> correctly
>> >> both through the IE WebBrowser control and external IE window.... So
>> >> this
>> >> problem is related to the specific envrionment or application. Since
>> >> the
>> >> reporting service's reprot page's print button also use some script to
>> >> execute the print command, I'd suggest you also try directly using the
>> >> WebBrowser's print command to print the current document to see
>> >> whether
>> >> you
>> >> can correctly print it. e.g:
>> >>
>> >> private void btnPrint_Click(object sender, System.EventArgs e)
>> >> {
>> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> >>
>> >> if(doc != null)
>> >> {
>> >> //doc.execCommand("Print", true, 0);
>> >>
>> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> OPT_PROMPTUSER);
>> >> }
>> >> }
>> >>
>> >>
>> >> If this also fails, I'm afraid there must have something incorrect
>> >> with
>> >> the
>> >> browser's script engine or else...
>> >>
>> >> In addition, you can also check the reporting service's serverside log
>> >> (under ....\Reporting Services\LogFiles folder) to see whether
>> >> there're
>> >> anything incorrectly for the reporter's generating....
>> >>
>> >> If there're anything else found, please feel free to post here.
>> >>
>> >> Thanks,
>> >>
>> >> Steven Cheng
>> >> Microsoft Online Support
>> >>
>> >> Get Secure! www.microsoft.com/security
>> >> (This posting is provided "AS IS", with no warranties, and confers no
>> >> rights.)
>> >>
>> >>
>> >> --
>> >> | Thread-Topic: An error occured during printing or An error occurred
>> >> during print
>> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >> <sfboiler@.nospam.nospam>
>> >> | Subject: An error occured during printing or An error occurred
>> >> during
>> >> print
>> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >> | Lines: 20
>> >> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >> | MIME-Version: 1.0
>> >> | Content-Type: text/plain;
>> >> | charset="Utf-8"
>> >> | Content-Transfer-Encoding: 7bit
>> >> | X-Newsreader: Microsoft CDO for Windows 2000
>> >> | Content-Class: urn:content-classes:message
>> >> | Importance: normal
>> >> | Priority: normal
>> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >> | Xref: TK2MSFTNGXA02.phx.gbl
>> >> microsoft.public.sqlserver.reportingsvcs:64792
>> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> |
>> >> | I get the following error when using the print button on the HTML
>> >> view
>> >> of
>> >> a
>> >> | report with reporting services 2005.
>> >> |
>> >> | "An error occured during printing (0x8007F304)"
>> >> |
>> >> | I have a windows application written in VS2003 .net 1.1 and it loads
>> >> a
>> >> | webcontrol to show and print the reports. I am using the URL syntax
>> >> to
>> >> view
>> >> | the report. The report views ok, but when the user clicks the print
>> >> button,
>> >> | they get the error.
>> >> |
>> >> | When I run the report via the report manager, I am able to print
>> >> directly
>> >> in
>> >> | the browser.
>> >> |
>> >> | Im running XP SP2.
>> >> |
>> >> | The application I wrote is running under my windows credentials, And
>> >> I
>> >> have
>> >> | rights to print to all the printers.
>> >> |
>> >> | Also.. when I click print, the print dialog doesnt come up.. just
>> >> get
>> >> the
>> >> | error
>> >> |
>> >>
>> >>
>>|||So.. How do I fix it?
The whole reason we are using reporting services is because a microsoft
consultant (Chris Jackson) told us we could imbed it into our application and
that it would work.
Bill
"Daniel Reib [MSFT]" wrote:
> That is correct. You are using the control in a Web Form app which hosts IE.
> This is not a supported scenario. The print control will not open because
> it can not find a handle to the current window.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <sfboiler@.nospam.nospam> wrote in message
> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
> >I deleted and reinstalled the control..
> >
> > Now I get this error:
> >
> > "An error occured trying to get the current window"
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> >> The print control is not supported in a win forms hosted app. It also
> >> sounds like you have a 2000 version of the print control. To get the
> >> 2005
> >> version you will need to manually remove the ActiveX object. (Via
> >> IE->Tools->Internet Option->Settings->View Objects). Then browse to RM
> >> and
> >> click on the print icon again.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> <sfboiler@.nospam.nospam> wrote in message
> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> >> > The error seem to be speficially with the print control.. In the same
> >> > application I am able to right click on the browser window and click
> >> > print.
> >> > Everthing prints fine. But when I use the print button in the
> >> > "Reporting
> >> > Services 2005" tool bar. I get the print error.
> >> >
> >> > To reproduce this error..
> >> > 1. create a report in RS 2005.
> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I use c#)
> >> > 3. Create a form that embeds the web broswer conrtol.
> >> > 4. Call the navigate method to show the report in the browser
> >> > (Also I have the webserver set as local intranet site in security so
> >> > that
> >> > is
> >> > passes credentials automatically)
> >> >
> >> > (Im also only showing the export / page / print toolbar)
> >> >
> >> > 5. click on the print icon on the report tool bar.
> >> >
> >> > Thats where I get the error.
> >> >
> >> > im usuing 2003 server with reporting services..
> >> > and XP sp2, IE 6.0.2900.2180
> >> >
> >> > Bill
> >> >
> >> > "Steven Cheng[MSFT]" wrote:
> >> >
> >> >> Hi Sfboiler,
> >> >>
> >> >> Welcome to MSDN newsgroup.
> >> >> From your description, you use the IE WebBrowser control in your
> >> >> winform
> >> >> application which navigate to a certain reporting service's report
> >> >> page
> >> >> and
> >> >> let the winform app user print the report. However, you found that
> >> >> you'll
> >> >> get an errro "An error occured during printing (0x8007F304)" when try
> >> >> printing the reprot through the "printing" button on the page, but
> >> >> this
> >> >> works well when we navigate the reprot through external IE window,
> >> >> yes?
> >> >>
> >> >> Based on my local testing, seems a normal report can be printed
> >> >> correctly
> >> >> both through the IE WebBrowser control and external IE window.... So
> >> >> this
> >> >> problem is related to the specific envrionment or application. Since
> >> >> the
> >> >> reporting service's reprot page's print button also use some script to
> >> >> execute the print command, I'd suggest you also try directly using the
> >> >> WebBrowser's print command to print the current document to see
> >> >> whether
> >> >> you
> >> >> can correctly print it. e.g:
> >> >>
> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
> >> >> {
> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
> >> >>
> >> >> if(doc != null)
> >> >> {
> >> >> //doc.execCommand("Print", true, 0);
> >> >>
> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
> >> >> OPT_PROMPTUSER);
> >> >> }
> >> >> }
> >> >>
> >> >>
> >> >> If this also fails, I'm afraid there must have something incorrect
> >> >> with
> >> >> the
> >> >> browser's script engine or else...
> >> >>
> >> >> In addition, you can also check the reporting service's serverside log
> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
> >> >> there're
> >> >> anything incorrectly for the reporter's generating....
> >> >>
> >> >> If there're anything else found, please feel free to post here.
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Steven Cheng
> >> >> Microsoft Online Support
> >> >>
> >> >> Get Secure! www.microsoft.com/security
> >> >> (This posting is provided "AS IS", with no warranties, and confers no
> >> >> rights.)
> >> >>
> >> >>
> >> >> --
> >> >> | Thread-Topic: An error occured during printing or An error occurred
> >> >> during print
> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==> >> >> | X-WBNR-Posting-Host: 67.109.68.162
> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
> >> >> <sfboiler@.nospam.nospam>
> >> >> | Subject: An error occured during printing or An error occurred
> >> >> during
> >> >> print
> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
> >> >> | Lines: 20
> >> >> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
> >> >> | MIME-Version: 1.0
> >> >> | Content-Type: text/plain;
> >> >> | charset="Utf-8"
> >> >> | Content-Transfer-Encoding: 7bit
> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
> >> >> | Content-Class: urn:content-classes:message
> >> >> | Importance: normal
> >> >> | Priority: normal
> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
> >> >> microsoft.public.sqlserver.reportingsvcs:64792
> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >> |
> >> >> | I get the following error when using the print button on the HTML
> >> >> view
> >> >> of
> >> >> a
> >> >> | report with reporting services 2005.
> >> >> |
> >> >> | "An error occured during printing (0x8007F304)"
> >> >> |
> >> >> | I have a windows application written in VS2003 .net 1.1 and it loads
> >> >> a
> >> >> | webcontrol to show and print the reports. I am using the URL syntax
> >> >> to
> >> >> view
> >> >> | the report. The report views ok, but when the user clicks the print
> >> >> button,
> >> >> | they get the error.
> >> >> |
> >> >> | When I run the report via the report manager, I am able to print
> >> >> directly
> >> >> in
> >> >> | the browser.
> >> >> |
> >> >> | Im running XP SP2.
> >> >> |
> >> >> | The application I wrote is running under my windows credentials, And
> >> >> I
> >> >> have
> >> >> | rights to print to all the printers.
> >> >> |
> >> >> | Also.. when I click print, the print dialog doesnt come up.. just
> >> >> get
> >> >> the
> >> >> | error
> >> >> |
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:uTG6ks0$FHA.3136@.TK2MSFTNGP15.phx.gbl...
> That is correct. You are using the control in a Web Form app which hosts
> IE. This is not a supported scenario. The print control will not open
> because it can not find a handle to the current window.
> --
What'! Are you actually saying that trying to print a report from the
ReportServer created web application is not a "supported scenario"'!!!!
How exactly *are* we supposed to print these reports?
Very confused,
Mike|||I might be mistaken but I think the issue here is how it is being done. If
you use the new controls that come with VS 2005 you will get the full
functionality. I haven't used the web control but I have used the new
winform control and the printing functionality is there. If you read the
first post there is URL integration going on. The new controls use web
services which eliminates a lot of the problems.
The new controls have a whole lot of functionality and provide much better
integration with a lot less effort than was possible before.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:umDqU72$FHA.3800@.TK2MSFTNGP10.phx.gbl...
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:uTG6ks0$FHA.3136@.TK2MSFTNGP15.phx.gbl...
>> That is correct. You are using the control in a Web Form app which hosts
>> IE. This is not a supported scenario. The print control will not open
>> because it can not find a handle to the current window.
>> --
> What'! Are you actually saying that trying to print a report from the
> ReportServer created web application is not a "supported scenario"'!!!!
> How exactly *are* we supposed to print these reports?
> Very confused,
> Mike
>|||Unfortunately the print control had limitations which forced us to not be
able to support this scenario. You can use the new RS 2005 controls which
were designed to be embedded in applications. They do, however, require
that you use RS 2005.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sfboiler@.nospam.nospam> wrote in message
news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
> So.. How do I fix it?
> The whole reason we are using reporting services is because a microsoft
> consultant (Chris Jackson) told us we could imbed it into our application
> and
> that it would work.
> Bill
> "Daniel Reib [MSFT]" wrote:
>> That is correct. You are using the control in a Web Form app which hosts
>> IE.
>> This is not a supported scenario. The print control will not open
>> because
>> it can not find a handle to the current window.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >I deleted and reinstalled the control..
>> >
>> > Now I get this error:
>> >
>> > "An error occured trying to get the current window"
>> >
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> The print control is not supported in a win forms hosted app. It also
>> >> sounds like you have a 2000 version of the print control. To get the
>> >> 2005
>> >> version you will need to manually remove the ActiveX object. (Via
>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse to
>> >> RM
>> >> and
>> >> click on the print icon again.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> > The error seem to be speficially with the print control.. In the
>> >> > same
>> >> > application I am able to right click on the browser window and click
>> >> > print.
>> >> > Everthing prints fine. But when I use the print button in the
>> >> > "Reporting
>> >> > Services 2005" tool bar. I get the print error.
>> >> >
>> >> > To reproduce this error..
>> >> > 1. create a report in RS 2005.
>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I use
>> >> > c#)
>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> > 4. Call the navigate method to show the report in the browser
>> >> > (Also I have the webserver set as local intranet site in security so
>> >> > that
>> >> > is
>> >> > passes credentials automatically)
>> >> >
>> >> > (Im also only showing the export / page / print toolbar)
>> >> >
>> >> > 5. click on the print icon on the report tool bar.
>> >> >
>> >> > Thats where I get the error.
>> >> >
>> >> > im usuing 2003 server with reporting services..
>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >
>> >> > Bill
>> >> >
>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >
>> >> >> Hi Sfboiler,
>> >> >>
>> >> >> Welcome to MSDN newsgroup.
>> >> >> From your description, you use the IE WebBrowser control in your
>> >> >> winform
>> >> >> application which navigate to a certain reporting service's report
>> >> >> page
>> >> >> and
>> >> >> let the winform app user print the report. However, you found that
>> >> >> you'll
>> >> >> get an errro "An error occured during printing (0x8007F304)" when
>> >> >> try
>> >> >> printing the reprot through the "printing" button on the page, but
>> >> >> this
>> >> >> works well when we navigate the reprot through external IE window,
>> >> >> yes?
>> >> >>
>> >> >> Based on my local testing, seems a normal report can be printed
>> >> >> correctly
>> >> >> both through the IE WebBrowser control and external IE window....
>> >> >> So
>> >> >> this
>> >> >> problem is related to the specific envrionment or application.
>> >> >> Since
>> >> >> the
>> >> >> reporting service's reprot page's print button also use some script
>> >> >> to
>> >> >> execute the print command, I'd suggest you also try directly using
>> >> >> the
>> >> >> WebBrowser's print command to print the current document to see
>> >> >> whether
>> >> >> you
>> >> >> can correctly print it. e.g:
>> >> >>
>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
>> >> >> {
>> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> >> >>
>> >> >> if(doc != null)
>> >> >> {
>> >> >> //doc.execCommand("Print", true, 0);
>> >> >>
>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> >> OPT_PROMPTUSER);
>> >> >> }
>> >> >> }
>> >> >>
>> >> >>
>> >> >> If this also fails, I'm afraid there must have something incorrect
>> >> >> with
>> >> >> the
>> >> >> browser's script engine or else...
>> >> >>
>> >> >> In addition, you can also check the reporting service's serverside
>> >> >> log
>> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
>> >> >> there're
>> >> >> anything incorrectly for the reporter's generating....
>> >> >>
>> >> >> If there're anything else found, please feel free to post here.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Steven Cheng
>> >> >> Microsoft Online Support
>> >> >>
>> >> >> Get Secure! www.microsoft.com/security
>> >> >> (This posting is provided "AS IS", with no warranties, and confers
>> >> >> no
>> >> >> rights.)
>> >> >>
>> >> >>
>> >> >> --
>> >> >> | Thread-Topic: An error occured during printing or An error
>> >> >> occurred
>> >> >> during print
>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >> >> <sfboiler@.nospam.nospam>
>> >> >> | Subject: An error occured during printing or An error occurred
>> >> >> during
>> >> >> print
>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >> >> | Lines: 20
>> >> >> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >> >> | MIME-Version: 1.0
>> >> >> | Content-Type: text/plain;
>> >> >> | charset="Utf-8"
>> >> >> | Content-Transfer-Encoding: 7bit
>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> | Content-Class: urn:content-classes:message
>> >> >> | Importance: normal
>> >> >> | Priority: normal
>> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
>> >> >> microsoft.public.sqlserver.reportingsvcs:64792
>> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> |
>> >> >> | I get the following error when using the print button on the HTML
>> >> >> view
>> >> >> of
>> >> >> a
>> >> >> | report with reporting services 2005.
>> >> >> |
>> >> >> | "An error occured during printing (0x8007F304)"
>> >> >> |
>> >> >> | I have a windows application written in VS2003 .net 1.1 and it
>> >> >> loads
>> >> >> a
>> >> >> | webcontrol to show and print the reports. I am using the URL
>> >> >> syntax
>> >> >> to
>> >> >> view
>> >> >> | the report. The report views ok, but when the user clicks the
>> >> >> print
>> >> >> button,
>> >> >> | they get the error.
>> >> >> |
>> >> >> | When I run the report via the report manager, I am able to print
>> >> >> directly
>> >> >> in
>> >> >> | the browser.
>> >> >> |
>> >> >> | Im running XP SP2.
>> >> >> |
>> >> >> | The application I wrote is running under my windows credentials,
>> >> >> And
>> >> >> I
>> >> >> have
>> >> >> | rights to print to all the printers.
>> >> >> |
>> >> >> | Also.. when I click print, the print dialog doesnt come up.. just
>> >> >> get
>> >> >> the
>> >> >> | error
>> >> >> |
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||I'm using RS 2005 and I still get the "cannot get window handle" message in
the IE toolbar created by ReportServer.
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
> Unfortunately the print control had limitations which forced us to not be
> able to support this scenario. You can use the new RS 2005 controls which
> were designed to be embedded in applications. They do, however, require
> that you use RS 2005.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> <sfboiler@.nospam.nospam> wrote in message
> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> So.. How do I fix it?
>> The whole reason we are using reporting services is because a microsoft
>> consultant (Chris Jackson) told us we could imbed it into our application
>> and
>> that it would work.
>> Bill
>> "Daniel Reib [MSFT]" wrote:
>> That is correct. You are using the control in a Web Form app which hosts
>> IE.
>> This is not a supported scenario. The print control will not open
>> because
>> it can not find a handle to the current window.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >I deleted and reinstalled the control..
>> >
>> > Now I get this error:
>> >
>> > "An error occured trying to get the current window"
>> >
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> The print control is not supported in a win forms hosted app. It
>> >> also
>> >> sounds like you have a 2000 version of the print control. To get the
>> >> 2005
>> >> version you will need to manually remove the ActiveX object. (Via
>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse to
>> >> RM
>> >> and
>> >> click on the print icon again.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> > The error seem to be speficially with the print control.. In the
>> >> > same
>> >> > application I am able to right click on the browser window and
>> >> > click
>> >> > print.
>> >> > Everthing prints fine. But when I use the print button in the
>> >> > "Reporting
>> >> > Services 2005" tool bar. I get the print error.
>> >> >
>> >> > To reproduce this error..
>> >> > 1. create a report in RS 2005.
>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I use
>> >> > c#)
>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> > 4. Call the navigate method to show the report in the browser
>> >> > (Also I have the webserver set as local intranet site in security
>> >> > so
>> >> > that
>> >> > is
>> >> > passes credentials automatically)
>> >> >
>> >> > (Im also only showing the export / page / print toolbar)
>> >> >
>> >> > 5. click on the print icon on the report tool bar.
>> >> >
>> >> > Thats where I get the error.
>> >> >
>> >> > im usuing 2003 server with reporting services..
>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >
>> >> > Bill
>> >> >
>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >
>> >> >> Hi Sfboiler,
>> >> >>
>> >> >> Welcome to MSDN newsgroup.
>> >> >> From your description, you use the IE WebBrowser control in your
>> >> >> winform
>> >> >> application which navigate to a certain reporting service's report
>> >> >> page
>> >> >> and
>> >> >> let the winform app user print the report. However, you found that
>> >> >> you'll
>> >> >> get an errro "An error occured during printing (0x8007F304)" when
>> >> >> try
>> >> >> printing the reprot through the "printing" button on the page, but
>> >> >> this
>> >> >> works well when we navigate the reprot through external IE window,
>> >> >> yes?
>> >> >>
>> >> >> Based on my local testing, seems a normal report can be printed
>> >> >> correctly
>> >> >> both through the IE WebBrowser control and external IE window....
>> >> >> So
>> >> >> this
>> >> >> problem is related to the specific envrionment or application.
>> >> >> Since
>> >> >> the
>> >> >> reporting service's reprot page's print button also use some
>> >> >> script to
>> >> >> execute the print command, I'd suggest you also try directly using
>> >> >> the
>> >> >> WebBrowser's print command to print the current document to see
>> >> >> whether
>> >> >> you
>> >> >> can correctly print it. e.g:
>> >> >>
>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
>> >> >> {
>> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> >> >>
>> >> >> if(doc != null)
>> >> >> {
>> >> >> //doc.execCommand("Print", true, 0);
>> >> >>
>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> >> OPT_PROMPTUSER);
>> >> >> }
>> >> >> }
>> >> >>
>> >> >>
>> >> >> If this also fails, I'm afraid there must have something incorrect
>> >> >> with
>> >> >> the
>> >> >> browser's script engine or else...
>> >> >>
>> >> >> In addition, you can also check the reporting service's serverside
>> >> >> log
>> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
>> >> >> there're
>> >> >> anything incorrectly for the reporter's generating....
>> >> >>
>> >> >> If there're anything else found, please feel free to post here.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Steven Cheng
>> >> >> Microsoft Online Support
>> >> >>
>> >> >> Get Secure! www.microsoft.com/security
>> >> >> (This posting is provided "AS IS", with no warranties, and confers
>> >> >> no
>> >> >> rights.)
>> >> >>
>> >> >>
>> >> >> --
>> >> >> | Thread-Topic: An error occured during printing or An error
>> >> >> occurred
>> >> >> during print
>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >> >> <sfboiler@.nospam.nospam>
>> >> >> | Subject: An error occured during printing or An error occurred
>> >> >> during
>> >> >> print
>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >> >> | Lines: 20
>> >> >> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >> >> | MIME-Version: 1.0
>> >> >> | Content-Type: text/plain;
>> >> >> | charset="Utf-8"
>> >> >> | Content-Transfer-Encoding: 7bit
>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> | Content-Class: urn:content-classes:message
>> >> >> | Importance: normal
>> >> >> | Priority: normal
>> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
>> >> >> microsoft.public.sqlserver.reportingsvcs:64792
>> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> |
>> >> >> | I get the following error when using the print button on the
>> >> >> HTML
>> >> >> view
>> >> >> of
>> >> >> a
>> >> >> | report with reporting services 2005.
>> >> >> |
>> >> >> | "An error occured during printing (0x8007F304)"
>> >> >> |
>> >> >> | I have a windows application written in VS2003 .net 1.1 and it
>> >> >> loads
>> >> >> a
>> >> >> | webcontrol to show and print the reports. I am using the URL
>> >> >> syntax
>> >> >> to
>> >> >> view
>> >> >> | the report. The report views ok, but when the user clicks the
>> >> >> print
>> >> >> button,
>> >> >> | they get the error.
>> >> >> |
>> >> >> | When I run the report via the report manager, I am able to print
>> >> >> directly
>> >> >> in
>> >> >> | the browser.
>> >> >> |
>> >> >> | Im running XP SP2.
>> >> >> |
>> >> >> | The application I wrote is running under my windows credentials,
>> >> >> And
>> >> >> I
>> >> >> have
>> >> >> | rights to print to all the printers.
>> >> >> |
>> >> >> | Also.. when I click print, the print dialog doesnt come up..
>> >> >> just
>> >> >> get
>> >> >> the
>> >> >> | error
>> >> >> |
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>|||I am usuing Visual Studio 2003 (.net 1.1) with Reporting Services 2005. I am
not able to ugrade my application at this time. It is very large and years
in development. we currently have 36mb of souce code and are close to being
ready for deployment. Ugrading to Visual Studio 2005 is not an option at the
moment.
How can this not be supported? Everything I am usuing in Microsoft.
Visual Studio .. Microsoft
Windows XP .. Microsoft
Interenet Explorer .. Microsoft
SQL Server .. Microsoft
Reporting Services .. Microsoft
Its seems to me there is a problem with the ReportingServices print dll.
What good is a reporting tool.. if you cant print?
Bill
"Bruce L-C [MVP]" wrote:
> I might be mistaken but I think the issue here is how it is being done. If
> you use the new controls that come with VS 2005 you will get the full
> functionality. I haven't used the web control but I have used the new
> winform control and the printing functionality is there. If you read the
> first post there is URL integration going on. The new controls use web
> services which eliminates a lot of the problems.
> The new controls have a whole lot of functionality and provide much better
> integration with a lot less effort than was possible before.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:umDqU72$FHA.3800@.TK2MSFTNGP10.phx.gbl...
> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> > news:uTG6ks0$FHA.3136@.TK2MSFTNGP15.phx.gbl...
> >> That is correct. You are using the control in a Web Form app which hosts
> >> IE. This is not a supported scenario. The print control will not open
> >> because it can not find a handle to the current window.
> >>
> >> --
> >
> > What'! Are you actually saying that trying to print a report from the
> > ReportServer created web application is not a "supported scenario"'!!!!
> > How exactly *are* we supposed to print these reports?
> >
> > Very confused,
> >
> > Mike
> >
> >
>
>|||If you are using RS 2005 then you have at least some of your web site using
framework 2.0 (since it is a framework 2.0 app). Can you leave most of your
app at 1.1 and just have a page with the new control in 2.0? As I said, I
don't know how feasible it is.
The ability to tightly integrate has improved greatly between versions. RS
2005 offers much better integration with the new controls. Because of your
situation it sounds like that is not an option for you at this time. There
are ways around it but nothing is that easy (render to a file on the server
and print that, etc).
It wasn't until SP2 that there was any printing. Previously my users had to
export to PDF and then print. That is still an option.
URL integration has some strong points, web services has it's strong points.
You seem to have hit an issue with URL integration. If there is any way to
use the new controls that would be the best solution.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<sfboiler@.nospam.nospam> wrote in message
news:2E4460ED-0983-4BD4-856B-CF78A875A615@.microsoft.com...
>I am usuing Visual Studio 2003 (.net 1.1) with Reporting Services 2005. I
>am
> not able to ugrade my application at this time. It is very large and
> years
> in development. we currently have 36mb of souce code and are close to
> being
> ready for deployment. Ugrading to Visual Studio 2005 is not an option at
> the
> moment.
> How can this not be supported? Everything I am usuing in Microsoft.
> Visual Studio .. Microsoft
> Windows XP .. Microsoft
> Interenet Explorer .. Microsoft
> SQL Server .. Microsoft
> Reporting Services .. Microsoft
> Its seems to me there is a problem with the ReportingServices print dll.
> What good is a reporting tool.. if you cant print?
> Bill
>
> "Bruce L-C [MVP]" wrote:
>> I might be mistaken but I think the issue here is how it is being done.
>> If
>> you use the new controls that come with VS 2005 you will get the full
>> functionality. I haven't used the web control but I have used the new
>> winform control and the printing functionality is there. If you read the
>> first post there is URL integration going on. The new controls use web
>> services which eliminates a lot of the problems.
>> The new controls have a whole lot of functionality and provide much
>> better
>> integration with a lot less effort than was possible before.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:umDqU72$FHA.3800@.TK2MSFTNGP10.phx.gbl...
>> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> > news:uTG6ks0$FHA.3136@.TK2MSFTNGP15.phx.gbl...
>> >> That is correct. You are using the control in a Web Form app which
>> >> hosts
>> >> IE. This is not a supported scenario. The print control will not open
>> >> because it can not find a handle to the current window.
>> >>
>> >> --
>> >
>> > What'! Are you actually saying that trying to print a report from the
>> > ReportServer created web application is not a "supported
>> > scenario"'!!!!
>> > How exactly *are* we supposed to print these reports?
>> >
>> > Very confused,
>> >
>> > Mike
>> >
>> >
>>|||Yes, the IE print control is not supported in hosted winform app. If you
are writing a winform app you should use the report server winform control.
Using this control will allow you to integrate report viewing with printing
into your app.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
> I'm using RS 2005 and I still get the "cannot get window handle" message
> in the IE toolbar created by ReportServer.
>
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> Unfortunately the print control had limitations which forced us to not be
>> able to support this scenario. You can use the new RS 2005 controls
>> which were designed to be embedded in applications. They do, however,
>> require that you use RS 2005.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> So.. How do I fix it?
>> The whole reason we are using reporting services is because a microsoft
>> consultant (Chris Jackson) told us we could imbed it into our
>> application and
>> that it would work.
>> Bill
>> "Daniel Reib [MSFT]" wrote:
>> That is correct. You are using the control in a Web Form app which
>> hosts IE.
>> This is not a supported scenario. The print control will not open
>> because
>> it can not find a handle to the current window.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >I deleted and reinstalled the control..
>> >
>> > Now I get this error:
>> >
>> > "An error occured trying to get the current window"
>> >
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> The print control is not supported in a win forms hosted app. It
>> >> also
>> >> sounds like you have a 2000 version of the print control. To get
>> >> the
>> >> 2005
>> >> version you will need to manually remove the ActiveX object. (Via
>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse to
>> >> RM
>> >> and
>> >> click on the print icon again.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> > The error seem to be speficially with the print control.. In the
>> >> > same
>> >> > application I am able to right click on the browser window and
>> >> > click
>> >> > print.
>> >> > Everthing prints fine. But when I use the print button in the
>> >> > "Reporting
>> >> > Services 2005" tool bar. I get the print error.
>> >> >
>> >> > To reproduce this error..
>> >> > 1. create a report in RS 2005.
>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I
>> >> > use c#)
>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> > 4. Call the navigate method to show the report in the browser
>> >> > (Also I have the webserver set as local intranet site in security
>> >> > so
>> >> > that
>> >> > is
>> >> > passes credentials automatically)
>> >> >
>> >> > (Im also only showing the export / page / print toolbar)
>> >> >
>> >> > 5. click on the print icon on the report tool bar.
>> >> >
>> >> > Thats where I get the error.
>> >> >
>> >> > im usuing 2003 server with reporting services..
>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >
>> >> > Bill
>> >> >
>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >
>> >> >> Hi Sfboiler,
>> >> >>
>> >> >> Welcome to MSDN newsgroup.
>> >> >> From your description, you use the IE WebBrowser control in your
>> >> >> winform
>> >> >> application which navigate to a certain reporting service's
>> >> >> report
>> >> >> page
>> >> >> and
>> >> >> let the winform app user print the report. However, you found
>> >> >> that
>> >> >> you'll
>> >> >> get an errro "An error occured during printing (0x8007F304)" when
>> >> >> try
>> >> >> printing the reprot through the "printing" button on the page,
>> >> >> but
>> >> >> this
>> >> >> works well when we navigate the reprot through external IE
>> >> >> window,
>> >> >> yes?
>> >> >>
>> >> >> Based on my local testing, seems a normal report can be printed
>> >> >> correctly
>> >> >> both through the IE WebBrowser control and external IE
>> >> >> window.... So
>> >> >> this
>> >> >> problem is related to the specific envrionment or application.
>> >> >> Since
>> >> >> the
>> >> >> reporting service's reprot page's print button also use some
>> >> >> script to
>> >> >> execute the print command, I'd suggest you also try directly
>> >> >> using the
>> >> >> WebBrowser's print command to print the current document to see
>> >> >> whether
>> >> >> you
>> >> >> can correctly print it. e.g:
>> >> >>
>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
>> >> >> {
>> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> >> >>
>> >> >> if(doc != null)
>> >> >> {
>> >> >> //doc.execCommand("Print", true, 0);
>> >> >>
>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> >> OPT_PROMPTUSER);
>> >> >> }
>> >> >> }
>> >> >>
>> >> >>
>> >> >> If this also fails, I'm afraid there must have something
>> >> >> incorrect
>> >> >> with
>> >> >> the
>> >> >> browser's script engine or else...
>> >> >>
>> >> >> In addition, you can also check the reporting service's
>> >> >> serverside log
>> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
>> >> >> there're
>> >> >> anything incorrectly for the reporter's generating....
>> >> >>
>> >> >> If there're anything else found, please feel free to post here.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Steven Cheng
>> >> >> Microsoft Online Support
>> >> >>
>> >> >> Get Secure! www.microsoft.com/security
>> >> >> (This posting is provided "AS IS", with no warranties, and
>> >> >> confers no
>> >> >> rights.)
>> >> >>
>> >> >>
>> >> >> --
>> >> >> | Thread-Topic: An error occured during printing or An error
>> >> >> occurred
>> >> >> during print
>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >> >> <sfboiler@.nospam.nospam>
>> >> >> | Subject: An error occured during printing or An error occurred
>> >> >> during
>> >> >> print
>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >> >> | Lines: 20
>> >> >> | Message-ID:
>> >> >> <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >> >> | MIME-Version: 1.0
>> >> >> | Content-Type: text/plain;
>> >> >> | charset="Utf-8"
>> >> >> | Content-Transfer-Encoding: 7bit
>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> | Content-Class: urn:content-classes:message
>> >> >> | Importance: normal
>> >> >> | Priority: normal
>> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
>> >> >> microsoft.public.sqlserver.reportingsvcs:64792
>> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> |
>> >> >> | I get the following error when using the print button on the
>> >> >> HTML
>> >> >> view
>> >> >> of
>> >> >> a
>> >> >> | report with reporting services 2005.
>> >> >> |
>> >> >> | "An error occured during printing (0x8007F304)"
>> >> >> |
>> >> >> | I have a windows application written in VS2003 .net 1.1 and it
>> >> >> loads
>> >> >> a
>> >> >> | webcontrol to show and print the reports. I am using the URL
>> >> >> syntax
>> >> >> to
>> >> >> view
>> >> >> | the report. The report views ok, but when the user clicks the
>> >> >> print
>> >> >> button,
>> >> >> | they get the error.
>> >> >> |
>> >> >> | When I run the report via the report manager, I am able to
>> >> >> print
>> >> >> directly
>> >> >> in
>> >> >> | the browser.
>> >> >> |
>> >> >> | Im running XP SP2.
>> >> >> |
>> >> >> | The application I wrote is running under my windows
>> >> >> credentials, And
>> >> >> I
>> >> >> have
>> >> >> | rights to print to all the printers.
>> >> >> |
>> >> >> | Also.. when I click print, the print dialog doesnt come up..
>> >> >> just
>> >> >> get
>> >> >> the
>> >> >> | error
>> >> >> |
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>|||Daniel,
I don't think we're connecting here. Here is what I am doing:
- I upload the reports from VS to http://localhost/ReportServer
- I pull up IE and browse to http://localhost/Reports
- I select a report and preview it
- I click the print button on the reports toolbar right next to the export
and refresh buttons
- It tells me "an error occurred trying to get the current window"
This is not a hosted winform app. This is the IE app ReportServer created
for me. Is this scenario supposed to be supported? If not, why did MS put
the print button there in the first place?
Thank you very much for you help,
Mike Rodriguez
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> Yes, the IE print control is not supported in hosted winform app. If you
> are writing a winform app you should use the report server winform
> control. Using this control will allow you to integrate report viewing
> with printing into your app.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
>> I'm using RS 2005 and I still get the "cannot get window handle" message
>> in the IE toolbar created by ReportServer.
>>
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> Unfortunately the print control had limitations which forced us to not
>> be able to support this scenario. You can use the new RS 2005 controls
>> which were designed to be embedded in applications. They do, however,
>> require that you use RS 2005.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> So.. How do I fix it?
>> The whole reason we are using reporting services is because a microsoft
>> consultant (Chris Jackson) told us we could imbed it into our
>> application and
>> that it would work.
>> Bill
>> "Daniel Reib [MSFT]" wrote:
>> That is correct. You are using the control in a Web Form app which
>> hosts IE.
>> This is not a supported scenario. The print control will not open
>> because
>> it can not find a handle to the current window.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >I deleted and reinstalled the control..
>> >
>> > Now I get this error:
>> >
>> > "An error occured trying to get the current window"
>> >
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> The print control is not supported in a win forms hosted app. It
>> >> also
>> >> sounds like you have a 2000 version of the print control. To get
>> >> the
>> >> 2005
>> >> version you will need to manually remove the ActiveX object. (Via
>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse
>> >> to RM
>> >> and
>> >> click on the print icon again.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> > The error seem to be speficially with the print control.. In the
>> >> > same
>> >> > application I am able to right click on the browser window and
>> >> > click
>> >> > print.
>> >> > Everthing prints fine. But when I use the print button in the
>> >> > "Reporting
>> >> > Services 2005" tool bar. I get the print error.
>> >> >
>> >> > To reproduce this error..
>> >> > 1. create a report in RS 2005.
>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I
>> >> > use c#)
>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> > 4. Call the navigate method to show the report in the browser
>> >> > (Also I have the webserver set as local intranet site in security
>> >> > so
>> >> > that
>> >> > is
>> >> > passes credentials automatically)
>> >> >
>> >> > (Im also only showing the export / page / print toolbar)
>> >> >
>> >> > 5. click on the print icon on the report tool bar.
>> >> >
>> >> > Thats where I get the error.
>> >> >
>> >> > im usuing 2003 server with reporting services..
>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >
>> >> > Bill
>> >> >
>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >
>> >> >> Hi Sfboiler,
>> >> >>
>> >> >> Welcome to MSDN newsgroup.
>> >> >> From your description, you use the IE WebBrowser control in your
>> >> >> winform
>> >> >> application which navigate to a certain reporting service's
>> >> >> report
>> >> >> page
>> >> >> and
>> >> >> let the winform app user print the report. However, you found
>> >> >> that
>> >> >> you'll
>> >> >> get an errro "An error occured during printing (0x8007F304)"
>> >> >> when try
>> >> >> printing the reprot through the "printing" button on the page,
>> >> >> but
>> >> >> this
>> >> >> works well when we navigate the reprot through external IE
>> >> >> window,
>> >> >> yes?
>> >> >>
>> >> >> Based on my local testing, seems a normal report can be printed
>> >> >> correctly
>> >> >> both through the IE WebBrowser control and external IE
>> >> >> window.... So
>> >> >> this
>> >> >> problem is related to the specific envrionment or application.
>> >> >> Since
>> >> >> the
>> >> >> reporting service's reprot page's print button also use some
>> >> >> script to
>> >> >> execute the print command, I'd suggest you also try directly
>> >> >> using the
>> >> >> WebBrowser's print command to print the current document to see
>> >> >> whether
>> >> >> you
>> >> >> can correctly print it. e.g:
>> >> >>
>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
>> >> >> {
>> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> >> >>
>> >> >> if(doc != null)
>> >> >> {
>> >> >> //doc.execCommand("Print", true, 0);
>> >> >>
>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> >> OPT_PROMPTUSER);
>> >> >> }
>> >> >> }
>> >> >>
>> >> >>
>> >> >> If this also fails, I'm afraid there must have something
>> >> >> incorrect
>> >> >> with
>> >> >> the
>> >> >> browser's script engine or else...
>> >> >>
>> >> >> In addition, you can also check the reporting service's
>> >> >> serverside log
>> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
>> >> >> there're
>> >> >> anything incorrectly for the reporter's generating....
>> >> >>
>> >> >> If there're anything else found, please feel free to post here.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Steven Cheng
>> >> >> Microsoft Online Support
>> >> >>
>> >> >> Get Secure! www.microsoft.com/security
>> >> >> (This posting is provided "AS IS", with no warranties, and
>> >> >> confers no
>> >> >> rights.)
>> >> >>
>> >> >>
>> >> >> --
>> >> >> | Thread-Topic: An error occured during printing or An error
>> >> >> occurred
>> >> >> during print
>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >> >> <sfboiler@.nospam.nospam>
>> >> >> | Subject: An error occured during printing or An error occurred
>> >> >> during
>> >> >> print
>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >> >> | Lines: 20
>> >> >> | Message-ID:
>> >> >> <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >> >> | MIME-Version: 1.0
>> >> >> | Content-Type: text/plain;
>> >> >> | charset="Utf-8"
>> >> >> | Content-Transfer-Encoding: 7bit
>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> | Content-Class: urn:content-classes:message
>> >> >> | Importance: normal
>> >> >> | Priority: normal
>> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
>> >> >> microsoft.public.sqlserver.reportingsvcs:64792
>> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> |
>> >> >> | I get the following error when using the print button on the
>> >> >> HTML
>> >> >> view
>> >> >> of
>> >> >> a
>> >> >> | report with reporting services 2005.
>> >> >> |
>> >> >> | "An error occured during printing (0x8007F304)"
>> >> >> |
>> >> >> | I have a windows application written in VS2003 .net 1.1 and it
>> >> >> loads
>> >> >> a
>> >> >> | webcontrol to show and print the reports. I am using the URL
>> >> >> syntax
>> >> >> to
>> >> >> view
>> >> >> | the report. The report views ok, but when the user clicks the
>> >> >> print
>> >> >> button,
>> >> >> | they get the error.
>> >> >> |
>> >> >> | When I run the report via the report manager, I am able to
>> >> >> print
>> >> >> directly
>> >> >> in
>> >> >> | the browser.
>> >> >> |
>> >> >> | Im running XP SP2.
>> >> >> |
>> >> >> | The application I wrote is running under my windows
>> >> >> credentials, And
>> >> >> I
>> >> >> have
>> >> >> | rights to print to all the printers.
>> >> >> |
>> >> >> | Also.. when I click print, the print dialog doesnt come up..
>> >> >> just
>> >> >> get
>> >> >> the
>> >> >> | error
>> >> >> |
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
>|||Are you physically sitting at the machine or did you connect via remote
desktop or terminal services? Since you are using localhost it is one or the
other. What OS do you have RS running with?
Are you an admin on the box? For this to work it will want to install an
active x control.
It gets confusing because when you said App everyone thought you had your
own asp.net app and were integrating with either URL integration or web
services. For the future, what you are doing is called using Report Manager
(this is what I call the portal that ships with RS).
Note, from IE using Report Manager, printing should work. However, for it to
work, the active x control has to get installed.
If you are on the server (particularly Windows 2003 server OS) there can be
security issues that might trip you up.
I have lots of users using this printing (it came out with SP2 and continued
with RS 2005). All my users have IE6 and either 2000 Pro or XP Pro. All the
users are local admin. In this environment it has worked every time.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
> Daniel,
> I don't think we're connecting here. Here is what I am doing:
> - I upload the reports from VS to http://localhost/ReportServer
> - I pull up IE and browse to http://localhost/Reports
> - I select a report and preview it
> - I click the print button on the reports toolbar right next to the export
> and refresh buttons
> - It tells me "an error occurred trying to get the current window"
> This is not a hosted winform app. This is the IE app ReportServer created
> for me. Is this scenario supposed to be supported? If not, why did MS
> put the print button there in the first place?
> Thank you very much for you help,
> Mike Rodriguez
>
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
>> Yes, the IE print control is not supported in hosted winform app. If you
>> are writing a winform app you should use the report server winform
>> control. Using this control will allow you to integrate report viewing
>> with printing into your app.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
>> I'm using RS 2005 and I still get the "cannot get window handle" message
>> in the IE toolbar created by ReportServer.
>>
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> Unfortunately the print control had limitations which forced us to not
>> be able to support this scenario. You can use the new RS 2005 controls
>> which were designed to be embedded in applications. They do, however,
>> require that you use RS 2005.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> So.. How do I fix it?
>> The whole reason we are using reporting services is because a
>> microsoft
>> consultant (Chris Jackson) told us we could imbed it into our
>> application and
>> that it would work.
>> Bill
>> "Daniel Reib [MSFT]" wrote:
>> That is correct. You are using the control in a Web Form app which
>> hosts IE.
>> This is not a supported scenario. The print control will not open
>> because
>> it can not find a handle to the current window.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >I deleted and reinstalled the control..
>> >
>> > Now I get this error:
>> >
>> > "An error occured trying to get the current window"
>> >
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> The print control is not supported in a win forms hosted app. It
>> >> also
>> >> sounds like you have a 2000 version of the print control. To get
>> >> the
>> >> 2005
>> >> version you will need to manually remove the ActiveX object. (Via
>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse
>> >> to RM
>> >> and
>> >> click on the print icon again.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers
>> >> no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> > The error seem to be speficially with the print control.. In the
>> >> > same
>> >> > application I am able to right click on the browser window and
>> >> > click
>> >> > print.
>> >> > Everthing prints fine. But when I use the print button in the
>> >> > "Reporting
>> >> > Services 2005" tool bar. I get the print error.
>> >> >
>> >> > To reproduce this error..
>> >> > 1. create a report in RS 2005.
>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I
>> >> > use c#)
>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> > 4. Call the navigate method to show the report in the browser
>> >> > (Also I have the webserver set as local intranet site in
>> >> > security so
>> >> > that
>> >> > is
>> >> > passes credentials automatically)
>> >> >
>> >> > (Im also only showing the export / page / print toolbar)
>> >> >
>> >> > 5. click on the print icon on the report tool bar.
>> >> >
>> >> > Thats where I get the error.
>> >> >
>> >> > im usuing 2003 server with reporting services..
>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >
>> >> > Bill
>> >> >
>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >
>> >> >> Hi Sfboiler,
>> >> >>
>> >> >> Welcome to MSDN newsgroup.
>> >> >> From your description, you use the IE WebBrowser control in
>> >> >> your
>> >> >> winform
>> >> >> application which navigate to a certain reporting service's
>> >> >> report
>> >> >> page
>> >> >> and
>> >> >> let the winform app user print the report. However, you found
>> >> >> that
>> >> >> you'll
>> >> >> get an errro "An error occured during printing (0x8007F304)"
>> >> >> when try
>> >> >> printing the reprot through the "printing" button on the page,
>> >> >> but
>> >> >> this
>> >> >> works well when we navigate the reprot through external IE
>> >> >> window,
>> >> >> yes?
>> >> >>
>> >> >> Based on my local testing, seems a normal report can be printed
>> >> >> correctly
>> >> >> both through the IE WebBrowser control and external IE
>> >> >> window.... So
>> >> >> this
>> >> >> problem is related to the specific envrionment or application.
>> >> >> Since
>> >> >> the
>> >> >> reporting service's reprot page's print button also use some
>> >> >> script to
>> >> >> execute the print command, I'd suggest you also try directly
>> >> >> using the
>> >> >> WebBrowser's print command to print the current document to see
>> >> >> whether
>> >> >> you
>> >> >> can correctly print it. e.g:
>> >> >>
>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
>> >> >> {
>> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
>> >> >>
>> >> >> if(doc != null)
>> >> >> {
>> >> >> //doc.execCommand("Print", true, 0);
>> >> >>
>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> >> OPT_PROMPTUSER);
>> >> >> }
>> >> >> }
>> >> >>
>> >> >>
>> >> >> If this also fails, I'm afraid there must have something
>> >> >> incorrect
>> >> >> with
>> >> >> the
>> >> >> browser's script engine or else...
>> >> >>
>> >> >> In addition, you can also check the reporting service's
>> >> >> serverside log
>> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
>> >> >> there're
>> >> >> anything incorrectly for the reporter's generating....
>> >> >>
>> >> >> If there're anything else found, please feel free to post here.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Steven Cheng
>> >> >> Microsoft Online Support
>> >> >>
>> >> >> Get Secure! www.microsoft.com/security
>> >> >> (This posting is provided "AS IS", with no warranties, and
>> >> >> confers no
>> >> >> rights.)
>> >> >>
>> >> >>
>> >> >> --
>> >> >> | Thread-Topic: An error occured during printing or An error
>> >> >> occurred
>> >> >> during print
>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >> >> <sfboiler@.nospam.nospam>
>> >> >> | Subject: An error occured during printing or An error
>> >> >> occurred
>> >> >> during
>> >> >> print
>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >> >> | Lines: 20
>> >> >> | Message-ID:
>> >> >> <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >> >> | MIME-Version: 1.0
>> >> >> | Content-Type: text/plain;
>> >> >> | charset="Utf-8"
>> >> >> | Content-Transfer-Encoding: 7bit
>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> | Content-Class: urn:content-classes:message
>> >> >> | Importance: normal
>> >> >> | Priority: normal
>> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
>> >> >> microsoft.public.sqlserver.reportingsvcs:64792
>> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> |
>> >> >> | I get the following error when using the print button on the
>> >> >> HTML
>> >> >> view
>> >> >> of
>> >> >> a
>> >> >> | report with reporting services 2005.
>> >> >> |
>> >> >> | "An error occured during printing (0x8007F304)"
>> >> >> |
>> >> >> | I have a windows application written in VS2003 .net 1.1 and
>> >> >> it loads
>> >> >> a
>> >> >> | webcontrol to show and print the reports. I am using the URL
>> >> >> syntax
>> >> >> to
>> >> >> view
>> >> >> | the report. The report views ok, but when the user clicks
>> >> >> the print
>> >> >> button,
>> >> >> | they get the error.
>> >> >> |
>> >> >> | When I run the report via the report manager, I am able to
>> >> >> print
>> >> >> directly
>> >> >> in
>> >> >> | the browser.
>> >> >> |
>> >> >> | Im running XP SP2.
>> >> >> |
>> >> >> | The application I wrote is running under my windows
>> >> >> credentials, And
>> >> >> I
>> >> >> have
>> >> >> | rights to print to all the printers.
>> >> >> |
>> >> >> | Also.. when I click print, the print dialog doesnt come up..
>> >> >> just
>> >> >> get
>> >> >> the
>> >> >> | error
>> >> >> |
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
>>
>|||We are usuing a windows app with version .net 1.1. Reporting Services is
running on a differnat server so we do not having any code in .net 2.0.
Our webservices are written in c# .net 1.1 and are not deployed to the same
server as reporting services runs from
We are linking to Reporting services usuing URL access with the IE control
embeded into the windows form.
Bill
"Bruce L-C [MVP]" wrote:
> If you are using RS 2005 then you have at least some of your web site using
> framework 2.0 (since it is a framework 2.0 app). Can you leave most of your
> app at 1.1 and just have a page with the new control in 2.0? As I said, I
> don't know how feasible it is.
> The ability to tightly integrate has improved greatly between versions. RS
> 2005 offers much better integration with the new controls. Because of your
> situation it sounds like that is not an option for you at this time. There
> are ways around it but nothing is that easy (render to a file on the server
> and print that, etc).
> It wasn't until SP2 that there was any printing. Previously my users had to
> export to PDF and then print. That is still an option.
> URL integration has some strong points, web services has it's strong points.
> You seem to have hit an issue with URL integration. If there is any way to
> use the new controls that would be the best solution.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <sfboiler@.nospam.nospam> wrote in message
> news:2E4460ED-0983-4BD4-856B-CF78A875A615@.microsoft.com...
> >I am usuing Visual Studio 2003 (.net 1.1) with Reporting Services 2005. I
> >am
> > not able to ugrade my application at this time. It is very large and
> > years
> > in development. we currently have 36mb of souce code and are close to
> > being
> > ready for deployment. Ugrading to Visual Studio 2005 is not an option at
> > the
> > moment.
> >
> > How can this not be supported? Everything I am usuing in Microsoft.
> >
> > Visual Studio .. Microsoft
> > Windows XP .. Microsoft
> > Interenet Explorer .. Microsoft
> > SQL Server .. Microsoft
> > Reporting Services .. Microsoft
> >
> > Its seems to me there is a problem with the ReportingServices print dll.
> >
> > What good is a reporting tool.. if you cant print?
> >
> > Bill
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> I might be mistaken but I think the issue here is how it is being done.
> >> If
> >> you use the new controls that come with VS 2005 you will get the full
> >> functionality. I haven't used the web control but I have used the new
> >> winform control and the printing functionality is there. If you read the
> >> first post there is URL integration going on. The new controls use web
> >> services which eliminates a lot of the problems.
> >>
> >> The new controls have a whole lot of functionality and provide much
> >> better
> >> integration with a lot less effort than was possible before.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> >> news:umDqU72$FHA.3800@.TK2MSFTNGP10.phx.gbl...
> >> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> >> > news:uTG6ks0$FHA.3136@.TK2MSFTNGP15.phx.gbl...
> >> >> That is correct. You are using the control in a Web Form app which
> >> >> hosts
> >> >> IE. This is not a supported scenario. The print control will not open
> >> >> because it can not find a handle to the current window.
> >> >>
> >> >> --
> >> >
> >> > What'! Are you actually saying that trying to print a report from the
> >> > ReportServer created web application is not a "supported
> >> > scenario"'!!!!
> >> > How exactly *are* we supposed to print these reports?
> >> >
> >> > Very confused,
> >> >
> >> > Mike
> >> >
> >> >
> >>
> >>
> >>
>
>|||Bruce is correct, this is certainly a supported scenario. We could try
looking at the log file and see if it contains anything that might help us.
To do that add the following registry key:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
Services]
"LogRSClientPrintInfo"=dword:00000001
The log file will be generated in the %temp% directory and be called
Log#.tmp. If you could post this, it might help us figure out what is going
on.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
> Are you physically sitting at the machine or did you connect via remote
> desktop or terminal services? Since you are using localhost it is one or
> the other. What OS do you have RS running with?
> Are you an admin on the box? For this to work it will want to install an
> active x control.
> It gets confusing because when you said App everyone thought you had your
> own asp.net app and were integrating with either URL integration or web
> services. For the future, what you are doing is called using Report
> Manager (this is what I call the portal that ships with RS).
> Note, from IE using Report Manager, printing should work. However, for it
> to work, the active x control has to get installed.
> If you are on the server (particularly Windows 2003 server OS) there can
> be security issues that might trip you up.
> I have lots of users using this printing (it came out with SP2 and
> continued with RS 2005). All my users have IE6 and either 2000 Pro or XP
> Pro. All the users are local admin. In this environment it has worked
> every time.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
>> Daniel,
>> I don't think we're connecting here. Here is what I am doing:
>> - I upload the reports from VS to http://localhost/ReportServer
>> - I pull up IE and browse to http://localhost/Reports
>> - I select a report and preview it
>> - I click the print button on the reports toolbar right next to the
>> export and refresh buttons
>> - It tells me "an error occurred trying to get the current window"
>> This is not a hosted winform app. This is the IE app ReportServer
>> created for me. Is this scenario supposed to be supported? If not, why
>> did MS put the print button there in the first place?
>> Thank you very much for you help,
>> Mike Rodriguez
>>
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
>> Yes, the IE print control is not supported in hosted winform app. If
>> you are writing a winform app you should use the report server winform
>> control. Using this control will allow you to integrate report viewing
>> with printing into your app.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
>> I'm using RS 2005 and I still get the "cannot get window handle"
>> message in the IE toolbar created by ReportServer.
>>
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> Unfortunately the print control had limitations which forced us to not
>> be able to support this scenario. You can use the new RS 2005
>> controls which were designed to be embedded in applications. They do,
>> however, require that you use RS 2005.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> So.. How do I fix it?
>> The whole reason we are using reporting services is because a
>> microsoft
>> consultant (Chris Jackson) told us we could imbed it into our
>> application and
>> that it would work.
>> Bill
>> "Daniel Reib [MSFT]" wrote:
>>> That is correct. You are using the control in a Web Form app which
>>> hosts IE.
>>> This is not a supported scenario. The print control will not open
>>> because
>>> it can not find a handle to the current window.
>>>
>>> --
>>> -Daniel
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>> <sfboiler@.nospam.nospam> wrote in message
>>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>>> >I deleted and reinstalled the control..
>>> >
>>> > Now I get this error:
>>> >
>>> > "An error occured trying to get the current window"
>>> >
>>> >
>>> > "Daniel Reib [MSFT]" wrote:
>>> >
>>> >> The print control is not supported in a win forms hosted app. It
>>> >> also
>>> >> sounds like you have a 2000 version of the print control. To get
>>> >> the
>>> >> 2005
>>> >> version you will need to manually remove the ActiveX object.
>>> >> (Via
>>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse
>>> >> to RM
>>> >> and
>>> >> click on the print icon again.
>>> >>
>>> >> --
>>> >> -Daniel
>>> >> This posting is provided "AS IS" with no warranties, and confers
>>> >> no
>>> >> rights.
>>> >>
>>> >>
>>> >> <sfboiler@.nospam.nospam> wrote in message
>>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>>> >> > The error seem to be speficially with the print control.. In
>>> >> > the same
>>> >> > application I am able to right click on the browser window and
>>> >> > click
>>> >> > print.
>>> >> > Everthing prints fine. But when I use the print button in the
>>> >> > "Reporting
>>> >> > Services 2005" tool bar. I get the print error.
>>> >> >
>>> >> > To reproduce this error..
>>> >> > 1. create a report in RS 2005.
>>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I
>>> >> > use c#)
>>> >> > 3. Create a form that embeds the web broswer conrtol.
>>> >> > 4. Call the navigate method to show the report in the browser
>>> >> > (Also I have the webserver set as local intranet site in
>>> >> > security so
>>> >> > that
>>> >> > is
>>> >> > passes credentials automatically)
>>> >> >
>>> >> > (Im also only showing the export / page / print toolbar)
>>> >> >
>>> >> > 5. click on the print icon on the report tool bar.
>>> >> >
>>> >> > Thats where I get the error.
>>> >> >
>>> >> > im usuing 2003 server with reporting services..
>>> >> > and XP sp2, IE 6.0.2900.2180
>>> >> >
>>> >> > Bill
>>> >> >
>>> >> > "Steven Cheng[MSFT]" wrote:
>>> >> >
>>> >> >> Hi Sfboiler,
>>> >> >>
>>> >> >> Welcome to MSDN newsgroup.
>>> >> >> From your description, you use the IE WebBrowser control in
>>> >> >> your
>>> >> >> winform
>>> >> >> application which navigate to a certain reporting service's
>>> >> >> report
>>> >> >> page
>>> >> >> and
>>> >> >> let the winform app user print the report. However, you found
>>> >> >> that
>>> >> >> you'll
>>> >> >> get an errro "An error occured during printing (0x8007F304)"
>>> >> >> when try
>>> >> >> printing the reprot through the "printing" button on the page,
>>> >> >> but
>>> >> >> this
>>> >> >> works well when we navigate the reprot through external IE
>>> >> >> window,
>>> >> >> yes?
>>> >> >>
>>> >> >> Based on my local testing, seems a normal report can be
>>> >> >> printed
>>> >> >> correctly
>>> >> >> both through the IE WebBrowser control and external IE
>>> >> >> window.... So
>>> >> >> this
>>> >> >> problem is related to the specific envrionment or application.
>>> >> >> Since
>>> >> >> the
>>> >> >> reporting service's reprot page's print button also use some
>>> >> >> script to
>>> >> >> execute the print command, I'd suggest you also try directly
>>> >> >> using the
>>> >> >> WebBrowser's print command to print the current document to
>>> >> >> see
>>> >> >> whether
>>> >> >> you
>>> >> >> can correctly print it. e.g:
>>> >> >>
>>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
>>> >> >> {
>>> >> >> mshtml.HTMLDocument doc = axWB.Document as
>>> >> >> mshtml.HTMLDocument;
>>> >> >>
>>> >> >> if(doc != null)
>>> >> >> {
>>> >> >> //doc.execCommand("Print", true, 0);
>>> >> >>
>>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>>> >> >> OPT_PROMPTUSER);
>>> >> >> }
>>> >> >> }
>>> >> >>
>>> >> >>
>>> >> >> If this also fails, I'm afraid there must have something
>>> >> >> incorrect
>>> >> >> with
>>> >> >> the
>>> >> >> browser's script engine or else...
>>> >> >>
>>> >> >> In addition, you can also check the reporting service's
>>> >> >> serverside log
>>> >> >> (under ....\Reporting Services\LogFiles folder) to see
>>> >> >> whether
>>> >> >> there're
>>> >> >> anything incorrectly for the reporter's generating....
>>> >> >>
>>> >> >> If there're anything else found, please feel free to post
>>> >> >> here.
>>> >> >>
>>> >> >> Thanks,
>>> >> >>
>>> >> >> Steven Cheng
>>> >> >> Microsoft Online Support
>>> >> >>
>>> >> >> Get Secure! www.microsoft.com/security
>>> >> >> (This posting is provided "AS IS", with no warranties, and
>>> >> >> confers no
>>> >> >> rights.)
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> | Thread-Topic: An error occured during printing or An error
>>> >> >> occurred
>>> >> >> during print
>>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>>> >> >> <sfboiler@.nospam.nospam>
>>> >> >> | Subject: An error occured during printing or An error
>>> >> >> occurred
>>> >> >> during
>>> >> >> print
>>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>>> >> >> | Lines: 20
>>> >> >> | Message-ID:
>>> >> >> <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>>> >> >> | MIME-Version: 1.0
>>> >> >> | Content-Type: text/plain;
>>> >> >> | charset="Utf-8"
>>> >> >> | Content-Transfer-Encoding: 7bit
>>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
>>> >> >> | Content-Class: urn:content-classes:message
>>> >> >> | Importance: normal
>>> >> >> | Priority: normal
>>> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>>> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
>>> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>>> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
>>> >> >> microsoft.public.sqlserver.reportingsvcs:64792
>>> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>>> >> >> |
>>> >> >> | I get the following error when using the print button on the
>>> >> >> HTML
>>> >> >> view
>>> >> >> of
>>> >> >> a
>>> >> >> | report with reporting services 2005.
>>> >> >> |
>>> >> >> | "An error occured during printing (0x8007F304)"
>>> >> >> |
>>> >> >> | I have a windows application written in VS2003 .net 1.1 and
>>> >> >> it loads
>>> >> >> a
>>> >> >> | webcontrol to show and print the reports. I am using the
>>> >> >> URL syntax
>>> >> >> to
>>> >> >> view
>>> >> >> | the report. The report views ok, but when the user clicks
>>> >> >> the print
>>> >> >> button,
>>> >> >> | they get the error.
>>> >> >> |
>>> >> >> | When I run the report via the report manager, I am able to
>>> >> >> print
>>> >> >> directly
>>> >> >> in
>>> >> >> | the browser.
>>> >> >> |
>>> >> >> | Im running XP SP2.
>>> >> >> |
>>> >> >> | The application I wrote is running under my windows
>>> >> >> credentials, And
>>> >> >> I
>>> >> >> have
>>> >> >> | rights to print to all the printers.
>>> >> >> |
>>> >> >> | Also.. when I click print, the print dialog doesnt come up..
>>> >> >> just
>>> >> >> get
>>> >> >> the
>>> >> >> | error
>>> >> >> |
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>>
>>
>>
>>
>|||I added the key to the registry, then ran my application where the error
shows. I was unable to find any log file on my computer that starts with log
and ends with tmp did a search log*.tmp also did *.tmp and none of the
files returned started with log.
"Daniel Reib [MSFT]" wrote:
> Bruce is correct, this is certainly a supported scenario. We could try
> looking at the log file and see if it contains anything that might help us.
> To do that add the following registry key:
>
> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
> Services]
> "LogRSClientPrintInfo"=dword:00000001
>
> The log file will be generated in the %temp% directory and be called
> Log#.tmp. If you could post this, it might help us figure out what is going
> on.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
> > Are you physically sitting at the machine or did you connect via remote
> > desktop or terminal services? Since you are using localhost it is one or
> > the other. What OS do you have RS running with?
> >
> > Are you an admin on the box? For this to work it will want to install an
> > active x control.
> >
> > It gets confusing because when you said App everyone thought you had your
> > own asp.net app and were integrating with either URL integration or web
> > services. For the future, what you are doing is called using Report
> > Manager (this is what I call the portal that ships with RS).
> >
> > Note, from IE using Report Manager, printing should work. However, for it
> > to work, the active x control has to get installed.
> >
> > If you are on the server (particularly Windows 2003 server OS) there can
> > be security issues that might trip you up.
> >
> > I have lots of users using this printing (it came out with SP2 and
> > continued with RS 2005). All my users have IE6 and either 2000 Pro or XP
> > Pro. All the users are local admin. In this environment it has worked
> > every time.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Michael Rodriguez" <mike@.nospam.com> wrote in message
> > news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
> >> Daniel,
> >>
> >> I don't think we're connecting here. Here is what I am doing:
> >>
> >> - I upload the reports from VS to http://localhost/ReportServer
> >> - I pull up IE and browse to http://localhost/Reports
> >> - I select a report and preview it
> >> - I click the print button on the reports toolbar right next to the
> >> export and refresh buttons
> >> - It tells me "an error occurred trying to get the current window"
> >>
> >> This is not a hosted winform app. This is the IE app ReportServer
> >> created for me. Is this scenario supposed to be supported? If not, why
> >> did MS put the print button there in the first place?
> >>
> >> Thank you very much for you help,
> >>
> >> Mike Rodriguez
> >>
> >>
> >>
> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> >> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> >> Yes, the IE print control is not supported in hosted winform app. If
> >> you are writing a winform app you should use the report server winform
> >> control. Using this control will allow you to integrate report viewing
> >> with printing into your app.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> >> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
> >> I'm using RS 2005 and I still get the "cannot get window handle"
> >> message in the IE toolbar created by ReportServer.
> >>
> >>
> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> >> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
> >> Unfortunately the print control had limitations which forced us to not
> >> be able to support this scenario. You can use the new RS 2005
> >> controls which were designed to be embedded in applications. They do,
> >> however, require that you use RS 2005.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> <sfboiler@.nospam.nospam> wrote in message
> >> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
> >> So.. How do I fix it?
> >>
> >> The whole reason we are using reporting services is because a
> >> microsoft
> >> consultant (Chris Jackson) told us we could imbed it into our
> >> application and
> >> that it would work.
> >>
> >> Bill
> >>
> >> "Daniel Reib [MSFT]" wrote:
> >>
> >>> That is correct. You are using the control in a Web Form app which
> >>> hosts IE.
> >>> This is not a supported scenario. The print control will not open
> >>> because
> >>> it can not find a handle to the current window.
> >>>
> >>> --
> >>> -Daniel
> >>> This posting is provided "AS IS" with no warranties, and confers no
> >>> rights.
> >>>
> >>>
> >>> <sfboiler@.nospam.nospam> wrote in message
> >>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
> >>> >I deleted and reinstalled the control..
> >>> >
> >>> > Now I get this error:
> >>> >
> >>> > "An error occured trying to get the current window"
> >>> >
> >>> >
> >>> > "Daniel Reib [MSFT]" wrote:
> >>> >
> >>> >> The print control is not supported in a win forms hosted app. It
> >>> >> also
> >>> >> sounds like you have a 2000 version of the print control. To get
> >>> >> the
> >>> >> 2005
> >>> >> version you will need to manually remove the ActiveX object.
> >>> >> (Via
> >>> >> IE->Tools->Internet Option->Settings->View Objects). Then browse
> >>> >> to RM
> >>> >> and
> >>> >> click on the print icon again.
> >>> >>
> >>> >> --
> >>> >> -Daniel
> >>> >> This posting is provided "AS IS" with no warranties, and confers
> >>> >> no
> >>> >> rights.
> >>> >>
> >>> >>
> >>> >> <sfboiler@.nospam.nospam> wrote in message
> >>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> >>> >> > The error seem to be speficially with the print control.. In
> >>> >> > the same
> >>> >> > application I am able to right click on the browser window and
> >>> >> > click
> >>> >> > print.
> >>> >> > Everthing prints fine. But when I use the print button in the
> >>> >> > "Reporting
> >>> >> > Services 2005" tool bar. I get the print error.
> >>> >> >
> >>> >> > To reproduce this error..
> >>> >> > 1. create a report in RS 2005.
> >>> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I
> >>> >> > use c#)
> >>> >> > 3. Create a form that embeds the web broswer conrtol.
> >>> >> > 4. Call the navigate method to show the report in the browser
> >>> >> > (Also I have the webserver set as local intranet site in
> >>> >> > security so
> >>> >> > that
> >>> >> > is
> >>> >> > passes credentials automatically)
> >>> >> >
> >>> >> > (Im also only showing the export / page / print toolbar)
> >>> >> >
> >>> >> > 5. click on the print icon on the report tool bar.
> >>> >> >
> >>> >> > Thats where I get the error.
> >>> >> >
> >>> >> > im usuing 2003 server with reporting services..
> >>> >> > and XP sp2, IE 6.0.2900.2180
> >>> >> >
> >>> >> > Bill
> >>> >> >
> >>> >> > "Steven Cheng[MSFT]" wrote:
> >>> >> >
> >>> >> >> Hi Sfboiler,
> >>> >> >>
> >>> >> >> Welcome to MSDN newsgroup.
> >>> >> >> From your description, you use the IE WebBrowser control in
> >>> >> >> your
> >>> >> >> winform
> >>> >> >> application which navigate to a certain reporting service's
> >>> >> >> report
> >>> >> >> page
> >>> >> >> and
> >>> >> >> let the winform app user print the report. However, you found
> >>> >> >> that
> >>> >> >> you'll
> >>> >> >> get an errro "An error occured during printing (0x8007F304)"
> >>> >> >> when try
> >>> >> >> printing the reprot through the "printing" button on the page,
> >>> >> >> but
> >>> >> >> this
> >>> >> >> works well when we navigate the reprot through external IE
> >>> >> >> window,
> >>> >> >> yes?
> >>> >> >>
> >>> >> >> Based on my local testing, seems a normal report can be
> >>> >> >> printed
> >>> >> >> correctly
> >>> >> >> both through the IE WebBrowser control and external IE
> >>> >> >> window.... So
> >>> >> >> this
> >>> >> >> problem is related to the specific envrionment or application.
> >>> >> >> Since
> >>> >> >> the
> >>> >> >> reporting service's reprot page's print button also use some
> >>> >> >> script to
> >>> >> >> execute the print command, I'd suggest you also try directly
> >>> >> >> using the
> >>> >> >> WebBrowser's print command to print the current document to
> >>> >> >> see
> >>> >> >> whether
> >>> >> >> you
> >>> >> >> can correctly print it. e.g:
> >>> >> >>
> >>> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
> >>> >> >> {
> >>> >> >> mshtml.HTMLDocument doc = axWB.Document as
> >>> >> >> mshtml.HTMLDocument;
> >>> >> >>
> >>> >> >> if(doc != null)
> >>> >> >> {
> >>> >> >> //doc.execCommand("Print", true, 0);
> >>> >> >>
> >>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
> >>> >> >> OPT_PROMPTUSER);
> >>> >> >> }
> >>> >> >> }
> >>> >> >>
> >>> >> >>
> >>> >> >> If this also fails, I'm afraid there must have something
> >>> >> >> incorrect
> >>> >> >> with
> >>> >> >> the
> >>> >> >> browser's script engine or else...
> >>> >> >>
> >>> >> >> In addition, you can also check the reporting service's
> >>> >> >> serverside log
> >>> >> >> (under ....\Reporting Services\LogFiles folder) to see
> >>> >> >> whether
> >>> >> >> there're
> >>> >> >> anything incorrectly for the reporter's generating....
> >>> >> >>
> >>> >> >> If there're anything else found, please feel free to post
> >>> >> >> here.
> >>> >> >>
> >>> >> >> Thanks,
> >>> >> >>
> >>> >> >> Steven Cheng
> >>> >> >> Microsoft Online Support
> >>> >> >>
> >>> >> >> Get Secure! www.microsoft.com/security
> >>> >> >> (This posting is provided "AS IS", with no warranties, and
> >>> >> >> confers no
> >>> >> >> rights.)
> >>> >> >>
> >>> >> >>
> >>> >> >> --
> >>> >> >> | Thread-Topic: An error occured during printing or An error
> >>> >> >> occurred
> >>> >> >> during print
> >>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==> >>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
> >>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
> >>> >> >> <sfboiler@.nospam.nospam>
> >>> >> >> | Subject: An error occured during printing or An error
> >>> >> >> occurred
> >>> >> >> during
> >>> >> >> print
> >>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
> >>> >> >> | Lines: 20
> >>> >> >> | Message-ID:
> >>> >> >> <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
> >>> >> >> | MIME-Version: 1.0
> >>> >> >> | Content-Type: text/plain;
> >>> >> >> | charset="Utf-8"
> >>> >> >> | Content-Transfer-Encoding: 7bit
> >>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000|||You added this on the client machine? If so I am not sure why it would not
show up. Do you have a space between Reporting and Services?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sfboiler@.nospam.nospam> wrote in message
news:90E06A1E-1F00-41D2-A357-97C39455843D@.microsoft.com...
>I added the key to the registry, then ran my application where the error
> shows. I was unable to find any log file on my computer that starts with
> log
> and ends with tmp did a search log*.tmp also did *.tmp and none of the
> files returned started with log.
> "Daniel Reib [MSFT]" wrote:
>> Bruce is correct, this is certainly a supported scenario. We could try
>> looking at the log file and see if it contains anything that might help
>> us.
>> To do that add the following registry key:
>>
>> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
>> Services]
>> "LogRSClientPrintInfo"=dword:00000001
>>
>> The log file will be generated in the %temp% directory and be called
>> Log#.tmp. If you could post this, it might help us figure out what is
>> going
>> on.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
>> > Are you physically sitting at the machine or did you connect via remote
>> > desktop or terminal services? Since you are using localhost it is one
>> > or
>> > the other. What OS do you have RS running with?
>> >
>> > Are you an admin on the box? For this to work it will want to install
>> > an
>> > active x control.
>> >
>> > It gets confusing because when you said App everyone thought you had
>> > your
>> > own asp.net app and were integrating with either URL integration or web
>> > services. For the future, what you are doing is called using Report
>> > Manager (this is what I call the portal that ships with RS).
>> >
>> > Note, from IE using Report Manager, printing should work. However, for
>> > it
>> > to work, the active x control has to get installed.
>> >
>> > If you are on the server (particularly Windows 2003 server OS) there
>> > can
>> > be security issues that might trip you up.
>> >
>> > I have lots of users using this printing (it came out with SP2 and
>> > continued with RS 2005). All my users have IE6 and either 2000 Pro or
>> > XP
>> > Pro. All the users are local admin. In this environment it has worked
>> > every time.
>> >
>> >
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> >
>> > "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> > news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
>> >> Daniel,
>> >>
>> >> I don't think we're connecting here. Here is what I am doing:
>> >>
>> >> - I upload the reports from VS to http://localhost/ReportServer
>> >> - I pull up IE and browse to http://localhost/Reports
>> >> - I select a report and preview it
>> >> - I click the print button on the reports toolbar right next to the
>> >> export and refresh buttons
>> >> - It tells me "an error occurred trying to get the current window"
>> >>
>> >> This is not a hosted winform app. This is the IE app ReportServer
>> >> created for me. Is this scenario supposed to be supported? If not,
>> >> why
>> >> did MS put the print button there in the first place?
>> >>
>> >> Thank you very much for you help,
>> >>
>> >> Mike Rodriguez
>> >>
>> >>
>> >>
>> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> >> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
>> >> Yes, the IE print control is not supported in hosted winform app. If
>> >> you are writing a winform app you should use the report server
>> >> winform
>> >> control. Using this control will allow you to integrate report
>> >> viewing
>> >> with printing into your app.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> >> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
>> >> I'm using RS 2005 and I still get the "cannot get window handle"
>> >> message in the IE toolbar created by ReportServer.
>> >>
>> >>
>> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> >> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> >> Unfortunately the print control had limitations which forced us to
>> >> not
>> >> be able to support this scenario. You can use the new RS 2005
>> >> controls which were designed to be embedded in applications. They
>> >> do,
>> >> however, require that you use RS 2005.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> >> So.. How do I fix it?
>> >>
>> >> The whole reason we are using reporting services is because a
>> >> microsoft
>> >> consultant (Chris Jackson) told us we could imbed it into our
>> >> application and
>> >> that it would work.
>> >>
>> >> Bill
>> >>
>> >> "Daniel Reib [MSFT]" wrote:
>> >>
>> >>> That is correct. You are using the control in a Web Form app
>> >>> which
>> >>> hosts IE.
>> >>> This is not a supported scenario. The print control will not
>> >>> open
>> >>> because
>> >>> it can not find a handle to the current window.
>> >>>
>> >>> --
>> >>> -Daniel
>> >>> This posting is provided "AS IS" with no warranties, and confers
>> >>> no
>> >>> rights.
>> >>>
>> >>>
>> >>> <sfboiler@.nospam.nospam> wrote in message
>> >>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >>> >I deleted and reinstalled the control..
>> >>> >
>> >>> > Now I get this error:
>> >>> >
>> >>> > "An error occured trying to get the current window"
>> >>> >
>> >>> >
>> >>> > "Daniel Reib [MSFT]" wrote:
>> >>> >
>> >>> >> The print control is not supported in a win forms hosted app.
>> >>> >> It
>> >>> >> also
>> >>> >> sounds like you have a 2000 version of the print control. To
>> >>> >> get
>> >>> >> the
>> >>> >> 2005
>> >>> >> version you will need to manually remove the ActiveX object.
>> >>> >> (Via
>> >>> >> IE->Tools->Internet Option->Settings->View Objects). Then
>> >>> >> browse
>> >>> >> to RM
>> >>> >> and
>> >>> >> click on the print icon again.
>> >>> >>
>> >>> >> --
>> >>> >> -Daniel
>> >>> >> This posting is provided "AS IS" with no warranties, and
>> >>> >> confers
>> >>> >> no
>> >>> >> rights.
>> >>> >>
>> >>> >>
>> >>> >> <sfboiler@.nospam.nospam> wrote in message
>> >>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >>> >> > The error seem to be speficially with the print control.. In
>> >>> >> > the same
>> >>> >> > application I am able to right click on the browser window
>> >>> >> > and
>> >>> >> > click
>> >>> >> > print.
>> >>> >> > Everthing prints fine. But when I use the print button in
>> >>> >> > the
>> >>> >> > "Reporting
>> >>> >> > Services 2005" tool bar. I get the print error.
>> >>> >> >
>> >>> >> > To reproduce this error..
>> >>> >> > 1. create a report in RS 2005.
>> >>> >> > 2. Create a windows Application in VS2003 .net framework 1.1
>> >>> >> > (I
>> >>> >> > use c#)
>> >>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >>> >> > 4. Call the navigate method to show the report in the
>> >>> >> > browser
>> >>> >> > (Also I have the webserver set as local intranet site in
>> >>> >> > security so
>> >>> >> > that
>> >>> >> > is
>> >>> >> > passes credentials automatically)
>> >>> >> >
>> >>> >> > (Im also only showing the export / page / print toolbar)
>> >>> >> >
>> >>> >> > 5. click on the print icon on the report tool bar.
>> >>> >> >
>> >>> >> > Thats where I get the error.
>> >>> >> >
>> >>> >> > im usuing 2003 server with reporting services..
>> >>> >> > and XP sp2, IE 6.0.2900.2180
>> >>> >> >
>> >>> >> > Bill
>> >>> >> >
>> >>> >> > "Steven Cheng[MSFT]" wrote:
>> >>> >> >
>> >>> >> >> Hi Sfboiler,
>> >>> >> >>
>> >>> >> >> Welcome to MSDN newsgroup.
>> >>> >> >> From your description, you use the IE WebBrowser control in
>> >>> >> >> your
>> >>> >> >> winform
>> >>> >> >> application which navigate to a certain reporting service's
>> >>> >> >> report
>> >>> >> >> page
>> >>> >> >> and
>> >>> >> >> let the winform app user print the report. However, you
>> >>> >> >> found
>> >>> >> >> that
>> >>> >> >> you'll
>> >>> >> >> get an errro "An error occured during printing
>> >>> >> >> (0x8007F304)"
>> >>> >> >> when try
>> >>> >> >> printing the reprot through the "printing" button on the
>> >>> >> >> page,
>> >>> >> >> but
>> >>> >> >> this
>> >>> >> >> works well when we navigate the reprot through external IE
>> >>> >> >> window,
>> >>> >> >> yes?
>> >>> >> >>
>> >>> >> >> Based on my local testing, seems a normal report can be
>> >>> >> >> printed
>> >>> >> >> correctly
>> >>> >> >> both through the IE WebBrowser control and external IE
>> >>> >> >> window.... So
>> >>> >> >> this
>> >>> >> >> problem is related to the specific envrionment or
>> >>> >> >> application.
>> >>> >> >> Since
>> >>> >> >> the
>> >>> >> >> reporting service's reprot page's print button also use
>> >>> >> >> some
>> >>> >> >> script to
>> >>> >> >> execute the print command, I'd suggest you also try
>> >>> >> >> directly
>> >>> >> >> using the
>> >>> >> >> WebBrowser's print command to print the current document to
>> >>> >> >> see
>> >>> >> >> whether
>> >>> >> >> you
>> >>> >> >> can correctly print it. e.g:
>> >>> >> >>
>> >>> >> >> private void btnPrint_Click(object sender, System.EventArgs
>> >>> >> >> e)
>> >>> >> >> {
>> >>> >> >> mshtml.HTMLDocument doc = axWB.Document as
>> >>> >> >> mshtml.HTMLDocument;
>> >>> >> >>
>> >>> >> >> if(doc != null)
>> >>> >> >> {
>> >>> >> >> //doc.execCommand("Print", true, 0);
>> >>> >> >>
>> >>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >>> >> >> OPT_PROMPTUSER);
>> >>> >> >> }
>> >>> >> >> }
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> If this also fails, I'm afraid there must have something
>> >>> >> >> incorrect
>> >>> >> >> with
>> >>> >> >> the
>> >>> >> >> browser's script engine or else...
>> >>> >> >>
>> >>> >> >> In addition, you can also check the reporting service's
>> >>> >> >> serverside log
>> >>> >> >> (under ....\Reporting Services\LogFiles folder) to see
>> >>> >> >> whether
>> >>> >> >> there're
>> >>> >> >> anything incorrectly for the reporter's generating....
>> >>> >> >>
>> >>> >> >> If there're anything else found, please feel free to post
>> >>> >> >> here.
>> >>> >> >>
>> >>> >> >> Thanks,
>> >>> >> >>
>> >>> >> >> Steven Cheng
>> >>> >> >> Microsoft Online Support
>> >>> >> >>
>> >>> >> >> Get Secure! www.microsoft.com/security
>> >>> >> >> (This posting is provided "AS IS", with no warranties, and
>> >>> >> >> confers no
>> >>> >> >> rights.)
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> --
>> >>> >> >> | Thread-Topic: An error occured during printing or An
>> >>> >> >> error
>> >>> >> >> occurred
>> >>> >> >> during print
>> >>> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==>> >>> >> >> | X-WBNR-Posting-Host: 67.109.68.162
>> >>> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
>> >>> >> >> <sfboiler@.nospam.nospam>
>> >>> >> >> | Subject: An error occured during printing or An error
>> >>> >> >> occurred
>> >>> >> >> during
>> >>> >> >> print
>> >>> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
>> >>> >> >> | Lines: 20
>> >>> >> >> | Message-ID:
>> >>> >> >> <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
>> >>> >> >> | MIME-Version: 1.0
>> >>> >> >> | Content-Type: text/plain;
>> >>> >> >> | charset="Utf-8"
>> >>> >> >> | Content-Transfer-Encoding: 7bit
>> >>> >> >> | X-Newsreader: Microsoft CDO for Windows 2000|||I had a cariage return in it.. and change it to a space.. and got nothing.
Then did it with no space.. and still found nothing. I did this on the
client machine where I get the error XP sp2. What directory should the tmp
file be in?
"Daniel Reib [MSFT]" wrote:
> You added this on the client machine? If so I am not sure why it would not
> show up. Do you have a space between Reporting and Services?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <sfboiler@.nospam.nospam> wrote in message
> news:90E06A1E-1F00-41D2-A357-97C39455843D@.microsoft.com...
> >I added the key to the registry, then ran my application where the error
> > shows. I was unable to find any log file on my computer that starts with
> > log
> > and ends with tmp did a search log*.tmp also did *.tmp and none of the
> > files returned started with log.
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> >> Bruce is correct, this is certainly a supported scenario. We could try
> >> looking at the log file and see if it contains anything that might help
> >> us.
> >> To do that add the following registry key:
> >>
> >>
> >> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
> >> Services]
> >> "LogRSClientPrintInfo"=dword:00000001
> >>
> >>
> >> The log file will be generated in the %temp% directory and be called
> >> Log#.tmp. If you could post this, it might help us figure out what is
> >> going
> >> on.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
> >> > Are you physically sitting at the machine or did you connect via remote
> >> > desktop or terminal services? Since you are using localhost it is one
> >> > or
> >> > the other. What OS do you have RS running with?
> >> >
> >> > Are you an admin on the box? For this to work it will want to install
> >> > an
> >> > active x control.
> >> >
> >> > It gets confusing because when you said App everyone thought you had
> >> > your
> >> > own asp.net app and were integrating with either URL integration or web
> >> > services. For the future, what you are doing is called using Report
> >> > Manager (this is what I call the portal that ships with RS).
> >> >
> >> > Note, from IE using Report Manager, printing should work. However, for
> >> > it
> >> > to work, the active x control has to get installed.
> >> >
> >> > If you are on the server (particularly Windows 2003 server OS) there
> >> > can
> >> > be security issues that might trip you up.
> >> >
> >> > I have lots of users using this printing (it came out with SP2 and
> >> > continued with RS 2005). All my users have IE6 and either 2000 Pro or
> >> > XP
> >> > Pro. All the users are local admin. In this environment it has worked
> >> > every time.
> >> >
> >> >
> >> > --
> >> > Bruce Loehle-Conger
> >> > MVP SQL Server Reporting Services
> >> >
> >> > "Michael Rodriguez" <mike@.nospam.com> wrote in message
> >> > news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
> >> >> Daniel,
> >> >>
> >> >> I don't think we're connecting here. Here is what I am doing:
> >> >>
> >> >> - I upload the reports from VS to http://localhost/ReportServer
> >> >> - I pull up IE and browse to http://localhost/Reports
> >> >> - I select a report and preview it
> >> >> - I click the print button on the reports toolbar right next to the
> >> >> export and refresh buttons
> >> >> - It tells me "an error occurred trying to get the current window"
> >> >>
> >> >> This is not a hosted winform app. This is the IE app ReportServer
> >> >> created for me. Is this scenario supposed to be supported? If not,
> >> >> why
> >> >> did MS put the print button there in the first place?
> >> >>
> >> >> Thank you very much for you help,
> >> >>
> >> >> Mike Rodriguez
> >> >>
> >> >>
> >> >>
> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> >> >> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> >> >> Yes, the IE print control is not supported in hosted winform app. If
> >> >> you are writing a winform app you should use the report server
> >> >> winform
> >> >> control. Using this control will allow you to integrate report
> >> >> viewing
> >> >> with printing into your app.
> >> >>
> >> >> --
> >> >> -Daniel
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >>
> >> >>
> >> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> >> >> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
> >> >> I'm using RS 2005 and I still get the "cannot get window handle"
> >> >> message in the IE toolbar created by ReportServer.
> >> >>
> >> >>
> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> >> >> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
> >> >> Unfortunately the print control had limitations which forced us to
> >> >> not
> >> >> be able to support this scenario. You can use the new RS 2005
> >> >> controls which were designed to be embedded in applications. They
> >> >> do,
> >> >> however, require that you use RS 2005.
> >> >>
> >> >> --
> >> >> -Daniel
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >>
> >> >>
> >> >> <sfboiler@.nospam.nospam> wrote in message
> >> >> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
> >> >> So.. How do I fix it?
> >> >>
> >> >> The whole reason we are using reporting services is because a
> >> >> microsoft
> >> >> consultant (Chris Jackson) told us we could imbed it into our
> >> >> application and
> >> >> that it would work.
> >> >>
> >> >> Bill
> >> >>
> >> >> "Daniel Reib [MSFT]" wrote:
> >> >>
> >> >>> That is correct. You are using the control in a Web Form app
> >> >>> which
> >> >>> hosts IE.
> >> >>> This is not a supported scenario. The print control will not
> >> >>> open
> >> >>> because
> >> >>> it can not find a handle to the current window.
> >> >>>
> >> >>> --
> >> >>> -Daniel
> >> >>> This posting is provided "AS IS" with no warranties, and confers
> >> >>> no
> >> >>> rights.
> >> >>>
> >> >>>
> >> >>> <sfboiler@.nospam.nospam> wrote in message
> >> >>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
> >> >>> >I deleted and reinstalled the control..
> >> >>> >
> >> >>> > Now I get this error:
> >> >>> >
> >> >>> > "An error occured trying to get the current window"
> >> >>> >
> >> >>> >
> >> >>> > "Daniel Reib [MSFT]" wrote:
> >> >>> >
> >> >>> >> The print control is not supported in a win forms hosted app.
> >> >>> >> It
> >> >>> >> also
> >> >>> >> sounds like you have a 2000 version of the print control. To
> >> >>> >> get
> >> >>> >> the
> >> >>> >> 2005
> >> >>> >> version you will need to manually remove the ActiveX object.
> >> >>> >> (Via
> >> >>> >> IE->Tools->Internet Option->Settings->View Objects). Then
> >> >>> >> browse
> >> >>> >> to RM
> >> >>> >> and
> >> >>> >> click on the print icon again.
> >> >>> >>
> >> >>> >> --
> >> >>> >> -Daniel
> >> >>> >> This posting is provided "AS IS" with no warranties, and
> >> >>> >> confers
> >> >>> >> no
> >> >>> >> rights.
> >> >>> >>
> >> >>> >>
> >> >>> >> <sfboiler@.nospam.nospam> wrote in message
> >> >>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> >> >>> >> > The error seem to be speficially with the print control.. In
> >> >>> >> > the same
> >> >>> >> > application I am able to right click on the browser window
> >> >>> >> > and
> >> >>> >> > click
> >> >>> >> > print.
> >> >>> >> > Everthing prints fine. But when I use the print button in
> >> >>> >> > the
> >> >>> >> > "Reporting
> >> >>> >> > Services 2005" tool bar. I get the print error.
> >> >>> >> >
> >> >>> >> > To reproduce this error..
> >> >>> >> > 1. create a report in RS 2005.
> >> >>> >> > 2. Create a windows Application in VS2003 .net framework 1.1
> >> >>> >> > (I
> >> >>> >> > use c#)
> >> >>> >> > 3. Create a form that embeds the web broswer conrtol.
> >> >>> >> > 4. Call the navigate method to show the report in the
> >> >>> >> > browser
> >> >>> >> > (Also I have the webserver set as local intranet site in
> >> >>> >> > security so
> >> >>> >> > that
> >> >>> >> > is
> >> >>> >> > passes credentials automatically)
> >> >>> >> >
> >> >>> >> > (Im also only showing the export / page / print toolbar)
> >> >>> >> >
> >> >>> >> > 5. click on the print icon on the report tool bar.
> >> >>> >> >
> >> >>> >> > Thats where I get the error.
> >> >>> >> >
> >> >>> >> > im usuing 2003 server with reporting services..
> >> >>> >> > and XP sp2, IE 6.0.2900.2180
> >> >>> >> >
> >> >>> >> > Bill
> >> >>> >> >
> >> >>> >> > "Steven Cheng[MSFT]" wrote:
> >> >>> >> >
> >> >>> >> >> Hi Sfboiler,
> >> >>> >> >>
> >> >>> >> >> Welcome to MSDN newsgroup.
> >> >>> >> >> From your description, you use the IE WebBrowser control in
> >> >>> >> >> your
> >> >>> >> >> winform
> >> >>> >> >> application which navigate to a certain reporting service's
> >> >>> >> >> report
> >> >>> >> >> page
> >> >>> >> >> and
> >> >>> >> >> let the winform app user print the report. However, you
> >> >>> >> >> found
> >> >>> >> >> that
> >> >>> >> >> you'll
> >> >>> >> >> get an errro "An error occured during printing
> >> >>> >> >> (0x8007F304)"
> >> >>> >> >> when try
> >> >>> >> >> printing the reprot through the "printing" button on the
> >> >>> >> >> page,
> >> >>> >> >> but
> >> >>> >> >> this
> >> >>> >> >> works well when we navigate the reprot through external IE
> >> >>> >> >> window,
> >> >>> >> >> yes?
> >> >>> >> >>
> >> >>> >> >> Based on my local testing, seems a normal report can be
> >> >>> >> >> printed
> >> >>> >> >> correctly
> >> >>> >> >> both through the IE WebBrowser control and external IE
> >> >>> >> >> window.... So
> >> >>> >> >> this
> >> >>> >> >> problem is related to the specific envrionment or
> >> >>> >> >> application.
> >> >>> >> >> Since
> >> >>> >> >> the
> >> >>> >> >> reporting service's reprot page's print button also use
> >> >>> >> >> some
> >> >>> >> >> script to
> >> >>> >> >> execute the print command, I'd suggest you also try
> >> >>> >> >> directly
> >> >>> >> >> using the
> >> >>> >> >> WebBrowser's print command to print the current document to
> >> >>> >> >> see
> >> >>> >> >> whether
> >> >>> >> >> you
> >> >>> >> >> can correctly print it. e.g:
> >> >>> >> >>
> >> >>> >> >> private void btnPrint_Click(object sender, System.EventArgs
> >> >>> >> >> e)
> >> >>> >> >> {
> >> >>> >> >> mshtml.HTMLDocument doc = axWB.Document as
> >> >>> >> >> mshtml.HTMLDocument;
> >> >>> >> >>
> >> >>> >> >> if(doc != null)
> >> >>> >> >> {
> >> >>> >> >> //doc.execCommand("Print", true, 0);
> >> >>> >> >>
> >> >>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
> >> >>> >> >> OPT_PROMPTUSER);
> >> >>> >> >> }
> >> >>> >> >> }|||The current users temp directory. If you type %temp% in start->run it
should take you there.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sfboiler@.nospam.nospam> wrote in message
news:1E8B40E9-F6A4-4FC7-B0FC-B29B089B46DA@.microsoft.com...
>I had a cariage return in it.. and change it to a space.. and got nothing.
> Then did it with no space.. and still found nothing. I did this on the
> client machine where I get the error XP sp2. What directory should the
> tmp
> file be in?
>
> "Daniel Reib [MSFT]" wrote:
>> You added this on the client machine? If so I am not sure why it would
>> not
>> show up. Do you have a space between Reporting and Services?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:90E06A1E-1F00-41D2-A357-97C39455843D@.microsoft.com...
>> >I added the key to the registry, then ran my application where the error
>> > shows. I was unable to find any log file on my computer that starts
>> > with
>> > log
>> > and ends with tmp did a search log*.tmp also did *.tmp and none of
>> > the
>> > files returned started with log.
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> Bruce is correct, this is certainly a supported scenario. We could
>> >> try
>> >> looking at the log file and see if it contains anything that might
>> >> help
>> >> us.
>> >> To do that add the following registry key:
>> >>
>> >>
>> >> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
>> >> Server\80\Reporting
>> >> Services]
>> >> "LogRSClientPrintInfo"=dword:00000001
>> >>
>> >>
>> >> The log file will be generated in the %temp% directory and be called
>> >> Log#.tmp. If you could post this, it might help us figure out what is
>> >> going
>> >> on.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> >> news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
>> >> > Are you physically sitting at the machine or did you connect via
>> >> > remote
>> >> > desktop or terminal services? Since you are using localhost it is
>> >> > one
>> >> > or
>> >> > the other. What OS do you have RS running with?
>> >> >
>> >> > Are you an admin on the box? For this to work it will want to
>> >> > install
>> >> > an
>> >> > active x control.
>> >> >
>> >> > It gets confusing because when you said App everyone thought you had
>> >> > your
>> >> > own asp.net app and were integrating with either URL integration or
>> >> > web
>> >> > services. For the future, what you are doing is called using Report
>> >> > Manager (this is what I call the portal that ships with RS).
>> >> >
>> >> > Note, from IE using Report Manager, printing should work. However,
>> >> > for
>> >> > it
>> >> > to work, the active x control has to get installed.
>> >> >
>> >> > If you are on the server (particularly Windows 2003 server OS) there
>> >> > can
>> >> > be security issues that might trip you up.
>> >> >
>> >> > I have lots of users using this printing (it came out with SP2 and
>> >> > continued with RS 2005). All my users have IE6 and either 2000 Pro
>> >> > or
>> >> > XP
>> >> > Pro. All the users are local admin. In this environment it has
>> >> > worked
>> >> > every time.
>> >> >
>> >> >
>> >> > --
>> >> > Bruce Loehle-Conger
>> >> > MVP SQL Server Reporting Services
>> >> >
>> >> > "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> >> > news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
>> >> >> Daniel,
>> >> >>
>> >> >> I don't think we're connecting here. Here is what I am doing:
>> >> >>
>> >> >> - I upload the reports from VS to http://localhost/ReportServer
>> >> >> - I pull up IE and browse to http://localhost/Reports
>> >> >> - I select a report and preview it
>> >> >> - I click the print button on the reports toolbar right next to the
>> >> >> export and refresh buttons
>> >> >> - It tells me "an error occurred trying to get the current window"
>> >> >>
>> >> >> This is not a hosted winform app. This is the IE app ReportServer
>> >> >> created for me. Is this scenario supposed to be supported? If
>> >> >> not,
>> >> >> why
>> >> >> did MS put the print button there in the first place?
>> >> >>
>> >> >> Thank you very much for you help,
>> >> >>
>> >> >> Mike Rodriguez
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
>> >> >> message
>> >> >> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
>> >> >> Yes, the IE print control is not supported in hosted winform app.
>> >> >> If
>> >> >> you are writing a winform app you should use the report server
>> >> >> winform
>> >> >> control. Using this control will allow you to integrate report
>> >> >> viewing
>> >> >> with printing into your app.
>> >> >>
>> >> >> --
>> >> >> -Daniel
>> >> >> This posting is provided "AS IS" with no warranties, and confers
>> >> >> no
>> >> >> rights.
>> >> >>
>> >> >>
>> >> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> >> >> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
>> >> >> I'm using RS 2005 and I still get the "cannot get window handle"
>> >> >> message in the IE toolbar created by ReportServer.
>> >> >>
>> >> >>
>> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
>> >> >> message
>> >> >> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> >> >> Unfortunately the print control had limitations which forced us
>> >> >> to
>> >> >> not
>> >> >> be able to support this scenario. You can use the new RS 2005
>> >> >> controls which were designed to be embedded in applications.
>> >> >> They
>> >> >> do,
>> >> >> however, require that you use RS 2005.
>> >> >>
>> >> >> --
>> >> >> -Daniel
>> >> >> This posting is provided "AS IS" with no warranties, and confers
>> >> >> no
>> >> >> rights.
>> >> >>
>> >> >>
>> >> >> <sfboiler@.nospam.nospam> wrote in message
>> >> >> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> >> >> So.. How do I fix it?
>> >> >>
>> >> >> The whole reason we are using reporting services is because a
>> >> >> microsoft
>> >> >> consultant (Chris Jackson) told us we could imbed it into our
>> >> >> application and
>> >> >> that it would work.
>> >> >>
>> >> >> Bill
>> >> >>
>> >> >> "Daniel Reib [MSFT]" wrote:
>> >> >>
>> >> >>> That is correct. You are using the control in a Web Form app
>> >> >>> which
>> >> >>> hosts IE.
>> >> >>> This is not a supported scenario. The print control will not
>> >> >>> open
>> >> >>> because
>> >> >>> it can not find a handle to the current window.
>> >> >>>
>> >> >>> --
>> >> >>> -Daniel
>> >> >>> This posting is provided "AS IS" with no warranties, and
>> >> >>> confers
>> >> >>> no
>> >> >>> rights.
>> >> >>>
>> >> >>>
>> >> >>> <sfboiler@.nospam.nospam> wrote in message
>> >> >>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >> >>> >I deleted and reinstalled the control..
>> >> >>> >
>> >> >>> > Now I get this error:
>> >> >>> >
>> >> >>> > "An error occured trying to get the current window"
>> >> >>> >
>> >> >>> >
>> >> >>> > "Daniel Reib [MSFT]" wrote:
>> >> >>> >
>> >> >>> >> The print control is not supported in a win forms hosted
>> >> >>> >> app.
>> >> >>> >> It
>> >> >>> >> also
>> >> >>> >> sounds like you have a 2000 version of the print control.
>> >> >>> >> To
>> >> >>> >> get
>> >> >>> >> the
>> >> >>> >> 2005
>> >> >>> >> version you will need to manually remove the ActiveX
>> >> >>> >> object.
>> >> >>> >> (Via
>> >> >>> >> IE->Tools->Internet Option->Settings->View Objects). Then
>> >> >>> >> browse
>> >> >>> >> to RM
>> >> >>> >> and
>> >> >>> >> click on the print icon again.
>> >> >>> >>
>> >> >>> >> --
>> >> >>> >> -Daniel
>> >> >>> >> This posting is provided "AS IS" with no warranties, and
>> >> >>> >> confers
>> >> >>> >> no
>> >> >>> >> rights.
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> >>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> >>> >> > The error seem to be speficially with the print control..
>> >> >>> >> > In
>> >> >>> >> > the same
>> >> >>> >> > application I am able to right click on the browser
>> >> >>> >> > window
>> >> >>> >> > and
>> >> >>> >> > click
>> >> >>> >> > print.
>> >> >>> >> > Everthing prints fine. But when I use the print button
>> >> >>> >> > in
>> >> >>> >> > the
>> >> >>> >> > "Reporting
>> >> >>> >> > Services 2005" tool bar. I get the print error.
>> >> >>> >> >
>> >> >>> >> > To reproduce this error..
>> >> >>> >> > 1. create a report in RS 2005.
>> >> >>> >> > 2. Create a windows Application in VS2003 .net framework
>> >> >>> >> > 1.1
>> >> >>> >> > (I
>> >> >>> >> > use c#)
>> >> >>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> >>> >> > 4. Call the navigate method to show the report in the
>> >> >>> >> > browser
>> >> >>> >> > (Also I have the webserver set as local intranet site in
>> >> >>> >> > security so
>> >> >>> >> > that
>> >> >>> >> > is
>> >> >>> >> > passes credentials automatically)
>> >> >>> >> >
>> >> >>> >> > (Im also only showing the export / page / print toolbar)
>> >> >>> >> >
>> >> >>> >> > 5. click on the print icon on the report tool bar.
>> >> >>> >> >
>> >> >>> >> > Thats where I get the error.
>> >> >>> >> >
>> >> >>> >> > im usuing 2003 server with reporting services..
>> >> >>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >>> >> >
>> >> >>> >> > Bill
>> >> >>> >> >
>> >> >>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >>> >> >
>> >> >>> >> >> Hi Sfboiler,
>> >> >>> >> >>
>> >> >>> >> >> Welcome to MSDN newsgroup.
>> >> >>> >> >> From your description, you use the IE WebBrowser control
>> >> >>> >> >> in
>> >> >>> >> >> your
>> >> >>> >> >> winform
>> >> >>> >> >> application which navigate to a certain reporting
>> >> >>> >> >> service's
>> >> >>> >> >> report
>> >> >>> >> >> page
>> >> >>> >> >> and
>> >> >>> >> >> let the winform app user print the report. However, you
>> >> >>> >> >> found
>> >> >>> >> >> that
>> >> >>> >> >> you'll
>> >> >>> >> >> get an errro "An error occured during printing
>> >> >>> >> >> (0x8007F304)"
>> >> >>> >> >> when try
>> >> >>> >> >> printing the reprot through the "printing" button on the
>> >> >>> >> >> page,
>> >> >>> >> >> but
>> >> >>> >> >> this
>> >> >>> >> >> works well when we navigate the reprot through external
>> >> >>> >> >> IE
>> >> >>> >> >> window,
>> >> >>> >> >> yes?
>> >> >>> >> >>
>> >> >>> >> >> Based on my local testing, seems a normal report can be
>> >> >>> >> >> printed
>> >> >>> >> >> correctly
>> >> >>> >> >> both through the IE WebBrowser control and external IE
>> >> >>> >> >> window.... So
>> >> >>> >> >> this
>> >> >>> >> >> problem is related to the specific envrionment or
>> >> >>> >> >> application.
>> >> >>> >> >> Since
>> >> >>> >> >> the
>> >> >>> >> >> reporting service's reprot page's print button also use
>> >> >>> >> >> some
>> >> >>> >> >> script to
>> >> >>> >> >> execute the print command, I'd suggest you also try
>> >> >>> >> >> directly
>> >> >>> >> >> using the
>> >> >>> >> >> WebBrowser's print command to print the current document
>> >> >>> >> >> to
>> >> >>> >> >> see
>> >> >>> >> >> whether
>> >> >>> >> >> you
>> >> >>> >> >> can correctly print it. e.g:
>> >> >>> >> >>
>> >> >>> >> >> private void btnPrint_Click(object sender,
>> >> >>> >> >> System.EventArgs
>> >> >>> >> >> e)
>> >> >>> >> >> {
>> >> >>> >> >> mshtml.HTMLDocument doc = axWB.Document as
>> >> >>> >> >> mshtml.HTMLDocument;
>> >> >>> >> >>
>> >> >>> >> >> if(doc != null)
>> >> >>> >> >> {
>> >> >>> >> >> //doc.execCommand("Print", true, 0);
>> >> >>> >> >>
>> >> >>> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
>> >> >>> >> >> OPT_PROMPTUSER);
>> >> >>> >> >> }
>> >> >>> >> >> }|||CRSClientPrint::Print - Starting Function.
reportServerUrl = /ReportServer
reportPath = %2fTestConfig&rs:SessionID=nitytw55avw3wk5505mtdd2m
reportName = TestConfig
CResourceManager::SetLocaleInfo - Starting Function.
SetUICulture - Starting Function.
Attempted UI LCID = 9
Using UI LCID = 1033
SetUICulture - Ending Function.
CResourceManager::LoadResourceDLL - Starting Function.
CResourceManager::LoadResourceDLL - Ending Function: 0x00000000.
CResourceManager::CanUseCurrentLocale - Starting Function.
CResourceManager::CanUseCurrentLocale - Ending Function.
CResourceManager::LoadGDIPlus - Starting Function.
CResourceManager::LoadGDIPlus - Ending Function: 0x00000000.
Attempted culture = 1033
Using culture = 1033
Culture name = English_United States.1252
CResourceManager::SetLocaleInfo - Ending Function: 0x00000000.
Failure QIing or getting the windows handle
Returned error: 0x80004005
"Daniel Reib [MSFT]" wrote:
> The current users temp directory. If you type %temp% in start->run it
> should take you there.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <sfboiler@.nospam.nospam> wrote in message
> news:1E8B40E9-F6A4-4FC7-B0FC-B29B089B46DA@.microsoft.com...
> >I had a cariage return in it.. and change it to a space.. and got nothing.
> > Then did it with no space.. and still found nothing. I did this on the
> > client machine where I get the error XP sp2. What directory should the
> > tmp
> > file be in?
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> >> You added this on the client machine? If so I am not sure why it would
> >> not
> >> show up. Do you have a space between Reporting and Services?
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> <sfboiler@.nospam.nospam> wrote in message
> >> news:90E06A1E-1F00-41D2-A357-97C39455843D@.microsoft.com...
> >> >I added the key to the registry, then ran my application where the error
> >> > shows. I was unable to find any log file on my computer that starts
> >> > with
> >> > log
> >> > and ends with tmp did a search log*.tmp also did *.tmp and none of
> >> > the
> >> > files returned started with log.
> >> >
> >> > "Daniel Reib [MSFT]" wrote:
> >> >
> >> >> Bruce is correct, this is certainly a supported scenario. We could
> >> >> try
> >> >> looking at the log file and see if it contains anything that might
> >> >> help
> >> >> us.
> >> >> To do that add the following registry key:
> >> >>
> >> >>
> >> >> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> >> >> Server\80\Reporting
> >> >> Services]
> >> >> "LogRSClientPrintInfo"=dword:00000001
> >> >>
> >> >>
> >> >> The log file will be generated in the %temp% directory and be called
> >> >> Log#.tmp. If you could post this, it might help us figure out what is
> >> >> going
> >> >> on.
> >> >>
> >> >> --
> >> >> -Daniel
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >>
> >> >>
> >> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> >> news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
> >> >> > Are you physically sitting at the machine or did you connect via
> >> >> > remote
> >> >> > desktop or terminal services? Since you are using localhost it is
> >> >> > one
> >> >> > or
> >> >> > the other. What OS do you have RS running with?
> >> >> >
> >> >> > Are you an admin on the box? For this to work it will want to
> >> >> > install
> >> >> > an
> >> >> > active x control.
> >> >> >
> >> >> > It gets confusing because when you said App everyone thought you had
> >> >> > your
> >> >> > own asp.net app and were integrating with either URL integration or
> >> >> > web
> >> >> > services. For the future, what you are doing is called using Report
> >> >> > Manager (this is what I call the portal that ships with RS).
> >> >> >
> >> >> > Note, from IE using Report Manager, printing should work. However,
> >> >> > for
> >> >> > it
> >> >> > to work, the active x control has to get installed.
> >> >> >
> >> >> > If you are on the server (particularly Windows 2003 server OS) there
> >> >> > can
> >> >> > be security issues that might trip you up.
> >> >> >
> >> >> > I have lots of users using this printing (it came out with SP2 and
> >> >> > continued with RS 2005). All my users have IE6 and either 2000 Pro
> >> >> > or
> >> >> > XP
> >> >> > Pro. All the users are local admin. In this environment it has
> >> >> > worked
> >> >> > every time.
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Bruce Loehle-Conger
> >> >> > MVP SQL Server Reporting Services
> >> >> >
> >> >> > "Michael Rodriguez" <mike@.nospam.com> wrote in message
> >> >> > news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
> >> >> >> Daniel,
> >> >> >>
> >> >> >> I don't think we're connecting here. Here is what I am doing:
> >> >> >>
> >> >> >> - I upload the reports from VS to http://localhost/ReportServer
> >> >> >> - I pull up IE and browse to http://localhost/Reports
> >> >> >> - I select a report and preview it
> >> >> >> - I click the print button on the reports toolbar right next to the
> >> >> >> export and refresh buttons
> >> >> >> - It tells me "an error occurred trying to get the current window"
> >> >> >>
> >> >> >> This is not a hosted winform app. This is the IE app ReportServer
> >> >> >> created for me. Is this scenario supposed to be supported? If
> >> >> >> not,
> >> >> >> why
> >> >> >> did MS put the print button there in the first place?
> >> >> >>
> >> >> >> Thank you very much for you help,
> >> >> >>
> >> >> >> Mike Rodriguez
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> >> >> >> Yes, the IE print control is not supported in hosted winform app.
> >> >> >> If
> >> >> >> you are writing a winform app you should use the report server
> >> >> >> winform
> >> >> >> control. Using this control will allow you to integrate report
> >> >> >> viewing
> >> >> >> with printing into your app.
> >> >> >>
> >> >> >> --
> >> >> >> -Daniel
> >> >> >> This posting is provided "AS IS" with no warranties, and confers
> >> >> >> no
> >> >> >> rights.
> >> >> >>
> >> >> >>
> >> >> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> >> >> >> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
> >> >> >> I'm using RS 2005 and I still get the "cannot get window handle"
> >> >> >> message in the IE toolbar created by ReportServer.
> >> >> >>
> >> >> >>
> >> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
> >> >> >> Unfortunately the print control had limitations which forced us
> >> >> >> to
> >> >> >> not
> >> >> >> be able to support this scenario. You can use the new RS 2005
> >> >> >> controls which were designed to be embedded in applications.
> >> >> >> They
> >> >> >> do,
> >> >> >> however, require that you use RS 2005.
> >> >> >>
> >> >> >> --
> >> >> >> -Daniel
> >> >> >> This posting is provided "AS IS" with no warranties, and confers
> >> >> >> no
> >> >> >> rights.
> >> >> >>
> >> >> >>
> >> >> >> <sfboiler@.nospam.nospam> wrote in message
> >> >> >> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
> >> >> >> So.. How do I fix it?
> >> >> >>
> >> >> >> The whole reason we are using reporting services is because a
> >> >> >> microsoft
> >> >> >> consultant (Chris Jackson) told us we could imbed it into our
> >> >> >> application and
> >> >> >> that it would work.
> >> >> >>
> >> >> >> Bill
> >> >> >>
> >> >> >> "Daniel Reib [MSFT]" wrote:
> >> >> >>
> >> >> >>> That is correct. You are using the control in a Web Form app
> >> >> >>> which
> >> >> >>> hosts IE.
> >> >> >>> This is not a supported scenario. The print control will not
> >> >> >>> open
> >> >> >>> because
> >> >> >>> it can not find a handle to the current window.
> >> >> >>>
> >> >> >>> --
> >> >> >>> -Daniel
> >> >> >>> This posting is provided "AS IS" with no warranties, and
> >> >> >>> confers
> >> >> >>> no
> >> >> >>> rights.
> >> >> >>>
> >> >> >>>
> >> >> >>> <sfboiler@.nospam.nospam> wrote in message
> >> >> >>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
> >> >> >>> >I deleted and reinstalled the control..
> >> >> >>> >
> >> >> >>> > Now I get this error:
> >> >> >>> >
> >> >> >>> > "An error occured trying to get the current window"
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > "Daniel Reib [MSFT]" wrote:
> >> >> >>> >
> >> >> >>> >> The print control is not supported in a win forms hosted
> >> >> >>> >> app.
> >> >> >>> >> It
> >> >> >>> >> also
> >> >> >>> >> sounds like you have a 2000 version of the print control.
> >> >> >>> >> To
> >> >> >>> >> get
> >> >> >>> >> the
> >> >> >>> >> 2005
> >> >> >>> >> version you will need to manually remove the ActiveX
> >> >> >>> >> object.
> >> >> >>> >> (Via
> >> >> >>> >> IE->Tools->Internet Option->Settings->View Objects). Then
> >> >> >>> >> browse
> >> >> >>> >> to RM
> >> >> >>> >> and
> >> >> >>> >> click on the print icon again.
> >> >> >>> >>
> >> >> >>> >> --
> >> >> >>> >> -Daniel
> >> >> >>> >> This posting is provided "AS IS" with no warranties, and
> >> >> >>> >> confers
> >> >> >>> >> no
> >> >> >>> >> rights.
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>> >> <sfboiler@.nospam.nospam> wrote in message
> >> >> >>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> >> >> >>> >> > The error seem to be speficially with the print control..
> >> >> >>> >> > In
> >> >> >>> >> > the same
> >> >> >>> >> > application I am able to right click on the browser
> >> >> >>> >> > window
> >> >> >>> >> > and
> >> >> >>> >> > click
> >> >> >>> >> > print.
> >> >> >>> >> > Everthing prints fine. But when I use the print button
> >> >> >>> >> > in
> >> >> >>> >> > the
> >> >> >>> >> > "Reporting
> >> >> >>> >> > Services 2005" tool bar. I get the print error.
> >> >> >>> >> >
> >> >> >>> >> > To reproduce this error..
> >> >> >>> >> > 1. create a report in RS 2005.
> >> >> >>> >> > 2. Create a windows Application in VS2003 .net framework
> >> >> >>> >> > 1.1
> >> >> >>> >> > (I
> >> >> >>> >> > use c#)
> >> >> >>> >> > 3. Create a form that embeds the web broswer conrtol.
> >> >> >>> >> > 4. Call the navigate method to show the report in the
> >> >> >>> >> > browser
> >> >> >>> >> > (Also I have the webserver set as local intranet site in
> >> >> >>> >> > security so
> >> >> >>> >> > that
> >> >> >>> >> > is
> >> >> >>> >> > passes credentials automatically)
> >> >> >>> >> >
> >> >> >>> >> > (Im also only showing the export / page / print toolbar)
> >> >> >>> >> >
> >> >> >>> >> > 5. click on the print icon on the report tool bar.
> >> >> >>> >> >
> >> >> >>> >> > Thats where I get the error.
> >> >> >>> >> >
> >> >> >>> >> > im usuing 2003 server with reporting services..
> >> >> >>> >> > and XP sp2, IE 6.0.2900.2180
> >> >> >>> >> >
> >> >> >>> >> > Bill
> >> >> >>> >> >
> >> >> >>> >> > "Steven Cheng[MSFT]" wrote:
> >> >> >>> >> >
> >> >> >>> >> >> Hi Sfboiler,
> >> >> >>> >> >>
> >> >> >>> >> >> Welcome to MSDN newsgroup.
> >> >> >>> >> >> From your description, you use the IE WebBrowser control
> >> >> >>> >> >> in
> >> >> >>> >> >> your
> >> >> >>> >> >> winform
> >> >> >>> >> >> application which navigate to a certain reporting
> >> >> >>> >> >> service's
> >> >> >>> >> >> report
> >> >> >>> >> >> page
> >> >> >>> >> >> and|||Hmm, nothing really helpful. I am at a loss. I have never seen this error
when using IE, only when hosting IE in winforms. I have no idea why you
would be getting this.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sfboiler@.nospam.nospam> wrote in message
news:04B36EF9-0EA0-4A34-80BD-6B3C61E428E1@.microsoft.com...
> CRSClientPrint::Print - Starting Function.
> reportServerUrl = /ReportServer
> reportPath = %2fTestConfig&rs:SessionID=nitytw55avw3wk5505mtdd2m
> reportName = TestConfig
> CResourceManager::SetLocaleInfo - Starting Function.
> SetUICulture - Starting Function.
> Attempted UI LCID = 9
> Using UI LCID = 1033
> SetUICulture - Ending Function.
> CResourceManager::LoadResourceDLL - Starting Function.
> CResourceManager::LoadResourceDLL - Ending Function: 0x00000000.
> CResourceManager::CanUseCurrentLocale - Starting Function.
> CResourceManager::CanUseCurrentLocale - Ending Function.
> CResourceManager::LoadGDIPlus - Starting Function.
> CResourceManager::LoadGDIPlus - Ending Function: 0x00000000.
> Attempted culture = 1033
> Using culture = 1033
> Culture name = English_United States.1252
> CResourceManager::SetLocaleInfo - Ending Function: 0x00000000.
> Failure QIing or getting the windows handle
> Returned error: 0x80004005
>
> "Daniel Reib [MSFT]" wrote:
>> The current users temp directory. If you type %temp% in start->run it
>> should take you there.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <sfboiler@.nospam.nospam> wrote in message
>> news:1E8B40E9-F6A4-4FC7-B0FC-B29B089B46DA@.microsoft.com...
>> >I had a cariage return in it.. and change it to a space.. and got
>> >nothing.
>> > Then did it with no space.. and still found nothing. I did this on the
>> > client machine where I get the error XP sp2. What directory should the
>> > tmp
>> > file be in?
>> >
>> >
>> > "Daniel Reib [MSFT]" wrote:
>> >
>> >> You added this on the client machine? If so I am not sure why it
>> >> would
>> >> not
>> >> show up. Do you have a space between Reporting and Services?
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> news:90E06A1E-1F00-41D2-A357-97C39455843D@.microsoft.com...
>> >> >I added the key to the registry, then ran my application where the
>> >> >error
>> >> > shows. I was unable to find any log file on my computer that starts
>> >> > with
>> >> > log
>> >> > and ends with tmp did a search log*.tmp also did *.tmp and none
>> >> > of
>> >> > the
>> >> > files returned started with log.
>> >> >
>> >> > "Daniel Reib [MSFT]" wrote:
>> >> >
>> >> >> Bruce is correct, this is certainly a supported scenario. We could
>> >> >> try
>> >> >> looking at the log file and see if it contains anything that might
>> >> >> help
>> >> >> us.
>> >> >> To do that add the following registry key:
>> >> >>
>> >> >>
>> >> >> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
>> >> >> Server\80\Reporting
>> >> >> Services]
>> >> >> "LogRSClientPrintInfo"=dword:00000001
>> >> >>
>> >> >>
>> >> >> The log file will be generated in the %temp% directory and be
>> >> >> called
>> >> >> Log#.tmp. If you could post this, it might help us figure out what
>> >> >> is
>> >> >> going
>> >> >> on.
>> >> >>
>> >> >> --
>> >> >> -Daniel
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> >> rights.
>> >> >>
>> >> >>
>> >> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> >> >> news:ubF2V%23BAGHA.3476@.TK2MSFTNGP10.phx.gbl...
>> >> >> > Are you physically sitting at the machine or did you connect via
>> >> >> > remote
>> >> >> > desktop or terminal services? Since you are using localhost it is
>> >> >> > one
>> >> >> > or
>> >> >> > the other. What OS do you have RS running with?
>> >> >> >
>> >> >> > Are you an admin on the box? For this to work it will want to
>> >> >> > install
>> >> >> > an
>> >> >> > active x control.
>> >> >> >
>> >> >> > It gets confusing because when you said App everyone thought you
>> >> >> > had
>> >> >> > your
>> >> >> > own asp.net app and were integrating with either URL integration
>> >> >> > or
>> >> >> > web
>> >> >> > services. For the future, what you are doing is called using
>> >> >> > Report
>> >> >> > Manager (this is what I call the portal that ships with RS).
>> >> >> >
>> >> >> > Note, from IE using Report Manager, printing should work.
>> >> >> > However,
>> >> >> > for
>> >> >> > it
>> >> >> > to work, the active x control has to get installed.
>> >> >> >
>> >> >> > If you are on the server (particularly Windows 2003 server OS)
>> >> >> > there
>> >> >> > can
>> >> >> > be security issues that might trip you up.
>> >> >> >
>> >> >> > I have lots of users using this printing (it came out with SP2
>> >> >> > and
>> >> >> > continued with RS 2005). All my users have IE6 and either 2000
>> >> >> > Pro
>> >> >> > or
>> >> >> > XP
>> >> >> > Pro. All the users are local admin. In this environment it has
>> >> >> > worked
>> >> >> > every time.
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Bruce Loehle-Conger
>> >> >> > MVP SQL Server Reporting Services
>> >> >> >
>> >> >> > "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> >> >> > news:OFs68pBAGHA.2148@.TK2MSFTNGP10.phx.gbl...
>> >> >> >> Daniel,
>> >> >> >>
>> >> >> >> I don't think we're connecting here. Here is what I am doing:
>> >> >> >>
>> >> >> >> - I upload the reports from VS to http://localhost/ReportServer
>> >> >> >> - I pull up IE and browse to http://localhost/Reports
>> >> >> >> - I select a report and preview it
>> >> >> >> - I click the print button on the reports toolbar right next to
>> >> >> >> the
>> >> >> >> export and refresh buttons
>> >> >> >> - It tells me "an error occurred trying to get the current
>> >> >> >> window"
>> >> >> >>
>> >> >> >> This is not a hosted winform app. This is the IE app
>> >> >> >> ReportServer
>> >> >> >> created for me. Is this scenario supposed to be supported? If
>> >> >> >> not,
>> >> >> >> why
>> >> >> >> did MS put the print button there in the first place?
>> >> >> >>
>> >> >> >> Thank you very much for you help,
>> >> >> >>
>> >> >> >> Mike Rodriguez
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:%23ZGdkyAAGHA.3136@.TK2MSFTNGP15.phx.gbl...
>> >> >> >> Yes, the IE print control is not supported in hosted winform
>> >> >> >> app.
>> >> >> >> If
>> >> >> >> you are writing a winform app you should use the report server
>> >> >> >> winform
>> >> >> >> control. Using this control will allow you to integrate report
>> >> >> >> viewing
>> >> >> >> with printing into your app.
>> >> >> >>
>> >> >> >> --
>> >> >> >> -Daniel
>> >> >> >> This posting is provided "AS IS" with no warranties, and
>> >> >> >> confers
>> >> >> >> no
>> >> >> >> rights.
>> >> >> >>
>> >> >> >>
>> >> >> >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> >> >> >> news:uGB4W13$FHA.2092@.TK2MSFTNGP10.phx.gbl...
>> >> >> >> I'm using RS 2005 and I still get the "cannot get window
>> >> >> >> handle"
>> >> >> >> message in the IE toolbar created by ReportServer.
>> >> >> >>
>> >> >> >>
>> >> >> >> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:Occ5qK3$FHA.2256@.TK2MSFTNGP11.phx.gbl...
>> >> >> >> Unfortunately the print control had limitations which forced
>> >> >> >> us
>> >> >> >> to
>> >> >> >> not
>> >> >> >> be able to support this scenario. You can use the new RS
>> >> >> >> 2005
>> >> >> >> controls which were designed to be embedded in applications.
>> >> >> >> They
>> >> >> >> do,
>> >> >> >> however, require that you use RS 2005.
>> >> >> >>
>> >> >> >> --
>> >> >> >> -Daniel
>> >> >> >> This posting is provided "AS IS" with no warranties, and
>> >> >> >> confers
>> >> >> >> no
>> >> >> >> rights.
>> >> >> >>
>> >> >> >>
>> >> >> >> <sfboiler@.nospam.nospam> wrote in message
>> >> >> >> news:09EC2A3B-BF05-4135-89B8-FB89A170E7FC@.microsoft.com...
>> >> >> >> So.. How do I fix it?
>> >> >> >>
>> >> >> >> The whole reason we are using reporting services is because
>> >> >> >> a
>> >> >> >> microsoft
>> >> >> >> consultant (Chris Jackson) told us we could imbed it into
>> >> >> >> our
>> >> >> >> application and
>> >> >> >> that it would work.
>> >> >> >>
>> >> >> >> Bill
>> >> >> >>
>> >> >> >> "Daniel Reib [MSFT]" wrote:
>> >> >> >>
>> >> >> >>> That is correct. You are using the control in a Web Form
>> >> >> >>> app
>> >> >> >>> which
>> >> >> >>> hosts IE.
>> >> >> >>> This is not a supported scenario. The print control will
>> >> >> >>> not
>> >> >> >>> open
>> >> >> >>> because
>> >> >> >>> it can not find a handle to the current window.
>> >> >> >>>
>> >> >> >>> --
>> >> >> >>> -Daniel
>> >> >> >>> This posting is provided "AS IS" with no warranties, and
>> >> >> >>> confers
>> >> >> >>> no
>> >> >> >>> rights.
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> <sfboiler@.nospam.nospam> wrote in message
>> >> >> >>> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
>> >> >> >>> >I deleted and reinstalled the control..
>> >> >> >>> >
>> >> >> >>> > Now I get this error:
>> >> >> >>> >
>> >> >> >>> > "An error occured trying to get the current window"
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> > "Daniel Reib [MSFT]" wrote:
>> >> >> >>> >
>> >> >> >>> >> The print control is not supported in a win forms hosted
>> >> >> >>> >> app.
>> >> >> >>> >> It
>> >> >> >>> >> also
>> >> >> >>> >> sounds like you have a 2000 version of the print
>> >> >> >>> >> control.
>> >> >> >>> >> To
>> >> >> >>> >> get
>> >> >> >>> >> the
>> >> >> >>> >> 2005
>> >> >> >>> >> version you will need to manually remove the ActiveX
>> >> >> >>> >> object.
>> >> >> >>> >> (Via
>> >> >> >>> >> IE->Tools->Internet Option->Settings->View Objects).
>> >> >> >>> >> Then
>> >> >> >>> >> browse
>> >> >> >>> >> to RM
>> >> >> >>> >> and
>> >> >> >>> >> click on the print icon again.
>> >> >> >>> >>
>> >> >> >>> >> --
>> >> >> >>> >> -Daniel
>> >> >> >>> >> This posting is provided "AS IS" with no warranties, and
>> >> >> >>> >> confers
>> >> >> >>> >> no
>> >> >> >>> >> rights.
>> >> >> >>> >>
>> >> >> >>> >>
>> >> >> >>> >> <sfboiler@.nospam.nospam> wrote in message
>> >> >> >>> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
>> >> >> >>> >> > The error seem to be speficially with the print
>> >> >> >>> >> > control..
>> >> >> >>> >> > In
>> >> >> >>> >> > the same
>> >> >> >>> >> > application I am able to right click on the browser
>> >> >> >>> >> > window
>> >> >> >>> >> > and
>> >> >> >>> >> > click
>> >> >> >>> >> > print.
>> >> >> >>> >> > Everthing prints fine. But when I use the print
>> >> >> >>> >> > button
>> >> >> >>> >> > in
>> >> >> >>> >> > the
>> >> >> >>> >> > "Reporting
>> >> >> >>> >> > Services 2005" tool bar. I get the print error.
>> >> >> >>> >> >
>> >> >> >>> >> > To reproduce this error..
>> >> >> >>> >> > 1. create a report in RS 2005.
>> >> >> >>> >> > 2. Create a windows Application in VS2003 .net
>> >> >> >>> >> > framework
>> >> >> >>> >> > 1.1
>> >> >> >>> >> > (I
>> >> >> >>> >> > use c#)
>> >> >> >>> >> > 3. Create a form that embeds the web broswer conrtol.
>> >> >> >>> >> > 4. Call the navigate method to show the report in the
>> >> >> >>> >> > browser
>> >> >> >>> >> > (Also I have the webserver set as local intranet site
>> >> >> >>> >> > in
>> >> >> >>> >> > security so
>> >> >> >>> >> > that
>> >> >> >>> >> > is
>> >> >> >>> >> > passes credentials automatically)
>> >> >> >>> >> >
>> >> >> >>> >> > (Im also only showing the export / page / print
>> >> >> >>> >> > toolbar)
>> >> >> >>> >> >
>> >> >> >>> >> > 5. click on the print icon on the report tool bar.
>> >> >> >>> >> >
>> >> >> >>> >> > Thats where I get the error.
>> >> >> >>> >> >
>> >> >> >>> >> > im usuing 2003 server with reporting services..
>> >> >> >>> >> > and XP sp2, IE 6.0.2900.2180
>> >> >> >>> >> >
>> >> >> >>> >> > Bill
>> >> >> >>> >> >
>> >> >> >>> >> > "Steven Cheng[MSFT]" wrote:
>> >> >> >>> >> >
>> >> >> >>> >> >> Hi Sfboiler,
>> >> >> >>> >> >>
>> >> >> >>> >> >> Welcome to MSDN newsgroup.
>> >> >> >>> >> >> From your description, you use the IE WebBrowser
>> >> >> >>> >> >> control
>> >> >> >>> >> >> in
>> >> >> >>> >> >> your
>> >> >> >>> >> >> winform
>> >> >> >>> >> >> application which navigate to a certain reporting
>> >> >> >>> >> >> service's
>> >> >> >>> >> >> report
>> >> >> >>> >> >> page
>> >> >> >>> >> >> and|||To print a report from within a windows application (windows application !=web application) you have to do one of the following:
1. Disable the print icon on the reporting server (this will disable it for
all reports, which may be an undesireable effect). Then impliment your own
via the windows form. See the SQL 2005 Books Online documents for how to do
this.
2. Override Microsoft's POS code with a more browser/platform friendly
(heh, not like their stuff is w3c compliant anyway), more secure method...
private void axWebBrowser1_DocumentComplete(object sender,
AxSHDocVw.DWebBrowserEvents2_DocumentCompleteEvent e) {
string html =((mshtml.IHTMLElement)(((mshtml.HTMLDocumentClass)(((System.Object)((axWebBr
owser1.Document))))).body)).innerHTML;
if
(Regex.IsMatch(html,@."onclick=\""ClientToolbarReportViewerControl_ctl01.Load
PrintControl\(\);return\sfalse;\""", RegexOptions.Compiled)) {
((mshtml.IHTMLElement)(((mshtml.HTMLDocumentClass)(((System.Object)((axWebBr
owser1.Document))))).body)).innerHTML = html.Replace(
@."onclick=""ClientToolbarReportViewerControl_ctl01.LoadPrintControl();return
false;""",
@."onclick=""javascript:print()""");
}
}
Some changes should include, less casting, more flexible regex & string
matching, and javascript:print() could be replaced with better options,
also. I just did this as a quick hack to show that it is possible, seeming
that Microsoft doesn't support their stuff, and that there are many web
posts about this problems.
-John
<sfboiler@.nospam.nospam> wrote in message
news:04F1C03C-7548-4494-BB82-DC84988FAE7D@.microsoft.com...
> We are usuing a windows app with version .net 1.1. Reporting Services is
> running on a differnat server so we do not having any code in .net 2.0.
> Our webservices are written in c# .net 1.1 and are not deployed to the
same
> server as reporting services runs from
> We are linking to Reporting services usuing URL access with the IE control
> embeded into the windows form.
> Bill
> "Bruce L-C [MVP]" wrote:
> > If you are using RS 2005 then you have at least some of your web site
using
> > framework 2.0 (since it is a framework 2.0 app). Can you leave most of
your
> > app at 1.1 and just have a page with the new control in 2.0? As I said,
I
> > don't know how feasible it is.
> >
> > The ability to tightly integrate has improved greatly between versions.
RS
> > 2005 offers much better integration with the new controls. Because of
your
> > situation it sounds like that is not an option for you at this time.
There
> > are ways around it but nothing is that easy (render to a file on the
server
> > and print that, etc).
> >
> > It wasn't until SP2 that there was any printing. Previously my users had
to
> > export to PDF and then print. That is still an option.
> >
> > URL integration has some strong points, web services has it's strong
points.
> > You seem to have hit an issue with URL integration. If there is any way
to
> > use the new controls that would be the best solution.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > <sfboiler@.nospam.nospam> wrote in message
> > news:2E4460ED-0983-4BD4-856B-CF78A875A615@.microsoft.com...
> > >I am usuing Visual Studio 2003 (.net 1.1) with Reporting Services 2005.
I
> > >am
> > > not able to ugrade my application at this time. It is very large and
> > > years
> > > in development. we currently have 36mb of souce code and are close to
> > > being
> > > ready for deployment. Ugrading to Visual Studio 2005 is not an option
at
> > > the
> > > moment.
> > >
> > > How can this not be supported? Everything I am usuing in Microsoft.
> > >
> > > Visual Studio .. Microsoft
> > > Windows XP .. Microsoft
> > > Interenet Explorer .. Microsoft
> > > SQL Server .. Microsoft
> > > Reporting Services .. Microsoft
> > >
> > > Its seems to me there is a problem with the ReportingServices print
dll.
> > >
> > > What good is a reporting tool.. if you cant print?
> > >
> > > Bill
> > >
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > >> I might be mistaken but I think the issue here is how it is being
done.
> > >> If
> > >> you use the new controls that come with VS 2005 you will get the full
> > >> functionality. I haven't used the web control but I have used the new
> > >> winform control and the printing functionality is there. If you read
the
> > >> first post there is URL integration going on. The new controls use
web
> > >> services which eliminates a lot of the problems.
> > >>
> > >> The new controls have a whole lot of functionality and provide much
> > >> better
> > >> integration with a lot less effort than was possible before.
> > >>
> > >>
> > >> --
> > >> Bruce Loehle-Conger
> > >> MVP SQL Server Reporting Services
> > >>
> > >>
> > >> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> > >> news:umDqU72$FHA.3800@.TK2MSFTNGP10.phx.gbl...
> > >> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in
message
> > >> > news:uTG6ks0$FHA.3136@.TK2MSFTNGP15.phx.gbl...
> > >> >> That is correct. You are using the control in a Web Form app which
> > >> >> hosts
> > >> >> IE. This is not a supported scenario. The print control will not
open
> > >> >> because it can not find a handle to the current window.
> > >> >>
> > >> >> --
> > >> >
> > >> > What'! Are you actually saying that trying to print a report from
the
> > >> > ReportServer created web application is not a "supported
> > >> > scenario"'!!!!
> > >> > How exactly *are* we supposed to print these reports?
> > >> >
> > >> > Very confused,
> > >> >
> > >> > Mike
> > >> >
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||When did this stop being supported? This was the recommended method of
printing reportserver reports from legacy apps like VB6 in RS2000 (and it did
work). If the old version of the control could get the handle to the window,
whay can't the new version? Is there any other way to PRINT a report from a
VB6 app?
BTW, I have a vb6 app with a webbrowser control in it. I use the control's
Navigate2 method to open the report. The user presses the print button to
get a paginated hardcopy. An error pops up "An error occurred during
printing (...)". The only alternative is to ask the user to export to PDF
and then print (shameful).
"Daniel Reib [MSFT]" wrote:
> That is correct. You are using the control in a Web Form app which hosts IE.
> This is not a supported scenario. The print control will not open because
> it can not find a handle to the current window.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <sfboiler@.nospam.nospam> wrote in message
> news:A71F127A-8290-4893-BB77-EA8AFEE1D2B8@.microsoft.com...
> >I deleted and reinstalled the control..
> >
> > Now I get this error:
> >
> > "An error occured trying to get the current window"
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> >> The print control is not supported in a win forms hosted app. It also
> >> sounds like you have a 2000 version of the print control. To get the
> >> 2005
> >> version you will need to manually remove the ActiveX object. (Via
> >> IE->Tools->Internet Option->Settings->View Objects). Then browse to RM
> >> and
> >> click on the print icon again.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> <sfboiler@.nospam.nospam> wrote in message
> >> news:044A5757-6288-4FA1-8D9B-E76CA4488755@.microsoft.com...
> >> > The error seem to be speficially with the print control.. In the same
> >> > application I am able to right click on the browser window and click
> >> > print.
> >> > Everthing prints fine. But when I use the print button in the
> >> > "Reporting
> >> > Services 2005" tool bar. I get the print error.
> >> >
> >> > To reproduce this error..
> >> > 1. create a report in RS 2005.
> >> > 2. Create a windows Application in VS2003 .net framework 1.1 (I use c#)
> >> > 3. Create a form that embeds the web broswer conrtol.
> >> > 4. Call the navigate method to show the report in the browser
> >> > (Also I have the webserver set as local intranet site in security so
> >> > that
> >> > is
> >> > passes credentials automatically)
> >> >
> >> > (Im also only showing the export / page / print toolbar)
> >> >
> >> > 5. click on the print icon on the report tool bar.
> >> >
> >> > Thats where I get the error.
> >> >
> >> > im usuing 2003 server with reporting services..
> >> > and XP sp2, IE 6.0.2900.2180
> >> >
> >> > Bill
> >> >
> >> > "Steven Cheng[MSFT]" wrote:
> >> >
> >> >> Hi Sfboiler,
> >> >>
> >> >> Welcome to MSDN newsgroup.
> >> >> From your description, you use the IE WebBrowser control in your
> >> >> winform
> >> >> application which navigate to a certain reporting service's report
> >> >> page
> >> >> and
> >> >> let the winform app user print the report. However, you found that
> >> >> you'll
> >> >> get an errro "An error occured during printing (0x8007F304)" when try
> >> >> printing the reprot through the "printing" button on the page, but
> >> >> this
> >> >> works well when we navigate the reprot through external IE window,
> >> >> yes?
> >> >>
> >> >> Based on my local testing, seems a normal report can be printed
> >> >> correctly
> >> >> both through the IE WebBrowser control and external IE window.... So
> >> >> this
> >> >> problem is related to the specific envrionment or application. Since
> >> >> the
> >> >> reporting service's reprot page's print button also use some script to
> >> >> execute the print command, I'd suggest you also try directly using the
> >> >> WebBrowser's print command to print the current document to see
> >> >> whether
> >> >> you
> >> >> can correctly print it. e.g:
> >> >>
> >> >> private void btnPrint_Click(object sender, System.EventArgs e)
> >> >> {
> >> >> mshtml.HTMLDocument doc = axWB.Document as mshtml.HTMLDocument;
> >> >>
> >> >> if(doc != null)
> >> >> {
> >> >> //doc.execCommand("Print", true, 0);
> >> >>
> >> >> axWB.ExecWB(SHDocVw.OLECMDID.OLECMDID_PRINT,SHDocVw.OLECMDEXECOPT.OLECMDEXEC
> >> >> OPT_PROMPTUSER);
> >> >> }
> >> >> }
> >> >>
> >> >>
> >> >> If this also fails, I'm afraid there must have something incorrect
> >> >> with
> >> >> the
> >> >> browser's script engine or else...
> >> >>
> >> >> In addition, you can also check the reporting service's serverside log
> >> >> (under ....\Reporting Services\LogFiles folder) to see whether
> >> >> there're
> >> >> anything incorrectly for the reporter's generating....
> >> >>
> >> >> If there're anything else found, please feel free to post here.
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Steven Cheng
> >> >> Microsoft Online Support
> >> >>
> >> >> Get Secure! www.microsoft.com/security
> >> >> (This posting is provided "AS IS", with no warranties, and confers no
> >> >> rights.)
> >> >>
> >> >>
> >> >> --
> >> >> | Thread-Topic: An error occured during printing or An error occurred
> >> >> during print
> >> >> | thread-index: AcX+c6CWzuG9ppc2S3ekdUXsIh9hsw==> >> >> | X-WBNR-Posting-Host: 67.109.68.162
> >> >> | From: "=?Utf-8?B?c2Zib2lsZXJAbm9zcGFtLm5vc3BhbQ==?="
> >> >> <sfboiler@.nospam.nospam>
> >> >> | Subject: An error occured during printing or An error occurred
> >> >> during
> >> >> print
> >> >> | Date: Sun, 11 Dec 2005 08:55:02 -0800
> >> >> | Lines: 20
> >> >> | Message-ID: <25C4730C-D1B0-46A8-BBF7-92DC5CCFAA7A@.microsoft.com>
> >> >> | MIME-Version: 1.0
> >> >> | Content-Type: text/plain;
> >> >> | charset="Utf-8"
> >> >> | Content-Transfer-Encoding: 7bit
> >> >> | X-Newsreader: Microsoft CDO for Windows 2000
> >> >> | Content-Class: urn:content-classes:message
> >> >> | Importance: normal
> >> >> | Priority: normal
> >> >> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >> | Xref: TK2MSFTNGXA02.phx.gbl
> >> >> microsoft.public.sqlserver.reportingsvcs:64792
> >> >> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >> |
> >> >> | I get the following error when using the print button on the HTML
> >> >> view
> >> >> of
> >> >> a
> >> >> | report with reporting services 2005.
> >> >> |
> >> >> | "An error occured during printing (0x8007F304)"
> >> >> |
> >> >> | I have a windows application written in VS2003 .net 1.1 and it loads
> >> >> a
> >> >> | webcontrol to show and print the reports. I am using the URL syntax
> >> >> to
> >> >> view
> >> >> | the report. The report views ok, but when the user clicks the print
> >> >> button,
> >> >> | they get the error.
> >> >> |
> >> >> | When I run the report via the report manager, I am able to print
> >> >> directly
> >> >> in
> >> >> | the browser.
> >> >> |
> >> >> | Im running XP SP2.
> >> >> |
> >> >> | The application I wrote is running under my windows credentials, And
> >> >> I
> >> >> have
> >> >> | rights to print to all the printers.
> >> >> |
> >> >> | Also.. when I click print, the print dialog doesnt come up.. just
> >> >> get
> >> >> the
> >> >> | error
> >> >> |
> >> >>
> >> >>
> >>
> >>
> >>
>
>
|||