Re: Login failed for user '(null)'. Reason: Not associated with a
- From: Paul Clement <UseAdddressAtEndofMessage@xxxxxxxxxxxxxx>
- Date: Mon, 22 Jan 2007 08:30:07 -0600
On Fri, 19 Jan 2007 14:49:01 -0800, Jon in Canby Or. <JoninCanbyOr@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
¤ Problem solved!
¤
¤ Talk about a red herring! The problem solution seemed to be to go into the
¤ web.config file and change the compilation option "debug=true" to
¤ "debug=false" because the Build option was set to "release". If this truly
¤ was the cause of the problem it sure would save a lot of people's time if the
¤ error message was a little more intelligent.
¤
Well it's definitely a red herring because that setting should have no affect on your ability to
connect. ;-)
More than likely you changed another configuration setting such as the web apps security mechanism
or another web.config setting.
Paul
~~~~
Microsoft MVP (Visual Basic)
.
- References:
- Login failed for user '(null)'. Reason: Not associated with a trus
- From: Jon in Canby Or.
- Re: Login failed for user '(null)'. Reason: Not associated with a trus
- From: William \(Bill\) Vaughn
- Re: Login failed for user '(null)'. Reason: Not associated with a
- From: Jon in Canby Or.
- Re: Login failed for user '(null)'. Reason: Not associated with a
- From: Jon in Canby Or.
- Login failed for user '(null)'. Reason: Not associated with a trus
- Prev by Date: Re: after network drop i get ora-03114 not connected to oracle
- Next by Date: Re: MSAccess DB and DataSets - help
- Previous by thread: Re: Login failed for user '(null)'. Reason: Not associated with a
- Next by thread: ExecuteXMLReader
- Index(es):