Microsoft KB Archive/250543: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 56: Line 56:
== CAUSE ==
== CAUSE ==


Package Command Manager is used to run packages while a user is not logged on. After a job is run, the instruction file is modified to show a year and date of "00/00/00 00:00:00." Package Command Manager interprets this date as "Thursday, October 06, 2033 11:55:01." This date prevents the package from running again. This issue is not known to cause any problems.
Package Command Manager is used to run packages while a user is not logged on. After a job is run, the instruction file is modified to show a year and date of "00/00/00 00:00:00." Package Command Manager interprets this date as "Thursday, October 06, 2033 11:55:01." This date prevents the package from running again. This issue is not known to cause any problems.


</div>
</div>
Line 76: Line 76:
== STATUS ==
== STATUS ==


Microsoft has confirmed that this is an issue in the Microsoft products that are listed in the &quot;Applies to&quot; section.
Microsoft has confirmed that this is an issue in the Microsoft products that are listed in the "Applies to" section.


</div>
</div>

Latest revision as of 13:52, 21 July 2020

Knowledge Base


The InstallByDate entry in Pacman.log indicates the year 2033

Article ID: 250543

Article Last Modified on 10/25/2006



APPLIES TO

  • Microsoft Systems Management Server 1.2 Standard Edition



This article was previously published under Q250543


SYMPTOMS

When Package Command Manager is installed, and you send a Run Command On Workstation job, Package Command Manager runs the command successfully, but the InstallByDate entry in Pacman.log indicates the year 2033.

CAUSE

Package Command Manager is used to run packages while a user is not logged on. After a job is run, the instruction file is modified to show a year and date of "00/00/00 00:00:00." Package Command Manager interprets this date as "Thursday, October 06, 2033 11:55:01." This date prevents the package from running again. This issue is not known to cause any problems.

RESOLUTION

To resolve this issue, install the hotfix that is mentioned in the following Microsoft Knowledge Base article:

241656 SMS: Memory leak in Pcmsvc32


STATUS

Microsoft has confirmed that this is an issue in the Microsoft products that are listed in the "Applies to" section.


Additional query words: PCMSVC32

Keywords: kbbug kbfix kbqfe KB250543