Can't turn off Resource Pooling

[Anil Gupte]

I got this error:
General network error. Check your network documentation.

So, I looked around and I found this:
http://support.microsoft.com/defaul...port/kb/articles/Q229/5/64.asp&NoWebContent=1

I added as below:
<configuration>
<appSettings>
<add key="ConnectionString" value="server='(local)'; OLE DB Services = -2;
trusted_connection=true; integrated security=SSPI; database='WroxUnited'" />
</appSettings>

Now I get an error saying the OLE DB keyword is not supported. What gives?

Thanx,

 

[Marc Gravell]

Well, "general network error" is a little vague to be leaping down
*any* route without more info.

Do you genuinely think that this is related to pooling? Or did you get
this from the article you quoted? For reference, to disable ADO.NET
(SqlConnection) pooling you add "Pooling=false;" to the connection
string (http://msdn2.microsoft.com/en-us/library/
system.data.sqlclient.sqlconnection.connectionstring.aspx).

Pooling is generally a good thing; have you a specific reason to
disable it? And is it just a case of not properly closing your
connections?

First stab - have you genuinely got line-of-sight between the
machines? firewalls, etc can be at fault. The article you have cited
is an old ADO article, not ADO.NET; so it *might* (although I
personally doubt it) help *if* you are using to the ADODB provider
(i.e. OleDbConnection). It isn't clear (since you aren't using the
normal connectionStrings configuration element) what provider you are
currently using - I'll guess at SqlConnection / ADO.NET, in which case
I don't think the article applies at all.

Marc

 

[Anil Gupte]

Ouch! Actually, I read an article where the poster had the identical
problem
http://www.sqljunkies.com/WebLog/orfda/archive/2003/10/22/295.aspx

and it seemed to fix his/her problem, so I figured that was it.

This is a SQL server running on the same machine as the app (Windows XP with
..Net 2003 Enterprise Architect - it comes with a basic SQL Server).