Re: Login failed for user '(null)'. Reason: Not associated with a
- From: boy <boy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Apr 2005 18:50:04 -0700
yes, i used impersonation <identity impersonate="true"/> in the web.config.
if i didn't, all accounts, userA and userB should failed to connect to
database.
however, acount, userA can access succesfully!
the database is installed on another machine from the web application.
"Scott Allen" wrote:
> Is the database on the same machine?
> Are you using impersonation <identity impersonate="true"/> ?
>
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
>
> On Fri, 29 Apr 2005 02:32:14 -0700, boy
> <boy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >I got the following error message when I access the web application, in which
> >the web application use SPPI to connect to database.
> >
> >"Login failed for user '(null)'. Reason: Not associated with a trusted
> >connection"
> >
> >The web application is grant to a group only in web.config
> > <authorization>
> > <allow roles="Domain\AGroup" />
> > <deny users="*" />
> > </authorization>
> >
> >I have two 2 accounts, userA and userB, which belong to the same group
> >"Domain\AGroup". userA can access the web application successfully, whereas
> >userB cannot and prompted the above error.
> >
> >Do all you have encountered the same problem?
> >
> >Thanks!
>
>
.
- Follow-Ups:
- Re: Login failed for user '(null)'. Reason: Not associated with a
- From: Patrick Olurotimi Ige
- Re: Login failed for user '(null)'. Reason: Not associated with a
- References:
- Prev by Date: Re: Best practices in ASP.NET application development
- Next by Date: RE: databinding xml to dropdownlist
- Previous by thread: Re: Login failed for user '(null)'. Reason: Not associated with a trus
- Next by thread: Re: Login failed for user '(null)'. Reason: Not associated with a
- Index(es):
Relevant Pages
|
