RSClientPrint issue and its resolution

For the record, and for anyone else this issue might affect...
We have an intranet application that uses RSClientPrint to display a
variety of reports from a particular web application. The
RSClientPrint object worked properly on some people's PCs, but on
others it would appear to hang for 15 minutes or more before finally
giving an error message "An error occured during printing.
(0x800C000B).
After scratching our heads over this for 3 business days, we
investigated the difference between those PCs where RSClientPrint
works, and those where it did not work.
The solution is that in IE, HTTP 1.1 must be enabled. In IE, go to
Tools - Options, Advanced tab, and scroll down to HTTP 1.1 settings.
Make sure that "Use 1.1" is checked.Interesting. I'm saving this posting. Not intuitive at all. Thanks for
letting us know.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rod" <RodEarly@.gmail.com> wrote in message
news:1169568932.741442.177430@.l53g2000cwa.googlegroups.com...
> For the record, and for anyone else this issue might affect...
> We have an intranet application that uses RSClientPrint to display a
> variety of reports from a particular web application. The
> RSClientPrint object worked properly on some people's PCs, but on
> others it would appear to hang for 15 minutes or more before finally
> giving an error message "An error occured during printing.
> (0x800C000B).
> After scratching our heads over this for 3 business days, we
> investigated the difference between those PCs where RSClientPrint
> works, and those where it did not work.
> The solution is that in IE, HTTP 1.1 must be enabled. In IE, go to
> Tools - Options, Advanced tab, and scroll down to HTTP 1.1 settings.
> Make sure that "Use 1.1" is checked.
>|||Hi Rod,
I am having the EXACT same problem you were having except that I have
"Use HTTP 1.1" already checked. Any other ideas?
Thanks,
Brian
"Rod" wrote:
> For the record, and for anyone else this issue might affect...
> We have an intranet application that uses RSClientPrint to display a
> variety of reports from a particular web application. The
> RSClientPrint object worked properly on some people's PCs, but on
> others it would appear to hang for 15 minutes or more before finally
> giving an error message "An error occured during printing.
> (0x800C000B).
> After scratching our heads over this for 3 business days, we
> investigated the difference between those PCs where RSClientPrint
> works, and those where it did not work.
> The solution is that in IE, HTTP 1.1 must be enabled. In IE, go to
> Tools - Options, Advanced tab, and scroll down to HTTP 1.1 settings.
> Make sure that "Use 1.1" is checked.
>