Task Scheduler Jobs Do Not Work and Generate Error Code 0x8004130f Intermittently (328773)
The information in this article applies to:
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q328773 SYMPTOMS If you are running many Task Scheduler jobs each
day by using a user account on a multiprocessor computer, and if some of the jobs run
multiple times a day, the jobs may intermittently lose their credentials and not run. When this occurs, you find entries that are similar to these in the Schedlgu.txt file in the Windows folder:
"Job Name" (Program) Time Stamp ** ERROR **
The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.
The specific error is:
0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.
If you open the properties for the affected jobs, you
see that the account that you are logged on with is specified as the account that the
job runs under, no matter which account was specified before. CAUSE In a rare combination of circumstances, the credential database that Task Scheduler uses may become corrupted. The credentials are removed when the corruption is detected. The user interface shows the current user name in the job properties when you open a job after it loses its credentials.RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported
fix is now available from Microsoft, but it is only intended to correct the
problem that is described in this article. Apply it only to computers that are
experiencing this specific problem. This fix may receive additional testing.
Therefore, if you are not severely affected by this problem, Microsoft
recommends that you wait for the next Windows 2000 service pack that contains
this fix. To resolve this problem immediately, contact Microsoft
Product Support Services to obtain the fix. For a complete list of Microsoft
Product Support Services phone numbers and information about support costs,
visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Support Professional determines
that a specific update will resolve your problem. The typical support costs
will apply to additional support questions and issues that do not qualify for
the specific update in question. The English version of
this fix has the file attributes (or later) that are listed in the following
table. The dates and times for these files are listed in coordinated universal
time (UTC). When you view the file information, it is converted to local time.
To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
-------------------------------------------------------
15-Jan-2003 19:13 4.71.2195.6654 123,664 Mstask.exe
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft Windows 2000 Service Pack 4.winseraid2:34110winseraid2:34396
Modification Type: | Minor | Last Reviewed: | 10/11/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbSysAdmin kbWin2kSP4fix kbbug kbfix kbWin2000preSP4Fix KB328773 |
---|
|