SNACFG Fails To Create Print Session When a PDT Is Specified

 Last reviewed: February 9, 1998
Article ID: Q180664
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0, 3.0SP1, 3.0SP2, 4.0

SYMPTOMS

When using the SNACFG command line utility to create an SNA Server printer session, it may fail with the following error message if a PDT file is specified and includes spaces in the name (for example, Active Setup Log.PDT): 

   Line No. 1: Error - Bad option specified

CAUSE

The SNACFG utility does not correctly parse the PDT file name when spaces are included in the file name itself.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, and 4.0. 

 A supported fix is now available, but has not been fully regression-tested
and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.

Additional query words: snacfg printsession pdt pdf
Keywords : kbbug3.00 kbbug3.00.sp1 prodsna snaprintservice kbbug3.00.sp2 kbbug4.00 kbbuglist
Version : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 9, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.