Re: Windows authentication on SQL server
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 10/20/04
- Next message: Kalevet: "Re: Reasons for an exception thrown at "new""
- Previous message: Polaris: "Re: How to load String from one of the string tables"
- In reply to: Bonj: "Re: Windows authentication on SQL server"
- Next in thread: Jeff Dillon: "Re: Windows authentication on SQL server"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 20 Oct 2004 18:37:15 +0200
I think it was my mistake that I was unclear. AFAIK, you *cannot* have anything that executes as
LocalSystem do any type of Windows authentication against another machine. So, make sure you change
the service account to a domain account, or make you extended procedure do a SQL server logins...
-- 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:2C456CAC-4EEF-440A-8190-1A8180CE28C4@microsoft.com... > 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 >> > >> > >> >> >>
- Next message: Kalevet: "Re: Reasons for an exception thrown at "new""
- Previous message: Polaris: "Re: How to load String from one of the string tables"
- In reply to: Bonj: "Re: Windows authentication on SQL server"
- Next in thread: Jeff Dillon: "Re: Windows authentication on SQL server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
