The only difference between the local system account and a "regular" NT
account is what I outlined. If you are positive that the procedure runs
under a regular NT account, but not under the local system account, then it
would seem very strong evidence that somewhere, somehow in the task that is
failing, there is a reference to a network resource.
From the information that you have provided, that is the only logical
conclusion. This does not preclude the task failing for another reason
having nothing to do with the account under which SQL Executive is running.
But, to make the point again, from the information you have provided, the
only logical conclusion is the one I provided. If are absolutely sure that
the reason I provided is not the correct one, then perhaps you can supply
> The database server and SQL Executive are running locally on the machine.
> There should be no need to access network resources.
> We have 6 other servers running SQL Server, with SQL Executive running
> under the local system account. We have no problems with those.
> The task runs a user defined stored procedure, which just updates
> statistics for about 10 tables locally.
> Thank you,
> > Jeff,
> > The local system account has no rights or privileges outside of the
> > box. So, for example, it cannot access data located on the network.
> > > When I try to run tasks on a server in which the SQL Executive uses
> > > local system account, the tasks do not run. If I create a separate
> > > account for the service to run under, it works fine.
> > > Can someone tell me what may be causing the problem when using the
> > > system account?
> > > --
> > > Posted via CNET Help.com
> > > http://www.help.com/
> Posted via CNET Help.com