Package source files are not copied to a child site's distribution point in Systems Management Server 2003 (886153)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

You create a new package on a Microsoft Systems Management Server (SMS) 2003 central site, and the new package appears on the child site. However, when you add one of the child site's distribution points to the package properties on the central site, the package source files are not copied to the child site's distribution point. Additionally, the package properties on the child site do not include the distribution point. When this problem occurs, the Distmgr.log file on the central site may contain entries that are similar to the following.

Note In this example entry, xxx is the central site code and yyy is the child site code.
~Needs to send the compressed package for package xxx000D2 to site yyy
~There isn't a copy of compressed copy for package xxx000D2, create it.
~Use drive D for storing the compressed package.
~The size of package xxx000D2 is 7734 KBytes
~Starting to compress \\smsb44dfp\SMSClient\i386 to D:\_S M05kw.TMP for package xxx000D
~Used 1 out of 7 allowed processing threads.
~Sleep 3600 seconds...
~Used 1 out of 7 allowed processing threads.
~Sleep 3600 seconds...
~Used 1 out of 7 allowed processing threads.
~Sleep 3600 seconds...
~Cannot open source file \\smsb44dfp\SMSClient\i386\capinst.exe, Win32 Error = 32
CTool::CompressAndAppendFile failed, error = 3, win32 = 32, filename = (null)
~Cannot compress \\smsb44dfp\SMSClient\i386 to D:\_S M05kw.TMP, last failed file is , Win32 error = 32
STATMSG: ID=2309 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SMSxxxC SITE=xxx PID=3988 TID=1636 GMTDATE=Thu Jul 01 18:55:15.171 2004 ISTR0="xxx000D2" ISTR1="\\smsb44dfp\SMSClient\i386" ISTR2="" ISTR3="D:\_S M05kw.TMP" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="xxx000D2"
~Cannot create the compressed copy for package xxx000D2.
Note Error 32 indicates that a process cannot access a file because the file is being used by another process.

CAUSE

This problem may occur if you add a distribution point to the new package, and one or more package source files are locked by another process.

WORKAROUND

To work around this problem, follow these steps to update the distribution point:
  1. Start the SMS Administrator console.
  2. Double-click the Site Database\Packages container.
  3. Right-click the package, point to All Tasks, and then click Update Distribution Points.
  4. Click Yes to confirm the update task.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbSMSDistribution kbSMS2003bug kbtshoot kbServer kberrmsg kbSoftwareDist KB886153 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.