Article ID: 887572 - View products that this article applies to.
On a Microsoft Windows XP-based computer, a scheduled task that is running under a specific account cannot access a shared network resource. This symptom occurs when the following conditions are true:
When the Task Scheduler service runs a job by using a specific account, the Task Scheduler service tries to determine whether this account is also the account of the current logged-on user. If the account is that of the current logged-on user, the security context of the scheduled task is mapped to the security context of that user. This process directs scheduled jobs to that user's desktop.
Additionally, if the scheduled task user account is the account of the current logged-on user, and if that user uses a smart card to log on, the network access attempt by the scheduled task may fail. This network access failure occurs when the TGT ticket is expired. In this scenario, the TGT update process fails. Because the security context comers through a smart card logon, the TGT update process requires that the user provide a PIN. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
323931Note Assume that the TGT update process fails because the user did not type a PIN. In this scenario, the NTLM authentication protocol is not used, even if the Simple and Protected GSS-API Negotiation (SPNEGO) security package is used. For more information about SPNEGO, visit the following IETF Web site:
(http://support.microsoft.com/kb/323931/ )User token expires when you log on by using a smart card for a long time
A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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:
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) 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.
Windows XP Service Pack 1 (SP1)
Date Time Version Size File name -------------------------------------------------------------- 30-Apr-2005 01:43 5.1.2600.1677 258,560 Mstask.dll 29-Apr-2005 23:40 5.1.2600.1677 10,752 Mstinit.exe 30-Apr-2005 01:43 5.1.2600.1677 173,568 Schedsvc.dll 29-Apr-2005 23:47 5.1.2600.1677 594,432 Xpsp2res.dll
Windows XP Service Pack 2 (SP2)
This hotfix creates the following new registry subkey:
Date Time Version Size File name -------------------------------------------------------------- 30-Apr-2005 01:07 5.1.2600.2667 192,000 Schedsvc.dll
This subkey lets you disable the correlation between the following two items:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.