Re: Login failed for user 'foo' but the SQL executed correctly

From: Benjamin Joldersma (benj_at_theinsiders.com)
Date: 09/11/03 

Date: 11 Sep 2003 08:52:51 -0700

Thanks Bill, for you quick reply. I'm a bit embarrassed though - I
think it is a code issue, the code my colleague wrote reuses the
existing SqlConnection object, with the SqlHelper class, in the same
method. It seems that this must be the likely source of the problem,
that we are re-using the connection? Maybe the SqlHelper class leaves
it in an invalid state for re-use?

Anyways, I told him to get me a build that explicitly clears the
connection object, so I am going to see if that works first.

Again, thanks for the suggestions. I'll gladly take the help if this
doesn't resolve the issue.

--ben

Relevant Pages

  • Re: Login failed for user foo but the SQL executed correctly
    ... directly uses SqlConnection, SqlCommand, etc. to call the stored procedure. ... | existing SqlConnection object, with the SqlHelper class, in the same ... Maybe the SqlHelper class leaves ... | connection object, so I am going to see if that works first. ...
    (microsoft.public.sqlserver.security)
  • Using SqlConnection object with TransactionScope
    ... A SqlConnection object is created as a member in a class and then used by ... What is desired is to use TransactionScope with TableAdapters however ... according to .NET documentation the creation of the connection object needs ... to be done within the TransactionScope block of code. ...
    (microsoft.public.dotnet.framework.adonet)
  • Database connection object in global area...
    ... I want to create a code module that has a global variable that will ... store a SqlConnection object. ... the overhead in creating the connection object each time a connection ... Is the real overhead involved in ...
    (microsoft.public.dotnet.languages.csharp)