Menu

Application Verifier break message

Pipeline manager calls print filter interface methods out of order

Probable cause

This verifier stop occurs when the pipeline manager incorrectly calls the methods of the print filter interface. Report this error to Microsoft because it could be a problem in the print filter pipeline service.

Information displayed by Application Verifier

Format:�-� Invalid call order to Print Filter : %s

Parameter 1�-�Filter CLSID pointer.

Parameter 2�-�Not used.

Parameter 3�-�Not used.

Parameter 4�-�Not used.

Additional information

Test Layer:�PrintDriver

Stop code:�0000D022

Severity:�Warning

One-time error:�no

Error report:�Break

Log to file:�yes

Create backtrace:�yes