Stephan wrote:Why are you passing a user id and password while setting trusted connection> Hi all,
> maybe someone can help me out. I have installed an ASP-App, using a
> W2K server, IIS 5.0, MDAC 2.8, MS SQL 2000. I got the app running once
> (first time onley), but after that I keep getting this error message.
> "ADODB.Command (0x800A0E7D) Requested operation requires an OLE DB
> Session object, which is not supported by the currentprovider".
> Whatever I tried, nothing helped. Initialy MDAC 2.5 was installed. So
> I upgraded to 2.8 but this didn't help. I found some post here about
> the issue, but none of the suggestions help. Het is the code that I
> ConnectString = "Provider=sqloledb;Data Source=127.0.0.1;Initial
> Catalog=HKT30;UID=HKT30USER;PWD=HKT30USER;Trusted_ Connection=Yes;"
to yes? I suspect you actually have a SQL login created called HKT30USER, so
you really don't want to be using a trusted connection - remove that part of
the connection string. Go to [url]www.able-consulting.com/ado_conn.htm[/url] for
examples of OLEDB connection strings.
The line should be:>
> Set objConn = Server.CreateObject("ADODB.Connection")
> objConn.Open ConnectString
> Set cmdSP = Server.CreateObject("ADODB.Command")
> cmdSP.CommandText = strStoredProcedure
> cmdSP.CommandType = adCmdStoredProc
> cmdSP.ActiveConnection = objConn <== This is the line on which the
> error is created
Set cmdSP.ActiveConnection = objConn
Without the Set keyword, a new Connection is being created using the
connection string property of the objConn connection.
I've never seen this error. Let us know if the above suggestions fix the
problem. The only other thing I can think of is that OLEDB Session Pooling
on this particular machine has been turned off. Go to
to see an explanation of how to turn session/resource pooling on.
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the