Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172645

From BetaArchive Wiki
Knowledge Base


Article ID: 172645

Article Last Modified on 6/29/2004



APPLIES TO

  • Microsoft SNA Server 3.0 Service Pack 4, when used with:
    • Microsoft Windows NT 4.0
  • Microsoft SNA Server 4.0, when used with:
    • Microsoft Windows NT 4.0



This article was previously published under Q172645


SYMPTOMS

In Microsoft SNA Server versions 3.0 and 3.0 Service Pack 1 (SP1), of a UNC (universal naming convention) path for a print session is specified and the printer is not installed on the server, Snaprint.exe fails and causes the print session to remain in a pending state rather than returning to inactive.

CAUSE

The Snaprint Service assumes that any printer to which it has access will have a port name set up for it. Print Server will fail if the WinvprtStartJob() or WinvprtOpenPrinter() fails to find the port name for the defined printer.

RESOLUTION

The Winvprt.dll and Ppd3270.dll files have been changed. When a port name is not detected, an error is logged and the status of the print LU returns to inactive instead of remaining in a pending state.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K


MORE INFORMATION

The remote printer must exist in the domain (and be installed) or the print session transitions to inactive without trapping.

Keywords: kbbug kbfix kbprint KB172645