RE: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 09/29/04
- Next message: SA Dev: "Re: I can only connect via Windows Auth - WHY?"
- Previous message: Steve Thompson: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- In reply to: Bil: "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- Next in thread: Bil: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- Reply: Bil: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 29 Sep 2004 17:38:20 GMT
Try forcing a Named Pipe connection and see if that succeeds.
osql -Snp:ServerName -E -Q"select @@version"
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
- Next message: SA Dev: "Re: I can only connect via Windows Auth - WHY?"
- Previous message: Steve Thompson: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- In reply to: Bil: "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- Next in thread: Bil: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- Reply: Bil: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
