Reinstalling WAS with embedded messaging

 

If WAS embedded messaging is installed, the component can not uninstall cleanly when the product is uninstalled, and can cause problems upon reinstallation.

Some components of the product may not be uninstalled properly, which can cause problems when the product is reinstalled.

Remove messaging objects such as Queue Connection Factories and Queue Destinations from the configuration,using the administrative console page or wsadmin command tool, before uninstalling the product.

If these objects are not removed prior to an uninstall, the Messaging component detects that these objects still exist and, by design, will not uninstall itself. The file mq_uninstall.log will show messages similar to these: 

Publish And Subscribe configuration exists>> 
Not uninstalling Pub Sub MQ Server configuration exists 
not uninstalling MQ and MA88

In this case, it may be possible to simply reinstall the product, including embedded messaging. The installation will detect that the messaging component is already installed, and write error messages to indicate this. In this case it is recommended that you proceed with the installation. If the installation is successful, recreate messaging objects in the administrative console, but use different names for messaging objects than in the prior installation. Further steps, such as manually uninstalling embedded messaging in the Windows control panel, or editing the Windows registry, should not be attempted unless you have tried a reinstallation and it cannot complete or does not create a usable WebSphere Application Server.

If the reinstallation is not successful, follow the steps below for manually deleting the Messaging component, then reinstall WebSphere Application Server with messaging.

Even if all JMS resources, such as Queue Connection Factories and Queue Destinations, have been removed, or none have been created, it may still happen that the messaging component will not uninstall completely, and will cause the reinstall of the product to fail. This is indicated by the following message in the mq_uninstall.log file: 

Return code from Publish And Subscribe uninstall was ERROR_INSTALL_FAILURE (1603)

Again, the message may be innocuous, that is the messaging component may be still resident and usable, and the recommended resolution is to first try reinstalling WebSphere Application Server with messaging, in the same location as before, ignoring messages indicating that Messaging is already installed, and to proceed normally unless problems are encountered.

If the reinstallation does not complete, or the reinstalled product does not behave correctly, follow these steps to manually remove the Embedded Messaging subcomponent so that the reinstallation will succeed:

 

Uninstalling embedded messaging on Windows platforms

First, try using the Add/Remove Programs application in the Windows Control Panel to remove IBM MQ and IBM WebSphere EMPS . This ensures that the programs are removed properly.

If the automated removal does not work, follow these steps to manually remove the programs:

  1. Delete the product's registry keys by removing the key HKLM\SOFTWARE\IBM\WebSphereEmbeddedMessagingPublishAndSubscribe .

  2. Delete the product's files.

  3. Delete the product's Microsoft Software Installer (MSI) record. Use Microsoft's "MSI Cleanup Utility", available from Microsoft's Web site as msicuu.exe :

    1. Click on the downloaded .exe file to install it. Once the program is installed, it appears on the program menu. When started it lists all the products that MSI knows about.

    2. Select IBM WebSphere EMPS and click Remove to remove its MSI record.

  4. Reboot and reinstall.

Troubleshooting by component: what is not working?
Troubleshooting installation problems

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.