PrintAPI Test Layer Stop Details

When Application Verifier is run on a solution or project in the Print, the Print Verifier provides a stop code when an error is found. The stop codes that may be encountered in the PrintAPIr test layer are listed in the following table. Refer to the specific error message to learn more about the details of the stop.

PrintAPI test layer messages

Error message	Stop code
Leaked printer handle detected	0000A000
Leaked printer change notification handle detected	0000A001
Leaked PRINTER_NOTIFY_INFO detected	0000A002
Race condition detected while using a printer handle	0000A003
Potential multi-threaded access to a printer handle detected	0000A004
Attempt to use a closed printer handle	0000A005
Attempt to use an unknown printer handle	0000A006
Attempt to use a closed printer change notification handle	0000A007
Attempt to use an invalid printer change notification handle	0000A008
Attempt to use a freed PRINTER_NOTIFY_INFO object	0000A009
Attempt to use an invalid PRINTER_NOTIFY_INFO object	0000A00A
Too many open printer handles.	0000A00B
OpenPrinter2W seems to be exported from winspool.drv of an earlier version of Microsoft Windows	0000A00C
Too many open PrintTicket provider handles (HPTPROVIDER)	0000A00D
Attempt to use a closed PrintTicket provider handle (HPTPROVIDER)	0000A00E
Attempt to use an unknown PrintTicket provider handle (HPTPROVIDER)	0000A00F
Race condition detected while using a PrintTicket provider handle	0000A010
Potential multi-threaded access to a PrintTicket provider handle detected	0000A011
Leaked PrintTicket provider handle detected	0000A012
Too many open printer change notification handles	0000A013
Too many open PRINTER_NOTIFY_INFO objects	0000A014
Attempt to use an invalid PrintTicket	0000A015
Attempt to use an invalid PrintCapabilities document	0000A016
An invalid NULL argument was passed to a PrintTicket method	0000A017
PTConform encountered an unexpected error (PrintAPI)	0000A018
Illegal print API called from DllMain	0000A019
Leaked spool file handle detected	0000A01A
Attempt to use a closed spool file handle	0000A01B
Attempt to use an unknown spool file handle	0000A01C
Too many open spool file handles	0000A01D
DEVMODE buffer parameter spans across non-readable memory page(s)	0000A01E
Unloading module with active COM callback	0000A01F
Async Notify handle returned by RegisterForPrintAsyncNotifications was not released properly	0000A020
Attempt to use an invalid handle in UnRegisterForPrintAsyncNotifications	0000A021
Attempt to use a closed handle in UnRegisterForPrintAsyncNotifications API function	0000A022
Third-party function reports failure but increases reference count for input interface	0000A023
Windows API function reports failure but increases reference count for input interface	0000A024
IPrintAsyncNotifyChannel contract violation by the operating system	0000A025
IPrintAsyncNotifyChannel contract violation by channel consumer	0000A026
Race detected during closing of IPrintAsyncNotifyChannel	0000A027
Calling a print API that makes network calls on a GUI thread	0000A028
Calling an API that will pop up user interface in Session0	0000A029

PrintAPI test layer messages

See Also

Concepts