Tuesday, February 21, 2012

Schedule a Job - Access denied

Greetings,
We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a job
that writes data to a text file. This job works fine either manually or
scheduled when writing to a local hard drive. However when writing to the
network the job will work when run manually but not when run scheduled.
I thought the problem has to do with the scheduler not having rights on the
network. The scheduler runs from the system account. When I tried to change
it to a network account I got this message, "Service Schedule could not be
configured to run under a shared process. If computer xxxx in not a Windows
2000 computer, service which run in a shared process must run under the
system account."
Error 1057: the account name is invalid or does not exist, or the password
is invalid for the account name specified.
Any idea how I can get this schedule job to write to the network?
JimJim,
Which service did you change? You need to change the account of the
SQLServerAgent service to use a domain account that has rights to your
network resource.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602_.html
"Jim" wrote:

> Greetings,
> We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a jo
b
> that writes data to a text file. This job works fine either manually or
> scheduled when writing to a local hard drive. However when writing to the
> network the job will work when run manually but not when run scheduled.
> I thought the problem has to do with the scheduler not having rights on th
e
> network. The scheduler runs from the system account. When I tried to chang
e
> it to a network account I got this message, "Service Schedule could not be
> configured to run under a shared process. If computer xxxx in not a Window
s
> 2000 computer, service which run in a shared process must run under the
> system account."
> Error 1057: the account name is invalid or does not exist, or the password
> is invalid for the account name specified.
> Any idea how I can get this schedule job to write to the network?
> Jim
>
>

No comments:

Post a Comment