Mobile printing with iPrint

qmangus

The use of mobile devices has greatly improved productivity in the workplace. Users can more easily access systems, quickly communicate and collaborate, and even create and share documents and files on their mobile devices (Micro Focus Filr is a great solution for this). In fact, a recent survey by Samsung and Frost & Sullivan found …

+read more

The post Mobile printing with iPrint appeared first on Cool Solutions. qmangus

Related:

  • No Related Posts

7023341: iPrint Appliance Directory Servers Configuration: An error has occurred

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

Environment

Micro Focus iPrint Appliance 3.x

Situation

When clicking the Synchronize Now button within the iPrint Appliance Directory Servers -> Directory Servers Configuration page, the following error is returned

Last manual synchronization [DATE]

  • Status: Failed
  • Server:
  • Error: An error has occurred. See the server logs for more information.

Resolution

Run the Re-Index Everything tool with the Search Index tool.
  1. Take a snapshot of the Appliance.
  2. Delete the kablink cache
  • rm /vastorage/search/lucene/kablink/*
  • Stop the firewall
    • rcSuSEfirewall2 stop
  • Find the Filr admin password
    • Paste the following command into a terminal session:
      • base64 -di /etc/opt/novell/iprintmobile/conf/credstore.conf
    • Look for the line which shows <entry key=”filr.password”>
    • Copy the password which shows for that entry.
  • Launch the Filr console from the browser.
    • https://<appliance host address>:8444
    • Type ‘admin’ for the user name
    • Type the password found from step 3 for the password
    • Choose “Cancel” when prompted to change the password
  • At the top right corner, click the “admin” link and choose “Administration Console”
  • Click “Search Index” within the left navigation list (under the “Management” section”)
  • Check the box for “Re-Index Everything” and click OK.
    • This might take quite some time so let it continue until it is completed.
  • Start the firewall.
    • rcSuSEfirewall2 start
  • Verify the problem is resolved.
  • 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.

    Related:

    7012837: NSS pool move operation displays Error 23316 “No Space for Move Stamps”

    Typically, when creating a NSS pool, a partition is created on a 1MB boundary and NSS uses 32 sectors for a header to store stamps, and provides the rest to NSS pools. NSS will then round the pools to a 1MB boundary. What this does is leave a 1MB (32 sectors space at the end of the partition that is not used.

    The NSS ‘pool move’ code takes advantage of that unused space to store the mirror stamps that are being used for the actual pool move.

    When this space is available, a pool move can successfully be performed.

    There is however always a possibility that the pool is using all the space for one reason or another. These could be pools that were originally created on earlier version of Novell NetWare.

    NSS checks to make sure the space required is available (NSS needs 6 sectors to store the stamps), and if not, will return the reported error. There is nothing that can be done with the pool as to fix this.

    It was however determined that after expanding the pool, with a minimum of 12 MB, then this causes the rounding to a 1MB boundary to take place again, which in turn will allow the stamps to be written, and the pool move to succeed. It will slightly affect the pool size, but also does solve the problem relatively easy.

    Related:

    7023349: Chromebook iPrint printer install loops, never installs

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

    Environment

    Micro Focus iPrint

    Situation

    When attempting to install an iPrint printer to a Chromebook, the install loops from 0 to 100% and never installs.

    Resolution

    Micro Focus is investigating a solution to this problem. Until that time, the following two options exist:

    1. Use the PSMHostAddress to access the iPrint Portal page.
    • Find the PSMHostaddress by running the following command a terminal session to the iPrint server:
      • cat /etc/opt/novell/iprint/conf/ipsmd.conf | grep PSMHostAddress
    • When accessing the iPrint Portal page, use the address PMSHostAddress value.
      • For example, if the address following PSMHostAddress is iprint03.mycompany.com, then use this address to bring up the iPrint Portal:
        • https://iprint03.mycompany.com/print
  • Recreate the certificate with a SAN to match the PSMHostAddress
  • Cause

    The iPrint code cannot handle a scenario where the address bound to the Print Manager does not match the address used to access the iPrint Portal page (https://<iPrintDNSName>/print).

    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.

    Related:

    7008708: History of iPrint Client fixes

    Fixes introduced in the 6.15 iPrint Client

    Available through the OES and iPrint Appliance Update channel and through the iPrint Appliance 2.1 Patch 7 download.

    • User printers installed using WSACL rules and shortname could not be removed (Bug 1089861)
    • iPrint Lite: Unsupported files information icon updated (Bug 1081341)
    • iPrint Lite is allowing to print unsupported files through windows context menu open with option. (Bug 1069221)
    • iPrint_lite: Clicking on iprint-lite icon on windows task bar does not minimize it. (Bug 1070780)
    • iPrint_lite: Hitting Enter key after entering server-ip does not click on “Find” button. (Bug 1070925)
    • iPrint Authentications fail with Novell Client installed (userPrincipalName) (Bug 1080884)
    • No error message when user prints to an SSL printer that he has no rights (Bug 1077610)
    • Printer driver download without iPrint provider using CLI. (Bug 116453)
    • iPrint client allowing to print the document even if the copies field is null. (Bug 1070716)

    Fixes introduced in the 6.12 iPrint Client

    Available through the OES and iPrint Appliance Update channel

    • Refresh iCM feature introduced (Bug 1057892)
    • Context menu printing crashes Windows Explorer with files with no extension (Bug 1063863)

    Fixes introduced in the 6.11 iPrint Client

    Available through the OES and iPrint Appliance Update channel

    • Minor cosmetic fixes.

    Fixes introduced in the 6.10 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through iPrint Appliance 2.1 Patch 5

    • TID 7020136: OES Client nwtray crashes when you login through icon repetitively

    Fixes introduced in the 6.09 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

    • iPrint Appliance 2.0 Hot Patch 4
    • iPrint Appliance 2.1 Hot Patch 4
    • Error messages flooding NPSMMON.LOG (Bug 1021421)
    • Print dialog within MS Office or Adobe Reader in perpetual error state or spins indefinitely. (Bug 1029529)
    • User Printer installation crashes print spooler if location or description is set. (Bug 1028999)

    Fixes introduced in the 6.08 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

    • iPrint Appliance 2.0 Patch 4
    • iPrint Appliance 2.1 Patch 2
    • TID 7017101 – 0x00000002 error installing iPrint printers with the EFI Fiery driver (Bug 1019023)
    • TID 7017417 – Direct Printers looses parts of the printed document if bDirectPrintSpoolJobEnabled is enabled (Bug 1021882)
    • TID 7021962 – Hide Document Names for iPrint printer’s Windows Printer Queue
    • Printer driver DLLs are being over-written during iPrint printer installation. (Bug 990474)
    • iprntcmd based printer install and deletion enhanced for new User Printer implementation (Bug 103440)
    • iCM settings only read on log on. Provided message-box in case iCM not enabled. – Added few strings to the string table for User Printer. (Bug 104441)

    Fixes introduced in the 6.07 iPrint Client

    Available through the OES Update channel

    • Mac driver upload via iManager results in inproper driver name. (Bug 984480)
    • iCM fails to launch when logging in with OES Client. (Bug 1011189)
    • error 0x00000002 installing PS EFI Fiery driver (Bug 1019023)
    • Spooler crashes with Auto driver/profile update on Win 10 x86 (Bug 1020818)

    Related:

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

    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.

    Related:

    7023235: Error code: 0xfffffec1 changing password after upgrade to Client for OES 2 SP4 (IR9)

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

    Environment

    Client for Open Enterprise Server 2 SP 4 (IR9)

    Situation

    When trying to change the password from the client, an error is reported:

    Attempt to change password for server TREE_NAME failed. Error code: 0xfffffec1

    Resolution

    Fixed in Client for Open Enterprise Server 2 SP4 (IR10) and later.

    Cause

    There is a mismatch in the cryptographic negotiation between Client for OES 2 SP4 (IR9) and eDir 9.x

    fffffec1

    Additional Information

    This error will appear if the change password request is sent to an OES 2018 server holding a R/W replica. If the request is sent to an OES 2015 SP1 server, the password is changed, and no error is displayed.

    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.

    Related:

    7023330: Uninstall Client for OES 2 without requiring a reboot

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

    Environment

    Client for Open Enterprise Server 2 SP4 (IR10)

    Situation

    In some cases, an administrator may want to uninstall Client for OES without an immediate reboot of the workstation.

    Resolution

    Beginning with Client for Open Enterprise Server 2 SP4 (IR10), a “norestart” (or “nr”) switch has been added.

    To uninstall the client silently and suppress the reboot, use this command:
    %SystemRoot%System32rundll32 “C:ProgramFilesNovellClientncsetup.dll” NWUninstallClient /s /norestart
    OR
    %SystemRoot%System32rundll32 “C:Program FilesNovellClientncsetup.dll” NWUninstallClient /s /nr
    Note:
    • The above command works only if the command prompt is opened in administrator mode.
    • After uninstalling the Client without rebooting, a restart of Windows is required before reinstalling the Client.

    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.

    Related: