RE: Login failed for user '(null)'.
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Fri, 28 Jul 2006 03:41:39 GMT
Thanks for your response Herb,
As you said it runs fine on development machine, are you using file system
based project and run the application in VS 2005 Test WebServer instead of
IIS? If so, this is expected because when using TestWebServer, the
server(WebDev.WebServer.exe) and our ASP.NET application is running under
the current logon user's identity which is generaly a powerful account and
have sufficient permission for both local and remote resources. Does this
make sense to your case?
Since you can make sure that it is the non-aspnetdb connection that fails,
you can create a simple test page which access the remote database through
the certain connectionstring.(I've seen that you're using windows
authentication for all those SQL connection strings) Thus, you can
concentrate on this test page according to the troubleshoot tips I
mentioned in the last message.
Anyway, if you have anything unclear in my pervious reply or meet any
further difficulties, please feel free to let me know.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- RE: Login failed for user '(null)'.
- From: Steven Cheng[MSFT]
- RE: Login failed for user '(null)'.
- From: Herb
- RE: Login failed for user '(null)'.
- Prev by Date: Problems with Process.Start
- Next by Date: Disable NT Windows Login for asp.net
- Previous by thread: RE: Login failed for user '(null)'.
- Next by thread: RE: Login failed for user '(null)'.
- Index(es):