Re: Windows authentication on SQL server

From: Bonj (Bonj_at_discussions.microsoft.com)
Date: 10/20/04 

Date: Wed, 20 Oct 2004 05:35:04 -0700

Sorry - I think you missed the gist of the question. I know that's what I've
got to do, I was asking HOW to do it...

"Tibor Karaszi" wrote:

> 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
    ... > 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: Replication problems
    ... The error that you are getting regarding using a system account is fine as ... machine share which you can then reference in the publication wizard. ... > SQL Server Enterprise Manager could not retrieve information about the ...
    (microsoft.public.sqlserver.ce)
  • Re: Windows authentication on SQL server
    ... AFAIK, you *cannot* have anything that executes as ... LocalSystem do any type of Windows authentication against another machine. ... the service account to a domain account, or make you extended procedure do a SQL server logins... ... >> AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ...
    (microsoft.public.vc.language)
  • Re: Windows authentication on SQL server
    ... AFAIK, you *cannot* have anything that executes as ... LocalSystem do any type of Windows authentication against another machine. ... the service account to a domain account, or make you extended procedure do a SQL server logins... ... >> AFAIK, system account doesn't exist outside the machine, so you cannot add system account from ...
    (microsoft.public.sqlserver.programming)