Re: login failed for user ... Not Associated with a trusted SQL Server
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Tue, 02 Aug 2005 17:56:59 -0600
In your connection string, you are specifying parameters for
both SQL authentication and Windows authentication - it
needs to be one or the other. If you use Windows
authentication, you don't specify a user id and password.
You can find some examples at:
http://www.carlprothman.net/Default.aspx?tabid=86#SQLClientManagedProvider
-Sue
On Tue, 2 Aug 2005 07:56:11 -0700, Christian F CLY
<ChristianFCLY@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Hello,
>
>I'm trying to connect a mobile computer runing under windows CE to a
>database located on a windows XP desktop.
>The mobile computer application is written in C# under Visual Studio .NET
>2003.
>
>My problem occurs when I execute mConnection.Open();
>
>A SqlException is caught with this message :
>Login failed for user '(null)'. Reason : Not associated with a trusted SQL
>Server connection.
>
>here is the connection string :
>mConnection = new SqlConnection("User ID=sa;data source=" + mSqlServer +
>";Integrated Security=SSPI;initial catalog=IDPS;Password=xxxx;persist
>security info=false;Trusted_Connection=yes");
>
>What can I do to correct it ?
.
- Follow-Ups:
- Re: login failed for user ... Not Associated with a trusted SQL Se
- From: Christian F CLY
- Re: login failed for user ... Not Associated with a trusted SQL Se
- References:
- login failed for user ... Not Associated with a trusted SQL Server
- From: Christian F CLY
- login failed for user ... Not Associated with a trusted SQL Server
- Prev by Date: SQL server not opening sockets on Opteron 64-bit server
- Next by Date: Re: Server Service not start
- Previous by thread: login failed for user ... Not Associated with a trusted SQL Server
- Next by thread: Re: login failed for user ... Not Associated with a trusted SQL Se
- Index(es):
Relevant Pages
|