Menu

When Application Verifier is run on a solution or project, the Print Verifier provides a stop code when an error is found. The stop codes that may be encountered depend on the tests selected to run.

The following is a list of all codes that may be encountered when running the Print Verifier. To find out more about the details of the stop, please refer to the specific error message.

PrintAPI test layer messages

These messages are returned by the Print Verifier when it is testing the PrintAPI test layer.

Error messageStop 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

PrintDriver test layer messages

These messages are returned by the Print Verifier when it is testing the PrintDriver test layer.

Error messageStop code

First chance access violation detected

0000D000

The thread tried to divide an integer value by an integer divisor of zero

0000D001

The thread tried to read or write misaligned data on hardware that does not provide alignment

0000D002

Invalid handle exception for current stack trace in Print Verifier

0000D003

Core driver is sending a closed printer handle to the plug-in

0000D004

Core driver is sending an unknown printer handle to the plug-in

0000D005

The plug-in driver closed the printer handle

0000D006

Invalid number of supported Print Schema major versions

0000D007

Missing supported Print Schema versions

0000D008

Invalid Print Schema major version

0000D009

Invalid OEMPTOPTS value

0000D00A

Missing Print Schema private namespace

0000D00B

Incorrect reference counting detected in the plug-in

0000D00C

pptl is NULL in OEMNextBand

0000D00D

The plug-in returned a NULL PDEV after returning S_OK from the EnablePDEV method

0000D00E

The plug-in returned a private DEVMODE that is smaller than the minimum size allowed

0000D00F

The plug-in returned a private DEVMODE with a different size than the size returned by the DevMode(OEMDM_SIZE) call

0000D010

The plug-in returned an invalid signature from the GetInfo(OEMGI_GETSIGNATURE) call

0000D011

The plug-in returned a different signature in the private DEVMODE than it returned from the GetInfo call

0000D012

The EnableDriver method in the plug-in failed.

0000D013

The EnableDriver method in the plug-in failed without setting the last error code

0000D014

The core driver called SetBandSize although the plug-in returned S_OK from DriverDMS

0000D015

The core driver made the WritePrinter initialization call with invalid parameters

0000D016

The WritePrinter method in the plug-in failed

0000D017

Core driver sent an invalid PrintTicket to the plug-in

0000D018

The plug-in returned an invalid PrintTicket to the core driver

0000D019

Core driver sent an invalid PrintCapabilities document to the plug-in

0000D01A

The plug-in returned an invalid PrintCapabilities document to the core driver

0000D01B

PTConform encountered an unexpected error (PrintDriver)

0000D01C

Print filter calls pipeline manager interface with invalid argument value

0000D01D

Print filter call to IPrintPipelinePropertyBag overwrites or removes common property

0000D01E

Print filter calls pipeline manager interface out of order

0000D01F

Print filter has mismatch of AddRef/Release calls to pipeline manager interface

0000D020

Print filter call to pipeline manager interface method is not expected

0000D021

Pipeline manager calls print filter interface methods out of order

0000D022

Pipeline manager calls print filter interface method with invalid argument value

0000D023

Pipeline manager returns invalid value to print filter

0000D024

A call to a printer driver changed the security context

0000D025

Print filter sent an invalid PrintTicket to pipeline manager

0000D026

Print filter received an invalid PrintTicket from pipeline manager

0000D027

Unloading print driver DLL with active COM callback.

0000D028

Attempt to use a released COM interface

0000D029

A print driver called ExitThread

0000D02A

A print driver called TerminateThread

0000D02B

See Also