The information in this article applies to:
SYMPTOMSWhen redistributing a package, despooler may report out of disk space in the application event log (Event 109) even though there is sufficient disk space. In addition, the package will not be copied to the distribution point. CAUSEThis problem may occur if a file that already exists in the distribution share point is open or in use when that file is being recopied. WORKAROUNDRestarting the computer that contains the open file will clear file contention issues. If the problem occurs again, it may be necessary to troubleshoot conflicts with backup software, antivirus software, and the file system. STATUSMicrosoft has confirmed this to be a problem in Systems Management Server version 1.2. MORE INFORMATIONThe following event will appear in the Windows NT application event log:
Note that <Server>, <Share>, and <PackageID> above will be the name of your
server, your package distribution share, and the ID of the package you are
sending.
Also note that the amount of disk space required and disk space available is reported as null, or blank. In the despooler log file, Despool.log, an error similar to the following error will be logged:
This error identifies the file that could not be copied. Win32 Error 32
indicates that the process cannot access the file because it is being used
by another process. The file is in use.
Event 109 should indicate that there is a file contention error, or that the file is in use, not that there is a disk space problem. Additional query words: prodsms anti virus
Keywords : smsdespooler kbbug1.20 |
Last Reviewed: September 7, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |