- This topic has 2 replies, 2 voices, and was last updated 23 hours, 55 minutes ago by .
-
Posts
-
Hi,
it seems that the new named pipe format ("?" instead of ".") is causing the printer to no longer working under Windows Server 2019.
Eventlog puts out an error (Source = PrintService, EventID = 372) saying "Win32 error code returned by the print processor: 50. The request is not supported.".
Trying to manually connect to a named pipe from PDF24 with a questionmark e.g. "\\?\pipe\PDFPrint" via powershell gives me "Illegal characters in path.".
Removing the PDF24 version 11.33.0 and reverting to 11.32.0 fixes the issue, as the pipe now uses a dot "." character.
Hello,
thank you for the analysis, that is exactly the cause. Since version 11.33.0 the port of the classic PDF printer is named
\\?\pipe\PDFPrint. Windows 10, Windows 11 up to 21H2 and Windows Server 2016 to 2022 do not recognize this port as a pipe, so the print jobs fail (event 372, error code 50). Windows 11 22H2 and later are not affected.The fix will come with the next version: on these systems the update moves the printer back to the port
\\.\pipe\PDFPrint.Until then, staying on 11.32.0 is fine. Instead you can also keep 11.33.0 and move the printer back yourself in a PowerShell window opened as administrator:
Add-PrinterPort -Name '\\.\pipe\PDFPrint' Set-Printer -Name 'PDF24' -PortName '\\.\pipe\PDFPrint'Use the name of your printer instead of
PDF24if you renamed it. 11.33.0 deleted the old port, so it has to be created first. PDF24 understands both port names.In both cases, please do not install 11.33.0 again (also not through the update function), as its setup would move the printer back to
\\?\pipe\PDFPrint.
- You must be logged in to reply to this topic.