In the situation where you create a virtual printer from scratch, you can find that your printer settings you supplied are not correct. In this case, when printing from Windows, the print job will error, and in the Print Queue you'll see an 'Error - Printing' message.
Inspecting the event viewer logs doesn't yield any actionable errors.
If the error is due to something which can be fixed by the developer, for example, a missing or miss-configured printer setting or capability in the virtual printer, it would be useful to log this somewhere. Even if it's a verbose logging setting that needs to be turned on manually.
Alternatively, documenting the required settings for different virtual printer scenarios could be useful too.
For example, 'A virtual printer accepting PDF requires these settings...'.
Thanks!
7 Comments
- Status changed:In progresstoCompleted
- Rachelle_Cheung
Microsoft
This work has been completed and will be available in Windows 11.
- Rachelle_Cheung
dennishaseloffalemo We are actively working on this right now. No timeline to share at this point in time.
Hey AndrewCardy,
thanks for providing this idea. Any error logging would have prevented many trouble in the past 🙂
is there any finished timeline for this feature?
Dennis
Installation and printing were my main areas of pain. I can't think of anything else other than what you've already noted.
Thanks for picking this up, it'll certainly make developing virtual printers a little easier! 🙂
Andy
- Rachelle_Cheung
We are working on incorporating basic Event Viewer logging. This includes:
- Errors during discovery
- Errors during printer installation
- Errors during printing
- No token errors
- Timeout errors
Is there anything else you can think of that would be useful to include in the Event Viewer?
- Status changed:NewtoIn progress
