Microsoft KB Archive/301332

= Print Jobs Continue Spooling if Host Ends Print Job with CHASE RU =

Article ID: 301332

Article Last Modified on 2/22/2007

-

APPLIES TO


 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 3.0 Service Pack 2
 * Microsoft SNA Server 3.0 Service Pack 3
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 4.0 Service Pack 1
 * Microsoft SNA Server 4.0 Service Pack 2
 * Microsoft SNA Server 4.0 Service Pack 3
 * Microsoft SNA Server 4.0 Service Pack 4
 * Microsoft Host Integration Server 2000 Standard Edition

-



This article was previously published under Q301332



SYMPTOMS
If the host system sends a CHASE Request Unit (RU) at the end of the print job, host print jobs that are sent through the host print service that is included with SNA Server and Host Integration Server 2000 may fail to print. SNA Manager lists the status of the host print session as &quot;Spooling&quot;, and the Microsoft Windows NT or Microsoft Windows 2000 print queue lists the status of the print job as &quot;Spooling&quot;.

NOTE: A host print session may stay in a spooling state due to reasons other than the one described in this article.



CAUSE
The host print service sets an incorrect message key (that is, sequence number) on the response to the CHASE RU that it received from the host through the SNA Server service. Because the message key is incorrect, the SNA Server service is unable to correlate this response to the CHASE message that it sent to the host print service. The SNA Server service cannot send either the CHASE +RSP back to the host system or the appropriate message to the host print service to signal the end of the print job until it receives a valid response to the CHASE message. This results in the spooling print session and the print job failing to print.



SNA Server 4.0
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.

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 Host Integration Server 2000 Service Pack 1.



MORE INFORMATION
The following annotated trace that was captured using the SNA Trace program (Snatrace.exe) shows the CHASE RU and the response from the host print service that causes the problem that is described in this article. The host sends a CHASE RU similar to the following to the SNA Server (or HIS 2000 Server):

DLC  0A160000->01020101 DLC DATA DLC                     DAF:07 OAF:01 ODAI:off Normal DLC                     CHASE  RQD DFC FI BC EC DR1 PI EB DLC DLC   Header  at address 0122485C, 1 elements DLC  04020001 20002C00 070101F1 01005C0C     <.... .,....1..\.> DLC DLC   Element at address 01C27F48, start 10, end 13 DLC  4B814084                                

The SNA Server service sends the CHASE RU to the host print service in the following format. Note the &quot;Msg key&quot; field marked with ^^^.

FMI  02020302->09120200 FMIST CTRL CHASE REQ FMI                     ACK required Msg key:498 FMHI BCI ECI EBI FMI                                  ^^^ ^^^^^^^ FMI   Header  at address 0153485C, 0 elements FMI  02011501 E4002C00 070101F2 01008C0C     <....U.,....2....>

The host print service responds to the CHASE message with the following CHASE acknowledgement. Note the &quot;Msg key&quot; field marked with ^^^.

FMI  09120200->02020302 FMIST CTRL CHASE ACK FMI                     Msg key:499 BCI BBIUI EBIUI FMI                     ^^^ ^^^^^^^ FMI   Header  at address 01534DA4, 0 elements FMI  020215F1 40062C00 070101F3 0100C407     <...1@.,....3..D.> The SNA Server set the message key (msg key) field to 498, but the host print service's acknowledgment incorrectly set the message key to 499. The message key field for the acknowledgment should be the same as the message key for the request.

Additional query words: HIS 2000

Keywords: kbbug kbfix kbhostintegserv2000sp1fix kbhostintegserv2000presp1fix KB301332

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.