Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- From: "Henning Krause [MVP - Exchange]" <newsgroups_remove@xxxxxxxxxxxxxxxxx>
- Date: Tue, 25 Mar 2008 23:00:06 +0100
Hello Waldy,
are the Impersonation settings equal on both asp.net applicaitons?
Kind regards,
Henning Krause
"Waldy" <someone@xxxxxxxxxxxxx> wrote in message news:uzn2GnpjIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Hi Henning,
there is already a .ASP application on the web server that is working fine. It is only the ASP.Net application that has this problem.
.
- Follow-Ups:
- References:
- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- From: Waldy
- Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- From: Henning Krause [MVP - Exchange]
- Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- From: Waldy
- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- Prev by Date: Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- Next by Date: Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- Previous by thread: Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- Next by thread: Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- Index(es):
Relevant Pages
|
|