Re: Windows authentication on SQL server

From: Kevin Burton (KevinBurton_at_discussions.microsoft.com)
Date: 10/21/04 

Date: Thu, 21 Oct 2004 09:26:23 -0700

I was following this thread as I think I have a similar problem. I looked in
Services and found SQLSERVERAGENT, MSSQLSERVER, and MSSQLServerADHelper.
Would I set all of these services to use a domain account? I am not sure what
each of these services do.

Would this be why when I run a service on another machine as *just* a domain
user I get SQL login failures? When I run the service on another machine as a
domain admin I don't get the SQL login failures.

Thank you for this clarification.

"Jeff Dillon" wrote:

> Control Panel, Administrative tools, Services. Right click on the SQL
> service, and change the login user from System to a domain user account
>
> Jeff
>
> "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: Utter madness!
    ... It is just Windows security stuff. ... You can get a trusted connection back to SQL server. ... ASP.NET account (either processModel or app pool identity depending on ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Passthrough authenication w/ SQL trusted connection
    ... separate connection will be used for each security context (each user ... account will have it's own pool). ... if you are using a Windows 2000 Domain, ... backend SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Search services not available
    ... Let me clarify that our SQL server uses Windows Authentication, ... account, even if it was just for now to get it working, that would be easier ... I have configured the Search service to use this ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Permissions!
    ... This account is used because your web ... application is configured for anonymous access instead of integrated ... The details on how to use Windows ... SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • connecting to sql server with windows authentication
    ... using windows authentication. ... Use delegation to leverage the current user's account. ... development machine, a live machine, and local installs of IIS for all your ... our DBA wants to keep SQL Server authentication ...
    (microsoft.public.dotnet.framework.aspnet.security)