Computer printing – Page 2 – Intelligent Systems Monitoring

7023334: Apache won’t load and “Document failed to print” after upgrade to OES 2018

September 5, 2018September 5, 2018 Novell Leave a comment

This document (7023334) is provided subject to the disclaimer at the end of this document.

Environment

Open Enterprise Server 2018

iPrint Client 6.15

Situation

After upgrading to OES 2018, sending a print job thru the Windows iPrint Client returns the error:

Document failed to print

iPrint Client properties, iPrint document status shows “Creation failed” error

ipsmd (Print Manager) and idsd (Driver Store) are running fine.

Apache is not loaded. When loading Apache, the following is returned:

[DATE + TIME] server start_apache2[6338]: httpd-prefork: Syntax error on line 204 of /etc/apache2/httpd.conf: Syntax error on line 119 of /etc/apache2/default-server.conf: Syntax error on line 5 of /etc/apache2/conf.d/oes_httpd.conf: Syntax error on line 9 of /etc/opt/novell/httpd/conf.d/iprint_g.conf: Cannot load /opt/novell/iprint/httpd/lib64/mod_ipp.so into server: /usr/lib64/libcurl.so.4: undefined symbol: libssh2_agent_disconnect

[DATE + TIME] server systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE

Resolution

Remove the incorrect link

Follow these steps to find the incorrect link and link the correct library:

1. Run the following command on both a working and non-working OES 2018 server:

ldd -r /usr/lib64/libcurl.so.4

The following will be returned on a working server:

linux-vdso.so.1 (0x00007ffe50bac000)

libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007fa924d73000)

libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007fa924b47000)

libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007fa9248dc000)

libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007fa924483000)

libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fa92423b000)

liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007fa92402c000)

libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007fa923de0000)

libz.so.1 => /lib64/libz.so.1 (0x00007fa923bca000)

libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa9239ad000)

libc.so.6 => /lib64/libc.so.6 (0x00007fa923608000)

libdl.so.2 => /lib64/libdl.so.2 (0x00007fa923404000)

libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fa923134000)

libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fa922f04000)

libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fa922d00000)

libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fa922af3000)

libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa9228dc000)

libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007fa9226bf000)

/lib64/ld-linux-x86-64.so.2 (0x00007fa925217000)

libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fa9224bb000)

libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fa922295000)

libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fa922026000)

The following will is an example of what was returned from one non-working server:

linux-vdso.so.1 (0x00007ffec170d000)

libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007f62ea6e4000)

libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f62eac5f000)

libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007f62ea479000)

libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007f62ea020000)

libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007f62e9dd8000)

liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f62e9bc9000)

libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f62e997d000)

libz.so.1 => /lib64/libz.so.1 (0x00007f62e9767000)

libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f62e954a000)

libc.so.6 => /lib64/libc.so.6 (0x00007f62e91a5000)

libdl.so.2 => /lib64/libdl.so.2 (0x00007f62e8fa1000)

libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007f62e8c01000)

libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007f62e8931000)

libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007f62e8701000)

libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f62e84fd000)

libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f62e82f0000)

libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f62e80d9000)

libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007f62e7ebc000)

/lib64/ld-linux-x86-64.so.2 (0x00007f62eab88000)

libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f62e7cb8000)

libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f62e7a92000)

libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f62e7823000)

undefined symbol: libssh2_agent_disconnect (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_knownhost_init (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_agent_free (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_knownhost_free (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_knownhost_readfile (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_agent_get_identity (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_knownhost_check (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_session_hostkey (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_agent_userauth (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_session_block_directions (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_knownhost_writefile (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_agent_init (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_agent_connect (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_knownhost_add (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_scp_send64 (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_sftp_seek64 (/usr/lib64/libcurl.so.4)

undefined symbol: libssh2_agent_list_identities (/usr/lib64/libcurl.so.4)

2. Compare the working and non-working output to the ldd command. In the above scenario, the 3rd line shows a library linked to an incorrect file:

libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f62eac5f000)

3. Do a listing on the incorrect module:

l /lib64/libssh2.so.1

In this scenario, the following is returned:

lrwxrwxrwx 1 root root 49 Nov 21 2012 /lib64/libssh2.so.1 -> /usr/openv/pdde/pdopensource/lib/libssh2.so.1.0.0*

4. Execute an RPM query on the incorrect package:

rpm -qf /lib64/libssh2.so.1

In this scenario, the following is returned:

file /lib64/libssh2.so.1 is not owned by any package

5. Delete the link:

rm /lib64/libssh2.so.1

6. Refresh the library links:

lddconfig

7. Start Apache

rcapache2 start

Cause

There was a wrong library link.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Is this still a valid approach with later versions of ICN, Sync, NMO,…?

7023317: iPrint on OES2018 Cluster fails to load – failed at step EXEC spawning /opt/novell/iprint/bin/precheck

August 29, 2018September 5, 2018 Novell Leave a comment

This document (7023317) is provided subject to the disclaimer at the end of this document.

Environment

iPrint for Linux Open Enterprise Server

Open Enterprise Server 2018 (OES 2018) Linux

Cluster

Situation

After fully patching an OES2018 server (note: fully patched as of 30 August 2018, which is Update 3, released 27 June 2018) with iPrint configured to run in a cluster, the iPrint services will not load. The following error is found in the system log:

failed at step EXEC spawning /opt/novell/iprint/bin/precheck

Resolution

Download ftp://ftp.novell.com/outgoing/novell-iprint-server-6.18.0_1074650-1.1.x86_64.rpm

Install this RPM on each node. The node must have the Cluster Volume hosting iPrint loaded at the time of the install.

If the server can access external sites, the following string of commands can be pasted into a terminal session to download and install the RPM.

wget -P /tmp ftp://ftp.novell.com/outgoing/novell-iprint-server-6.18.0_1074650-1.1.x86_64.rpm;rpm -Uvh /tmp/novell-iprint-server-6.18.0_1074650-1.1.x86_64.rpm

Cause

A defect in the iPrint server code.

Additional Information

This issue is scheduled to be fix in the next update. This article will be modified once the fix has been released.

Disclaimer

Is this still a valid approach with later versions of ICN, Sync, NMO,…?

Invite for Beta participation- Micro Focus iPrint 3.2

June 25, 2018June 25, 2018 Novell Leave a comment

iPrint team has been working hard for quite some time on the next release. There are a bunch of features and lots of bug fixes that are shaping up for this. We would absolutely love to hear your feedback on them, and therefore are opening up the beta for iPrint 3.2. Find the registration link here. Program …

No Related Posts

Packaging Cupsfilter on a Mac Device

June 25, 2018June 25, 2018 Novell Leave a comment

Installation of the printer fails on Mac if the cupsfilters specified in the PPD file is not installed. Some vendors do not distribute the drivers in .pkg or .dmg format. Hence, associating the package to the PPD file is not possible. Micro Focus iPrint server has an option to associate a package containing cupsfilters to …

+read more

The post Packaging Cupsfilter on a Mac Device appeared first on Cool Solutions. wpreetham

File and Print Community Webinars – 2018 (Jun to Sep)

June 11, 2018June 11, 2018 Novell Leave a comment

The first set of webinars in 2018 were well received with some webinars attracting more than 500 registrations. Continuing the run, here are the next set of File and Print Community webinars for OES, iPrint, Filr, and File Reporter. Each webinar will be a duration of an hour, with 45 mins for content and 15 mins …

No Related Posts

Multiple Monitors – Mouse Cursor Jumping Around, Out-of-sync if DPIs of Monitors Are Not Matched

May 30, 2018June 5, 2018 Citrix Leave a comment

Versions of Citrix Receiver for Windows 4.10 and higher are now “DPI scaling aware”, and provide improved support for handling higher DPI resolution in a session. You can now use multiple monitors with different DPI setting.

Reference:https://support.citrix.com/article/CTX230017

For Receiver versions older than 4.10, there is no restriction on matching monitor resolutions but the monitors must have the same DPI settings.

Windows 8.1 Settings

If using a Windows 8.1 or Windows 10 end-point with automatic scaling configured, you will see this issue. If you use the Let me choose one scaling level for all my displays option in the Windows Control Panel > Display options, this will configure the monitors appropriately.

Windows 10 Settings

In Windows Control Panel Display settings you are able to change the setting from the *Change size of items* text. Where selecting *set a custom scaling level* will enable changing DPI. When selecting Change size of items and the review the information in the text description are links- select set a custom scaling level and then set DPI for each display to same value.

Control Panel > Display.

Change size of items

To change the size of text, apps and other items, you can *set a custom scaling level*.

Selecting the *set a custom scaling level* link enables changes to the DPI for each display. Setting equal number resolves issue.

No Related Posts

7018081: Manually Upgrade or Migrate iPrint Appliance

May 30, 2018June 4, 2018 Novell Leave a comment

This document (7018081) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus iPrint Appliance

Situation

The iPrint Appliance documentation lists two ways to upgrade the Appliance:

Version 1.1 to 2.1 – iprintconfig.zip method
Version 2.0 to 2.1 – Attach secondary disk method

This article documents a third method.

This third method is valid for upgrading or migrating to and from the following versions:

Note: The upgrade paths mentioned below do not apply to methods 1 and 2 above. For example, the iprintconfig.zip and secondary disk methods does not support a 1.x to 3.x upgrade.

1.0 to 1.1

1.0 to 2.0

1.0 to 2.1

1.1 to 2.0

1.1 to 2.1

2.0 to 2.1

2.x to 3.0

Resolution

Watch this video, and/or follow the steps below:

Copy files

From the existing iPrint Appliance server, copy the following to a Windows machine.

/var/opt/novell/iprint/resdir directory and all of its contents.
/var/opt/novell/iprint/print_manager.iPrintAppliance.psm/padbtxt.xml
/var/opt/novell/iprint/htdocs/iprint.ini

Configure the target appliance server.

It is important that the new server has the same DNS name and same IP address as the original server. Because of this requirement, you must shut down the original server to install and configure the new server.
After the initial configuration, be sure to go to https://<ip or dns>:9443 to complete the installation.

Choose the Create New iPrint Appliance option.

Import users

If you had imported users in the previous Appliance, do the same for the new one.

Create OUs.

If iPrint printer objects in the previous Appliance were created to an OU other than the iPrintAppliance Organization, create that OU using iManager.

Enable SSH so WinSCP and Putty can connect.

Go to https://<ip or dns>:9443
Click the System Services icon
Highlight SSH

Click Action -> Start
Click Options -> Set as Automatic

Copy files to the server

Copy the resdir directory and its contents to the new iPrint Appliance server.
Copy the padbtxt.xml to the /tmp directory.
Copy the iprint.ini to /var/opt/novell/iprint/htdocs

Prepare the padbtxt.xml

Line 7 of the /tmp/padbtxt.xml shows the tree name. This tree name is wrong. Update the tree name to the new server’s tree name. You can view the new server’s tree name by pasting the following command into a terminal session:

ndsstat | grep Tree

Import the printer agent configuration

Paste the following string of commands into a terminal session of the new server while logged in as root:

sed -i ‘s/driverupdateenabled>1/driverupdateenabled>0/’ /tmp/padbtxt.xml;rcnovell-ipsmd stop;chown -R iprint.iprint /var/opt/novell/iprint/resdir;rcnovell-idsd restart;/opt/novell/iprint/bin/ipsmd -x /tmp/padbtxt.xml -u cn=admin,o=iPrintAppliance;rcnovell-ipsmd start;rcnovell-iprint-mobile restart

You will be prompted to provide the admin password.
Among the commands listed above is a sed command which turns off Auto Driver Update within the XML file. This feature is turned because having Auto Driver Update enabled on a printer agent (or many printer agents) is undesirable when doing any type of migration. Having that option enabled instructs the workstations with printers installed to auto-remove and auto-install the iPrint printer to the workstation. This auto process happens when the time stamp on the printer driver is updated. A migration (manual or otherwise) will update the time stamp. Auto-removing printers and auto re-installing them is desirable only if the driver or profile was actually updated.

Mobile configuration

The above steps do not import the mobile printing configuration. You will need to configure all that was configured before, such as:

enable printers for mobile printing
configure the remote renderer
configure email printing
apply the license file
configure 3rd party certificates

Additional Information

The above documented upgrade steps can be desirable if :

the upgrade methods in the documentation are not working

or

you want a fresh start with the newer server, but don’t want to manually upload printer drivers or manually create printer agents and printer driver profiles.

Disclaimer

7022947: Blue Screen when installing iPrint Client version 6.15

May 28, 2018May 31, 2018 Novell Leave a comment

This document (7022947) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus iPrint Client

Situation

Installing the iPrint client to a Windows 10 workstation with Symantec installed results in a Blue Screen (BSOD).

Note: This problem happens when installing any version of the iPrint Client. But because the iPrint Client version 6.15 was released in May of 2018 (around the time of the problematic version of Symantec was released) many iPrint customers associate the blue screen with the 6.15 client.

Resolution

Install SEP version 14.0.3929.1200 or later.

Cause

The Blue Screen is caused by a version of Symantec Endpoint Protection.

Additional Information

The FTF client is a workaround for now. Refer back to this TID for updates regarding the resolution. The FTF removes the ability to upload printer drivers within iManager. As a workaround to the inability to upload printer drivers using iManager, use the steps documented in “Resolution 2” within TID 7016789.

Disclaimer

3006726: Configure iPrint to redirect printers on clients to different server.

May 16, 2018May 21, 2018 Novell Leave a comment

This document (3006726) is provided subject to the disclaimer at the end of this document.

Environment

Novell iPrint for NetWare 6.5

Situation

Goal: Configure iPrint printersinstalled to Windows workstations to point toanother server.

Problem: A print manager is a database thatresides on a NetWare or Linux server that contains a list ofPrinter Agents that can be installed to workstations. Movinga print manager from one NetWare server to another isas simple as typing NDPSM on the destination serverconsole. The administrator is prompted to browse to the printmanager object in NDS, then asked if they want to move the databaseto the new server. Moving Print Agents from a NetWareserver to a Linux server is also not difficult.

The challenge is that workstations have installed printeragents that point to the DNS or IP of the original server. Once the print manger or printer agents are moved, users willfail to print.

Solution: The manual solution is to instructyour users to delete and re-install their iPrint printers installedto their workstations. This TID explains an automatedsolution that will auto-delete and auto-install the printers forthe users.

Reconfiguring iPrint printers installed to workstations using thisTID has additional applications:

Migrating from iPrint on NetWare to iPrint on Linux.
Changing the IP address or DNS to which the print manager isbound.
Moving printer agents from one manager to another

NOTE: If the print manager was originally configured to bindto a CNAME (DNS of a service, rather than a server) AND you aremoving ALL the printers to a different server, then theproblem stated above is easily resolved: Change the IPaddress that is associated to that CNAME. However, manyadministrators bind their print manager to a server’s DNS or IPaddress, which ties the Windows installed iPrint printers tothat server. This common practice causes Windows installediPrint printers break when moving printers agents or a PrintManager to another server. This TID shows you howto configure an iPrint printer installed to a Windowsworkstation to point to another server without user intervention.

Resolution

All versions of iPrint on Linux has this feature. As for NetWare, you need Support Pack 6 for NetWare 6.5.

The feature is found within iManager, go to iPrint -> ManagePrint Manager -> Printer Agent Redirection. You will see alist of Printer Agents assigned to that Print Manager. Youwill also see a column to Redirect the Printer URL. Bypopulating the second column, iPrint printers installed toworkstations will see that the printer agent URL has changed. This will cause the iPrint client to remove the iPrint Printer fromthe workstation, and install the Printer Agent specified by theadministrator in the “Printer Redirect URL” column.

With the default configuration, end users will receive apop-up that notifies them the printer has been deleted. Theyreceive another pop-up to notify that the new printer will beinstalled. To change that notification behavior, see TID3476106.

Note: If you are redirecting a printer from Print Manager A to Print Manager B, then both Print Managers must be running for the redirection to take place. You can redirect same or different named printers.

Disclaimer

Is this still a valid approach with later versions of ICN, Sync, NMO,…?

iPrint Client for Win 7/Win 8/Win 8.1/Win 10 6.15

May 16, 2018July 2, 2018 Novell Leave a comment

Abstract:

nipp615.zip includes the iPrint Client version 6.15 for Windows 10, Windows 8.1, Windows 8, and Windows 7.

Note: iPrint support for Windows 8.1 and 10 requires either a) iPrint Appliance, or b) Open Enterprise Server 11 SP2 or later.

Document ID: 5380150
Security Alert: No
Distribution Type: Public
Entitlement Required: No
Files:

nipp615.zip (380.86 MB)

Products:

iPrint Appliance 3.1
iPrint Appliance 1.0.1
iPrint Appliance 3.0
iPrint Appliance 2.1
iPrint for OES (2018)
iPrint for OES (2015 SP1)

Superceded Patches:

iPrint Client for Windows Win 7/Win 8.x/Win 10

Is this still a valid approach with later versions of ICN, Sync, NMO,…?

Environment

Situation

Resolution

Cause

Disclaimer

Related:

Environment

Situation

Resolution

Cause

Additional Information

Disclaimer

Related:

Related:

Related:

Related:

Windows 8.1 Settings

Windows 10 Settings

Related:

Environment

Situation

Resolution

Additional Information

Disclaimer

Related:

Environment

Situation

Resolution

Cause

Additional Information

Disclaimer

Related:

Environment

Situation

Resolution

Disclaimer

Related:

Related:

Links