Connection Pool Error

Hello,
I'm having a recurring error whenever I try to debug a
asp.net web page is retrieving data from a SQL server.
The error msg is:
"Timeout expired. The timeout period elapsed prior to
obtaining a connection from the pool. This may have
occurred because all pooled connections were in use and
max pool size was reached."
Any ideas?There were some connection pooling problems in the earlier versions of .NET.
Have you applied the .NET service packs to your boxes?
--Brian
(Please reply to the newsgroups only.)
"Brian" <anonymous@.discussions.microsoft.com> wrote in message
news:041501c3d7ba$5694ff40$a001280a@.phx.gbl...

quote:

---

> Hello,
> I'm having a recurring error whenever I try to debug a
> asp.net web page is retrieving data from a SQL server.
> The error msg is:
> "Timeout expired. The timeout period elapsed prior to
> obtaining a connection from the pool. This may have
> occurred because all pooled connections were in use and
> max pool size was reached."
> Any ideas?
>

---

|||Brian (anonymous@.discussions.microsoft.com) writes:

quote:

---

> I'm having a recurring error whenever I try to debug a
> asp.net web page is retrieving data from a SQL server.
> The error msg is:
> "Timeout expired. The timeout period elapsed prior to
> obtaining a connection from the pool. This may have
> occurred because all pooled connections were in use and
> max pool size was reached."

---

ADO.Net is not my best game, but I know that there are pitfalls, so
if you are not careful, you will fill up your connection pool. One
way to diagnose this is to run sp_who from Query Analyzer, and see
how many connections you have open. If you think you have none,
but there are hundred you know that 1) you have filled up the pool
2) you have a leak.
Explicitly closing your connections is probably a good idea.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Connection Managers not installed?

apologies if this is the wrong group ..

whenever I create an Integrated Services project and attempt to add a Connection Manager I get the error

Connection Manager 'blah' is not properly installed on this computer.

(Microsoft.DataTransformationServices.Design)

This happens with all menu options except New Connection..

I have uninstalled and reinstalled both Visual Studio 2005 and SQL Server 2005 and made sure I have selected everything in each case

what am I missing?

Thanks

Chris

seems this has happened to others

see Jason Lodice thread for solution

Chris

Connection error after copying an rdl

Whenever I make a copy of an existing report (.rdl) in order to use it as a
template for a new report, I get the following error message when I try to
preview it:
An error has occurred during report processing.
Cannot create a connection to data source 'Prospect'
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
The originial copy of the report - in the same project - works without
error. Why is this happening. This requires me to start every report from
scratch, and since I have a lot of parameters and data sources, this is very
tedious.Since specific credential information is not stored in the .rdl so when you
attempt to preview the copied report you'll see this error until you modify
your report DataSource. If you modify your report DataSets to use a shared
DataSource, I don't believe you'll run into this.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jody Z" <Jody Z@.discussions.microsoft.com> wrote in message
news:B95FFD30-F0D5-4FAC-B6C9-6A91DD5DFAA0@.microsoft.com...
> Whenever I make a copy of an existing report (.rdl) in order to use it as
> a
> template for a new report, I get the following error message when I try to
> preview it:
> An error has occurred during report processing.
> Cannot create a connection to data source 'Prospect'
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL
> Server connection.
> The originial copy of the report - in the same project - works without
> error. Why is this happening. This requires me to start every report
> from
> scratch, and since I have a lot of parameters and data sources, this is
> very
> tedious.