Task Scheduler result code 0xc0000025

[Guest]

What is result code 0xc0000025? I can run the particular program I am trying to schedule manually, but any attempt to run it as a scheduled task results in this code

The MS KB says the full list of result codes is available on MSDN, but a search of MSDN does not return a full list.

 

[Jason Hall [MSFT]]

--------------------

From: "=?Utf-8?B?QnJpYW4=?=" <[email protected]>
Subject: Task Scheduler result code 0xc0000025
Date: Mon, 7 Jun 2004 07:06:03 -0700

What is result code 0xc0000025? I can run the particular program I am

trying to schedule manually, but any attempt to run it as a scheduled task
results in this code.

The MS KB says the full list of result codes is available on MSDN, but a
search of MSDN does not return a full list.---------------------

The result code can be deciphered using the "Err" utility from the resource
kit.
Here is the output for this particular error:

# for hex 0xc0000025 / decimal -1073741787 :
STATUS_NONCONTINUABLE_EXCEPTION
# {EXCEPTION}
# Cannot Continue
# Windows cannot continue from this exception.
# 1 matches found for "c0000025"

As you can see, it isn't too helpful.

Regarding your issue:
- Is the task running under the same credentials as the user that is logged
in at the time?
- If not, and the task is interactive (that is, it provides some kind
of user interface) then it will not run. This is for security reasons
- Also, in order for a user account to run a task and not be logged
in, they need to have the "Log on as a batch job" user right in Group Policy
(start > run > gpedit.msc > Computer Configuration > Wdinows
Settings > Security Settings > Local Policies > User Rights Assigment)



--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Guest]

The task cannot be run under the same credentials as the logged-in user because it is started via a terminal services session, and if I use the same credentials for the task as for the TS session, then the task stops when I log off the TS session

The task does have an interactive component, but the developer has provided a auto-start command-line switch that bypasses or automates that interactive component so that it could be run without user intervention

The user is in the local admins group on this server and therefore inherits the "Log on as a batch job" right. The user shows up on the list of users having that right in the Local Security Policy.

 

[Jason Hall [MSFT]]

--------------------

From: "=?Utf-8?B?QnJpYW4=?=" <[email protected]>
Subject: RE: Task Scheduler result code 0xc0000025
Date: Wed, 9 Jun 2004 14:31:02 -0700

The task cannot be run under the same credentials as the logged-in user

because it is started via a terminal services session, and if I use the
same credentials for the task as for the TS session, then the task stops
when I log off the TS session.

The task does have an interactive component, but the developer has provided
a auto-start command-line switch that bypasses or automates that
interactive component so that it could be run without user intervention.

The user is in the local admins group on this server and therefore inherits
the "Log on as a batch job" right. The user shows up on the list of users
having that right in the Local Security Policy.---------------------

Check to see if your DCOM permissions are too restrictive to allow the job
to be run....
1. Start > Run > DCOMCNFG
2. On the Default Security tab:
Default Access Permissions > Edit Default > Add > Everyone > Add >
OK > OK
Default Launch Permissions > Edit Default > Add > Everyone > Add >
OK > OK
3. Click OK, and try to run the scheduled task

Regarding the "interactive component": I am not sure, given the nature of
this "switch", whether or not the application will still be regarded as
"interactive" by the system. If the application is regarded as
non-interactive, then the above may resolve your issue.

Also, if you get any application or system errors in the Event Viewer,
please post them

Thanks, I hope this helps


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.