Article ID: 328773 - View products that this article applies to.
This article was previously published under Q328773
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.
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.
Service 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:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. 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
Microsoft 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.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/265173/EN-US/ )The Datacenter Program and Windows 2000 Datacenter Server Product
Article ID: 328773 - Last Review: February 20, 2007 - Revision: 1.9
Contact us for more help
Connect with Answer Desk for expert help.