|
Posted by e v t on November 27, 2006, 9:08 am
Please log in for more thread options Hi Roger,
Thanks for the info. What I don't understand is why it works perfectly
when the task is run as Administrator. I've tried assigning the account
I'm using to be in the Administrators group, removing all other groups,
and assigning the permissions in Local Security Policy. I'm trying to
figure out what other permissions the Administrator has that are not
obvious. Does this make sense?
-eric
Roger Abell [MVP] wrote:
> I have seen that odd, unicode-ish, proc id in these failure events
> on W2k3 R2 systems. In each case I have tracked it only so
> far as due to excessive network restrictions (ipsec, firewall)
> on communications either by the machine with itself or with
> the domain controllers. I have not pinned it down to exactly
> what, which protocol/ports. Similarly when I last attempted
> searches for info on the failure with odd logon process id,
> I turned up nothing specific.
>
>
>> I have a question about Scheduled Tasks on Windows 2003 Server. I've got
>> several scheduled tasks that are exhibiting some strange behavior. They
>> appear to run and don't issue any errors in the scheduled tasks log, yet
>> they seem to be having permissions problems. Here's an example...
>>
>> There's a job that's configured to run under a specific user. The user
>> has "Log on as a service" and "Log on as a batch job" permissions. When I
>> run the job, no errors are reported in the 'SchedLgU.txt' file. However,
>> the application that I'm running via the Scheduled Task has its own log
>> which states, "Access is denied". When I change the user to
>> 'Administrator', the job works just fine. I've tried adding the user who
>> runs the job into the Administrators group, but this doesn't appear to
>> work, either. I notice in the Security Event Log that when the job is run
>> under the other user, the following shows up:
>>
>> Logon Failure:
>> Reason: An error occurred during logon
>> User Name: task_user
>> Domain: SERVER1C
>> Logon Type: 3
>> Logon Process: Ðùl
>> Authentication Package: NTLM
>> Workstation Name: SERVER1C
>> Status code: 0xC000006D
>> Substatus code: 0x0
>> Caller User Name: -
>> Caller Domain: -
>> Caller Logon ID: -
>> Caller Process ID: -
>> Transited Services: -
>> Source Network Address: 192.168.1.20
>>
>> The only strange thing I can see above is the 'Logon Process' output.
>> What's up with that?
>>
>> The scheduled jobs worked fine under Windows 2000. I've been pulling my
>> hair out over this for the past two days and I know it's got to be
>> something simple. Can anyone assist, please?
>>
>> Thanks in advance for any assistance you can provide.
>>
>> -evt
>
>
| 
XML Sitemap