Printer XXXXX was not found in the host system error in the sap java nwa logs

[vijayghorpade82-eng]

Describe the bug

A network printer configured in CUPS is available and visible on the operating system. The printer can be verified using lpstat -p and is successfully registered in CUPS.

However, a Java-based application fails to detect the printer and displays the following error:

"Printer <printer_name> was not found in the host system"

The printer exists on the host, CUPS is running, and the printer queue is available. The issue appears to be related to printer discovery between the Java application and CUPS.

To Reproduce

1. Configure a network printer in CUPS.
2. Verify the printer is available using:
   lpstat -p
3. Launch the Java application.
4. Open the print functionality within the application.
5. Select or search for the configured printer.
6. The application returns:
   "Printer <printer_name> was not found in the host system"

Expected behavior

The Java application should detect and use printers that are already configured and available through CUPS on the host system.

Screenshots

Not available.

System Information

• OS and its version:

NAME="SLES"
VERSION="15-SP7"
VERSION_ID="15.7"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP7"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp7"
DOCUMENTATION_URL="https://documentation.suse.com/"

• Application:
  Java-based application

• Printer Type:
  Network Printer

• CUPS version:
  2.2.7

Additional context

The printer is successfully configured and visible in CUPS.

Verification performed:

lpstat -p

Result:
The printer is listed and available.

Additional observations:

• CUPS service is running.
• Network printer is reachable.
• Printer queue exists in CUPS.
• Issue occurs only within the Java application.
• The printer can be seen at the operating system level but is not detected by the Java application.
• The application may not be refreshing or retrieving the latest printer list from CUPS.
• Possible relation to printer discovery, Java Print Service integration, printer cache, or compatibility with the CUPS version in use.

Diagnostic information available upon request:

lpstat -t
lpstat -l -e
systemctl status cups

No CUPS errors have been observed so far. The issue appears specific to printer discovery from the Java application despite the printer being available and operational in CUPS.

[michaelrsweet]

This is a really old version of CUPS; we can try to help but it might be an issue that has been already fixed, and SuSE will likely be able to provide more targeted support...

One thing you can do is enable detailed debugging ("cupsctl LogLevel=debug2") and then try accessing the printer from the Java application. That will yield some very detailed debug messages in the error_log file/system journal that might yield some clues...

[vijayghorpade82-eng]

Hello Team,

I want to check regarding the CUPS configuration difference observed between the server and the client application server. On the server side, the configuration is:

Listen *:631 BrowseLocalProtocols all Order allow,deny Allow from all

Whereas on the client application server, the configuration is:

Listen localhost:631 BrowseLocalProtocols dnssd <Location /admin> Order allow,deny

Could you please confirm if these differences may cause intermittent 'printer not found' errors?

We will enable cupsctl LogLevel=debug2 and share the error details if found.

Thanks, Vijay

[michaelrsweet]

The cupsd.conf differences shouldn't matter.

[vijayghorpade82-eng]

Dear Team,

We are analyzing intermittent “printer not found” behavior on our client application server (XYZ) and would like your expert confirmation regarding the impact of specific CUPS configuration differences between the server and client.

CUPS Server (ABC) – cupsd.conf
Listen *:631

BrowseLocalProtocols all

Allow from all

Client (XYZ) – cupsd.conf
Listen localhost:631

BrowseLocalProtocols dnssd

(no “Allow from all” present)

Context
In our environment, the client (XYZ) does not use static printer queues.
Instead, it relies on IPP browsing to dynamically discover printers broadcasted by the CUPS server (ABC).
Therefore, XYZ must be able to:

receive IPP broadcast packets from XYZ

accept incoming printer updates

use the correct browsing protocol for discovery

Request for Confirmation
Given this architecture, could you please confirm whether the following XYZ configuration differences may directly impact printer discovery and lead to intermittent “printer not found” conditions?

Listen localhost:631
Does this prevent XYZ from receiving IPP broadcasts from ABC compared to Listen *:631?

BrowseLocalProtocols dnssd
Does using dnssd limit discovery compared to BrowseLocalProtocols all, especially when PMC broadcasts via IPP?

Missing “Allow from all” under
Could this cause XYZ to reject or ignore incoming broadcast updates from ABC ?

We will enable cupsctl LogLevel=debug2 and share logs, but before doing so, we would appreciate your confirmation based on CUPS browsing architecture and client–server behavior.

Thank you for your guidance.

Regards,
Vijay