Re: Windows authentication on SQL server

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 10/20/04 

Date: Wed, 20 Oct 2004 14:03:40 +0200

Make certain that the service account for your SQL Server is added as a login to the other SQL
server.
AFAIK, system account doesn't exist outside the machine, so you cannot add system account from
another machine. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bonj" <Bonj@discussions.microsoft.com> wrote in message
news:2324EB8B-0082-4E6A-9095-0F32D0F34FED@microsoft.com...
> Hello
> In making an extended stored proc, I am trying to use a wizard-generated ATL
> OLEDB consumer class to access data. I've tested this and it works fine when
> run from a standard windows application.
> When I debug the extended stored proc, it connects fine (it is connecting to
> a remote SQL server).
> However, when I deploy it to SQL server and run it from SQL when SQL is
> running as a service, then trying to connect using ATL produces "IDispatch
> error #3149", and an ADODB connection just returns the generic 'Access
> violation occurred' error.
> However I think I know why this is: when debugging, it is working fine
> because it is logged in as me, and I can log in with windows authentication
> to the SQL server on the other machine, but the SYSTEM account can't, which I
> believe is the cause of why it is failing.
>
> My question is, how can I add the SYSTEM account on my development machine
> to the list of people trusted by the windows authentication of SQL server on
> the other machine? It's MSDE so I'm an admin on it, so I can do this - if I
> knew what to do!
>
> Failing this I will create a limited account and hardcode its name into the
> application, but I'd rather not do this if it's possible with windows
> authentication.
>
> Thanks
>
>

Relevant Pages

  • Re: Windows authentication on SQL server
    ... Make certain that the service account for your SQL Server is added as a login to the other SQL ... AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ... > to the list of people trusted by the windows authentication of SQL server on ...
    (microsoft.public.sqlserver.programming)
  • Re: Windows authentication on SQL server
    ... Make certain that the service account for your SQL Server is added as a login to the other SQL ... AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ... > to the list of people trusted by the windows authentication of SQL server on ...
    (microsoft.public.sqlserver.security)
  • Re: Windows authentication on SQL server
    ... > AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ... > Tibor Karaszi, SQL Server MVP ... >> believe is the cause of why it is failing. ... >> to the list of people trusted by the windows authentication of SQL server on ...
    (microsoft.public.vc.language)
  • Re: Windows authentication on SQL server
    ... > AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ... > Tibor Karaszi, SQL Server MVP ... >> believe is the cause of why it is failing. ... >> to the list of people trusted by the windows authentication of SQL server on ...
    (microsoft.public.sqlserver.programming)
  • Re: Windows authentication on SQL server
    ... > AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ... > Tibor Karaszi, SQL Server MVP ... >> believe is the cause of why it is failing. ... >> to the list of people trusted by the windows authentication of SQL server on ...
    (microsoft.public.sqlserver.security)