Zero Byte Files When You Print to a File with ByPass GDI Selected (276264)



The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 SP1
  • Microsoft SNA Server 4.0 SP2
  • Microsoft SNA Server 4.0 SP3

This article was previously published under Q276264

SYMPTOMS

When you print to a file through SNA Server, zero-byte-size files may be printed.

CAUSE

This problem only occurs when ByPass GDI is selected in the printer session configuration dialog box. Typically, the SNA Server Print Service starts up a print job by calling the StartDoc function. However, when ByPass GDI is selected, this print job must be started up transparently, so the AbortDoc function is called, then the StartDocPrinter function is called.

Because of a timing issue with Microsoft Windows NT, the handle to the original file is not released immediately, which can cause the call to StartDocPrinter to fail, which results in the zero byte file. This problem has been corrected so that print jobs are started transparently, by using a generated minimal PDT file, rather than SNA Print Service having to stop and restart them. This same approach is used in Microsoft Host Integration Server (HIS) 2000.

RESOLUTION

SNA Server 4.0:

To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack


Host Integration Server 2000:

To resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

328152 How to Obtain the Latest Host Integration Server 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in SNA Server 4.0 Service Pack 4. This problem was first corrected in Host Integration Server 2000 Service Pack 1.

Modification Type:MinorLast Reviewed:3/10/2005
Keywords:kbbug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix kbSNA400PreSP4fix kbSNA400sp4fix KB276264