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.
>

RS2005 crashing...stupid error

For some reason, our reports will just stop working...randomly.
It basically tells us it can't connect to our record sets. The report works
in the designer.
Also, if we re-deploy the report it starts working! Even if we don't change
anything it sometimes stops. Then, we re-deploy and it works.
What gives?
This is with different users and different reports.
Thanks!
-cbmeeksSorry to bump this but it is really becoming a problem.
At random, our reports just stop working. With different error messages.
Sometimes, it can't find a stored procedure. Sometimes, it can't find a
table. It's like the report is loosing its connection with the server.
I have confirmed the stored procedure/tables/etc are there and working. All
other apps access the data just fine. The newest SP has been installed on
the server.
Any clues?
Here is a copy of the error message:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'Customers'. (rsErrorExecutingCommand)
Could not find stored procedure 'dbo.up_get_customer_list_with_All'.
The last line changes. Sometimes it can't find a stored procedure,
sometimes it can't find a table. Once again, I have confimed they are indeed
there and working.
Thanks
-cbmeeks
"cbmeeks" wrote:
> For some reason, our reports will just stop working...randomly.
> It basically tells us it can't connect to our record sets. The report works
> in the designer.
> Also, if we re-deploy the report it starts working! Even if we don't change
> anything it sometimes stops. Then, we re-deploy and it works.
> What gives?
> This is with different users and different reports.
> Thanks!
> -cbmeeks