Cannot update iManager 2.6 plug-ins after applying NetWare 6.5 Support Pack 6

  • 3561801
  • 24-Apr-2007
  • 26-Apr-2012


Novell iManager 2.6
Novell iManager 2.6 Maintenance Update 1
Novell iManager 2.6 Support Pack 2
Novell NetWare 6.5 Support Pack 6


Cannot update plug-ins after applying NetWare 6.5 Support Pack 6

Temporary npm files (i.e. ldap_plugin.npm2007551344) are being left behind in the webapps/nps/packages directory.

Plug-ins say they are downloading, but they do not get installed.
iManager plugins failed to install


1. Uncheck the Read Only flag on all the files in the webapps/nps/packages directory (so they are read write).
2. Remove (delete) all files with the date extension on them such as plug_in_name.npm2007551344.npm. These files should be duplicates of a similar to an original plugin already in the directory. plug_in_name.npm.
3. Restart Tomcat (TC4STOP and TOMCAT4 on NetWare)
4. Login to iManager and re-install the plugins, and restart Tomcat again. This time they should take the plugin installation.
5. Make sure you install the iManager 2.6 sp3 update on the server.

Additional Information

This problem is caused by read-only npm files in the webapps/nps/packages directory and only happens on NetWare. When Support Pack 6 is installed on a NetWare 6.5 server, iManager 2.6 is installed by default. When the new set of plug-ins is copied down to the packages directory, they are all flagged read-only.

When you try to update/install a plug-in through the plug-in download feature in iManager 2.6 it creates a temporary file during the download named something like plug_in_name.npm2007551344.npm. Once the file finishes downloading, it is supposed to remove the existing plug-in and rename the temporary one, but it can't because of the read-only flag. In most cases, the new plug-in is not installed and the temporary file is left behind in the packages directory. After

This has been resolved in iManager 2.6 Support Pack 3 or greater. If you have not yet applied Support Pack 3, you can work around this issue by simply going to the nps/packages directory and removing the read-only flag on all the npms in the directory.