Distribution of Files with Long Filenames Require NTFSLast reviewed: April 15, 1997Article ID: Q139589 |
The information in this article applies to:
SYMPTOMSWhen you attempt to distribute files with long filenames to a NetWare server that has the OS/2 Name Space NLM loaded, the server stops responding and fails to receive the complete distribution of files. In addition, the following error message appears:
SMSEXEC.EXE - Application Error The instruction at <address> referenced memory at <memory address>. The memory could not be written.Some of the Systems Management Server services stop, including the Systems Management Server Executive service. The following event appears in the Systems Management Server application log:
113 There isn’t any NTFS drive on server <server name>, which is needed by the despooler to decompress or install the package. CAUSEWhen the Scheduler creates a package for distribution, it checks for files with long filenames. If such a file is detected, the Scheduler sets a flag requiring the Windows NT file system (NTFS) for the package destination. The despooler then should not attempt to distribute the package when it detects the flag.
WORKAROUNDTo work around this problem, either rename or delete the file(s) in the 8.3 file format and then distribute the package again. Refer to the "Run Command on Workstation Job" flowchart in Appendix C of the Systems Management Server Administrators Guide for the location of the file(s).
STATUSMicrosoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1, and 1.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: prodsms
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |