this is correct, Anders

A bug or features? but will be solved with oes24.4, is also in iprint appliance, npm will be see to installed, you select the items, but they will not installed!

we are all not happy, but what can you do? nobody is interested by ot

It appears to be hit or miss as to when that happens.  It has been fine for most of the servers I've dealt with.  With the workaround for those impacted being to just install one at a time, restarting tomcat each time.

I have seen similar. I picked 4 to update and went in lala land. I closed imanager and restarted tomcat. Tried again. The same thing.

Restarted again. Picked only one nom to update. It did work but took 30 minutes. First time ever seen that. Was not even that slow in the old days. Was identical on 2 servers.

Yes, that is the new way of installing npms. Obviously there is an error in the installer script - and/or a compatibility problem of the imananger framework with the newer server modules, which leads to errors in the uninstall process, which can hang completely, hang for a long time or - seldom - work correctly. If you manage to uninstall the modules to be upgraded, the simple install of the new modules takes only a few seconds - and not even one minute.

I will forward the info about potential error in script - however, the PM in charge is out of office, it may take some time. 

Caroline, this a general trouble on oes24.3 and also on iprint appliance 24.3

I have become the information from ot-support that this will be solved in the new version 24.4

Prindl speak from new method to install/deinstall. Can you explain?

The "new method" was ironically meant for the troubles this gives.

If the installation of a npm stalled or was hung I looked into the logs and in all cases found, that the installer had exitet from uninstall with an error-code and did not proceed any further. Mostly the uninstaller had already removed the old version, but did not update the list of installed npms. So restarting the install (after restarting novell-tomcat) mostly errored again, because it tried to uninstall the already uninstalled old version of the npm.

You can manually uninstall npms outside of the update process and that approach sometimes worked great, but not in all cases.

But in theory, if you have 2 servers with the same SLES and OES patch levels, you could copy the whole /var/opt/novell/iManager directory from a working iManager instance to a not working server and that should work on the other server. You need not even change the server.cert file, if both servers are in the same  tree. Maybe you have to change file permissions. Interestingly the server, which had the fewest issues with npm updates had a server.cert certificate, which was not in use any more as the CA had been recreated in the meantime.

I remember the days of Novell / Microfocus where updates were made very quickly when errors occurred,
 but OT probably wants to annoy and scare away all of your customers!
this situation is for all products, not only oes and imanager
i am crying and who stop OT, my trust is flying away, i am to old to anderstand the politic from the new direction.
How long will this allow a survival?

Caroline, are all you ot product manager in holiday and this since passing from MF to OT

sorry for my post, but this is the verity, bad or non existing support, no assistance on your latest customer!

Do you see any (likely java-related) errors in /var/log/messages at that time?