iprint and imanager screwy after nw65sp7

After installing nw65sp7, when I go to imanager on the netware server to
manage iprint, I get two entries for most choices. This is what is under
the iprint roles
Parents
  • You somehow have the options for both the NetWare and the Linux iPrint
    plugins mixed.
    Are you using RBS? If yes, make sure you update your collections. Also, if
    you don't have any OES(2)/Linux server, then simply remove the
    iPrint/Linux plugin from your iManager installation.

    --
    Marcel Cox (Sysop)
    Discover the new Novell forums at http://forums.novell.com
  • Why doesn't the iimanager for windows on my xp workstation have the stuff
    for netware?

    >>> On 2/4/2008 at 2:09 PM, in message

    <vpJpj.29140$k06.7783@kovat.provo.novell.com>, Marcel
    Cox<cimetmc@myrealbox.com> wrote:
    > You somehow have the options for both the NetWare and the Linux iPrint
    > plugins mixed.
    > Are you using RBS? If yes, make sure you update your collections. Also,
    > if
    > you don't have any OES(2)/Linux server, then simply remove the
    > iPrint/Linux plugin from your iManager installation.

  • Marcel,

    there is no iManager.bat as referenced in that tid. The only thing
    installed on my system was a shortcut on the desktop to a
    gettingstarted.url

    I DO have ndps installed with the client.

    >>> On 2/5/2008 at 2:25 AM, in message <fo92ih$a2d$1@linux.cie.etat.lu>,

    Marcel
    Cox<cimetmc@myrealbox.com> wrote:
    > Make sure you meet the requirements to run the iPrint plugin on Windows:
    >
    > https://secure-support.novell.com/KanisaPlatform/Publishing/70/3731169_f.
    > SAL_Public.html

  • Did you install the windows server version by any chance? Only the
    workstation version works with the iPrint plugin and the workstation
    version just comes as a ZIP file to unpack and does not include any
    installation program that puts any links on the desktop.

    --
    Marcel Cox (Sysop)
    Discover the new Novell forums at http://forums.novell.com
  • Marcel,

    THAT'S IT!!

    Maybe it's too much to expect that the install for a tools which is only
    supposed to run on server would actually check the OS it's being installed
    to.


    Anyway, after installing the workstation version. We now have the following
    2 problems:

    1 - If you try to create a printer driver profile you get the message:

    Creating and modifying driver profiles is only supported on IE 5.5 and
    above.



    2 - If you launch IE and run it, after you click OK to create the printer
    driver profile, it shows progress bars with LOADING,
    then you get an error window which says:

    Error message: the operation completed successfully.

    Error group: Windows
    Error code: 0


    But you do NOT have the screen where you can manipulate the printer
    settings.


    3 - running it from IE on another workstation, you can get to the screen
    where you can change printer settings, but when you click OK to try and save
    those settings, it just hangs.



    I am at my wits end with the low quality of the management tools for Novell
    environments. At least in the windows world, the management tools just
    work, and you don't waste days of time just troubleshooting a tool to manage
    your network.



    >>> On 2/5/2008 at 4:05 PM, in message

    <Oc4qj.29933$k06.11281@kovat.provo.novell.com>, Marcel
    Cox<cimetmc@myrealbox.com> wrote:
    > Did you install the windows server version by any chance? Only the
    > workstation version works with the iPrint plugin and the workstation
    > version just comes as a ZIP file to unpack and does not include any
    > installation program that puts any links on the desktop.

  • Alberto de_la_Torre wrote:

    >Maybe it's too much to expect that the install for a tools which is only
    >supposed to run on server would actually check the OS it's being installed
    >to.


    Well, technically, iManager 2.7 server does not require any Windows server
    specific component and as such can also run on a Windows workstation. It
    is just common usage for virtually all third party software companies that
    when they provide a server type product, they ask you to run it on a
    Windows server even if technically the product just runs fine on a Windows
    workstation as well. I think this is also related to Microsoft's Windows
    license conditions.

    As for your iManager problems in general, it all boils down to the fact
    the the iPrint/NetWare plugin is the most particular and delicate plugin
    of them all. IT requires native NDPS libraries on the platform it runs on
    and it also requires the IE as browser and the iPrint client activex
    control to be active in the browser. I think Novell never really intended
    this plugin to run on anything else but NetWare servers and it just
    happens to kind of run on Windows workstations as well.
    Most other iManager plugins are platform neutral and for those, you just
    unzip iManager, you install the plugin and you go.

    As for your actual problem, what version of IE is installed on your
    workstation? You have to make sure that the iPrint client is correctly
    installed, and if you are using IE7, you also have to make sure that the
    activex control for the iPrint client is activated in IE.

    --
    Marcel Cox (Sysop)
    Discover the new Novell forums at http://forums.novell.com
  • Marcel,

    I am using IE Version: 7.0.5730.11

    Iprint client is 4.32.00

    iPrint ActiveX control is enable in the browser.

    I get the same behavior when trying create a printer profile for this
    printer whether I use local iManager on xp or the iManager on the server.



    >>> On 2/6/2008 at 2:22 PM, in message

    <fOnqj.30402$k06.13921@kovat.provo.novell.com>, Marcel
    Cox<cimetmc@myrealbox.com> wrote:
    > Alberto de_la_Torre wrote:
    >
    >>Maybe it's too much to expect that the install for a tools which is only
    >>supposed to run on server would actually check the OS it's being

    > installed
    >>to.

    >
    > Well, technically, iManager 2.7 server does not require any Windows
    > server
    > specific component and as such can also run on a Windows workstation. It
    >
    > is just common usage for virtually all third party software companies
    > that
    > when they provide a server type product, they ask you to run it on a
    > Windows server even if technically the product just runs fine on a
    > Windows
    > workstation as well. I think this is also related to Microsoft's Windows
    >
    > license conditions.
    >
    > As for your iManager problems in general, it all boils down to the fact
    > the the iPrint/NetWare plugin is the most particular and delicate plugin
    >
    > of them all. IT requires native NDPS libraries on the platform it runs
    > on
    > and it also requires the IE as browser and the iPrint client activex
    > control to be active in the browser. I think Novell never really
    > intended
    > this plugin to run on anything else but NetWare servers and it just
    > happens to kind of run on Windows workstations as well.
    > Most other iManager plugins are platform neutral and for those, you just
    >
    > unzip iManager, you install the plugin and you go.
    >
    > As for your actual problem, what version of IE is installed on your
    > workstation? You have to make sure that the iPrint client is correctly
    > installed, and if you are using IE7, you also have to make sure that the
    >
    > activex control for the iPrint client is activated in IE.

  • Alberto de_la_Torre wrote:

    >I get the same behavior when trying create a printer profile for this
    >printer whether I use local iManager on xp or the iManager on the server.


    In that case, it is possible that you just have a driver that is iPrint
    unfriendly. Have you checked whether you have the same problem with other
    types of printers?

    --
    Marcel Cox
    Discover the new Novell forums at http://forums.novell.com
  • Marcel,

    the problem is only with this driver. "iPrint unfriendly" is a pretty vague
    term.

    Is there some way to get more information of a technical nature so that we
    can show the vendor what the problem is?


    >>> On 2/7/2008 at 2:43 AM, in message <foec75$92f$1@linux.cie.etat.lu>,

    Marcel
    Cox<cimetmc@myrealbox.com> wrote:
    > Alberto de_la_Torre wrote:
    >
    >>I get the same behavior when trying create a printer profile for this
    >>printer whether I use local iManager on xp or the iManager on the server.

    >
    > In that case, it is possible that you just have a driver that is iPrint
    > unfriendly. Have you checked whether you have the same problem with
    > other
    > types of printers?

  • Alberto de_la_Torre wrote:

    >Is there some way to get more information of a technical nature so that we
    >can show the vendor what the problem is?


    Alas, I don't know. Often, vendors have different drivers for the same
    printer (like PS, "fat" PCl driver, PCL miniport driver ...). Often,
    switching to a different driver type helps. Also, the drivers already
    included with Windows are in the vast majority of the cases compatible
    with iPrint. It's the drivers directly supplied by the pritner
    manufacturers that more often cuase the problem.

    --
    Marcel Cox
    Discover the new Novell forums at http://forums.novell.com
Reply
  • Alberto de_la_Torre wrote:

    >Is there some way to get more information of a technical nature so that we
    >can show the vendor what the problem is?


    Alas, I don't know. Often, vendors have different drivers for the same
    printer (like PS, "fat" PCl driver, PCL miniport driver ...). Often,
    switching to a different driver type helps. Also, the drivers already
    included with Windows are in the vast majority of the cases compatible
    with iPrint. It's the drivers directly supplied by the pritner
    manufacturers that more often cuase the problem.

    --
    Marcel Cox
    Discover the new Novell forums at http://forums.novell.com
Children
No Data