Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Prashant (barnwal_p_at_hotmail.com)
Date: 10/06/04 

Date: Wed, 6 Oct 2004 16:39:21 +0530

Hi,
I removed TCP/IP and faced enumerable problems. however I can give yu more
insight, what is happening whenever I run util.exe as a standalone
application its running under the logged in user account but if it is run by
Setup.exe, it runs under system account, that is causing the problem with
the connection. can you suggest what to do next? how to impersonate so that
it runs under logged in user Account?

Thanks,
Prashant

"Steve Thompson" <stevethompson@nomail.please> wrote in message
news:#vE4tciqEHA.708@tk2msftngp13.phx.gbl...
> "Prashant" <barnwal_p@hotmail.com> wrote in message
> news:%23aGwm5EqEHA.3324@TK2MSFTNGP15.phx.gbl...
> > I have a windows setup program (framework 1.1), this setup
> > program calls one util.exe with parameters. util.exe opens the
connection
> > (SQL Server 2000, windows authentication only) and does some db
> updations.
> > when i run thru setup exe fails throwing
> > "Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > Server connection" error. if i run the exe separately thru command line
> > argument, it executes properly.
> > To add to this, problem only comes with Windows 2003 domain, not with
> > windows 2000 domain.
> >
> > does anyone has any idea whats happening behind the scene?
>
> This seems to pop up a lot, what happens if you remove the SQL Server
> network library TCP/IP? (Make sure that Named Pipes is still enabled on
both
> client and server).
>
> Steve
>
>