| Previous | Next |
| ERROR_INVALID_PRINTER_DRIVER_MANIFEST | ERROR_REQUEST_PAUSED |
ERROR_PRINTER_NOT_SHAREABLE
Windows sharing is a property of the logical printer object managed by the print server, not of the physical device alone. AddPrinter accepts PRINTER_INFO_2 data that includes a printer name, port, driver, print processor, share name, and attributes, while SetPrinter changes printer configuration and state.
The failure should therefore be investigated at the queue configuration and provider/server boundary. A printer can produce a local test page yet still fail an operation that attempts to expose that printer object for remote clients.
Inspect the logical printer object
- Capture the exact printer object, server, share name, attributes, driver, port, and print processor used in the sharing request.
- Read the existing printer configuration before and after the failed SetPrinter or creation operation; do not infer sharing state from device connectivity.
- Check whether the object is managed by the expected print provider and server and whether remote printing is enabled for that server.
- When interoperating with Samba, verify that the queue is exported by the server and has a valid backend and Windows printing configuration before debugging client-side discovery.
AddPrinter configuration fields · SetPrinter configuration controls · MS-RPRN remote print management
Looking for a different code? Search another status or error code.