iPrint Client Management Plugin doesn't work with Role Based Services

  • 3402254
  • 18-Jan-2007
  • 26-Apr-2012

Environment

Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 5
iPrint Client Management (iCM)

Situation

iPrint management features do not exist or function properly after updating the iPrint iManager plug-in because of one of the following:

  • The new iPrint iManager plug-in does not always install properly and files are occasionally not updated.

  • The iManager un-install process does not consistently work.

Resolution

Uninstall and reinstall the iPrint iManager plug-in by completing the following steps. If you are using Role-Based Services (RBS), start with Step1; otherwise, you can start with Step 3.

1.Uninstall the RBS iPrint Management objects from eDirectory if you are using RBS

a. In iManager, click the Configure button (icon of a person sitting behind a desk).
b. Click Role Based Services -> RBS Configuration.
c. Click the number listed under in the Installed column for the collection to display a list RBS modules that are installed.
d. From the list, select the check box for the iPrint plug-in and click Uninstall.
e. After the uninstall is complete, click RBS Configuration from the left menu. The Not-Installed column should be incremented by one for the collection.

The RBS iPrint Management objects have been uninstalled from eDirectory.

2. Validate iPrint Removal from RBS and uninstall the iPrint Management plug-in if necessary

a. From the RBS Configuration page in iManager, click the Collection name that iPrint was installed in.
b. If iPrint appears in the list, select the check box for the iPrint module and click Delete.

iPrint has been uninstalled from RBS, but the iPrint iManager plug-in is still installed and must be removed.

3. Uninstall the iPrint iManager plug-in

a. In iManager, click the Configure button (icon of a person sitting behind a desk).
b. Click Module Installation -> Installed Novell Plug-in Modules.
c. From the displayed list of plug-ins, select the check box for the iPrint plug-in, then click Uninstall.

A message displays, indicating that the NPM has been successfully uninstalled and that the Web server must be restarted. The iPrint iManager plug-in should now be removed from the iManager file structure; however, continue with Step 4 to restart the Web server and validate iPrint's removal from the file system.

4. Restart the Web server and validate removal of iPrint plug-in files

a. At the server console, enter tc4stop
b. From a mapped drive to the NetWare server where iManager is running, do the following:

  • In the sys:\tomcat\4\webapps\nps\portal\modules directory, delete the iPrint subdirectory.

  • In the sys:\tomcat\4\webapps\nps\WEB-INF\modules directory, delete the iPrint subdirectory.

  • Starting from the sys:\tomcat\4\webapps\nps directory, search for files or folders containing iprint in the name. Delete any files or folders your find. Repeat the search to confirm that there are no files remaining that contain the iprint in the name.

c. Copy the latest iPrint iManager plug-in into the sys:\tomcat\4\webapps\nps\packages directory. (You can downloade the latest iPrint iManager plug-in from https://download.novell.com.)
d. At the server console, enter tomcat4. It will take some time for Java and Tomcat to load.

5. Install the iPrint Management plug-in to iManager

a. Log in to iManager.
b. On the initial iManager screen, there should be an indication of new modules available to install.
c. Click install.
d. From the displayed list of plug-ins, select the check box for the iPrint plug-in and click Install.

A dialog displays indicating that the NPM has successfully installed. The iPrint iManager plug-in is now installed. If you need iPrint to run with RBS, continue with Step f.

f. Click RBS Configuration on the dialog.
g. For the collection where you want iPrint installed, click the number in the Not-Installed column.
h. From the RBS Modules list, select the check box for iPrint and click Install.
i. After installation is complete, you need to restart the Web server. You can restart the Web server using the following commands:
tc4stop
tomcat4