Re: SQL server does not exist or access denied

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

It's not clear what's running on what box but you can add
the login if you need to:
exec sp_grantlogin 'NT Authority\System'
go
use YourDB
go
exec sp_grantdbaccess 'NT Authority\System'
and whatever access it needs in whichever databases.

That's not necessarily the best way to go about it though.
It sound like your windows service is going to access
network resources so you would want to run under a domain
account - use User for the Account property. Then the domain
account that the service runs under is the account you want
to give the appropriate login and database access.

-Sue

On Fri, 21 Oct 2005 09:56:31 +0100, "Jan Timmer"
<oriolus@xxxxxxxxx> wrote:

>Enric,
>
>> NT AUTHORITY\SYSTEM doesn't exists in sql server
>
>I know but nevertheless the SQL profiler shows a user SYSTEM with loging
>name NT AUTHORITY\SYSTEM, for the Windows Service.
>
>> The user that have the responsability from the asp page for do update have
>> the fine permissions on the selected table?
>
>Yes.
>
>
>Jan
>
>
>Enric <Enric@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in berichtnieuws
>71774958-F12C-46CA-B13F-39A940CD8015@xxxxxxxxxxxxxxxx
>> NT AUTHORITY\SYSTEM doesn't exists in sql server
>> The user that have the responsability from the asp page for do update have
>> the fine permissions on the selected table?
>>
>> "Jan Timmer" wrote:
>>
>> > Hello,
>> >
>> > We have two applications that connect to three SQL databases on another
>> > machine. Both applications access and update the databases.
>> > One application is a web application (ASP.NET) the other one is a
>Windows
>> > service.
>> > The web application runs fine. It accesses and updates all three
>databases
>> > The Windows service is supposed to access and update two of the three
>> > databases. The tables in one database are accessed and updated
>correctly. In
>> > the other database the only table there is can be selected, but when ik
>> > comes to update, a .NET exception is generated (SQL server does not
>exist or
>> > access denied).
>> > When I take a look at the SQL profiler I see that the Windows Service is
>> > logged in as "System" with a login name "NT AUTHORITY\SYSTEM". When I
>take a
>> > look at the users in the database, there is no such user.
>> >
>> > What is the best way for me to go about to solve this problem?
>> >
>> > Thanks in advance.
>> >
>> > Jan
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>
>
>

.

Relevant Pages

  • Re: DomainLocalServer$ is not a valid user
    ... So I understand that it is a bug because SQL Windows Service Account is not ... The workaround to run the SQL Server as the domain user is also not ...
    (microsoft.public.sqlserver.security)
  • Re: denying permissions on the views underlying tables
    ... (running NT4, SP6a). ... see the thread "one SQL DB getting info form another - user ... >>passing between databases on the same server. ... >>account is defined, then that account must have rights. ...
    (microsoft.public.sqlserver.security)
  • RE: Hiding MS SQL databases in Enterprise Manager
    ... Using Enterprise Manager does not inheritly mean that the user ... called to get a list of databases that the user has access to. ... This command takes no permissions into account, ... didn't use that nasty chunk of ad hoc SQL to get the list of databases. ...
    (Focus-Microsoft)
  • Re: SQL server does not exist or access denied
    ... I know but nevertheless the SQL profiler shows a user SYSTEM with loging ... name NT AUTHORITY\SYSTEM, for the Windows Service. ... Both applications access and update the databases. ... >> The Windows service is supposed to access and update two of the three ...
    (microsoft.public.sqlserver.connect)
  • Re: DomainLocalServer$ is not a valid user
    ... the SQL Windows Service Account to execute the transaction. ... As for the access deny issue when you use the domain account as the SQL ... If you use the domain use account as the SQL Server Windows Services ...
    (microsoft.public.sqlserver.security)