|
Problem(Abstract) |
During a WebSphere® Application Server installation you
receive the following error in the mq_install.log file:
"<<ERROR>> Internal error code ERROR_BAD_CONFIGURATION (1610)
at line 01512. After this the Embedded Messaging installation will be
completely uninstalled as part of the normal installation." |
|
|
|
Cause |
The WebSphere Embedded Messaging Publish and Subscribe
(WEMPS) installation is part of the overall installation of embedded
messaging. As with other parts of the umbrella installation, if any part
fails to install, the entire installation of embedded messaging is
uninstalled. In this case, information is left in the Windows® registry
from previous installations that embedded messaging interprets as a bad
configuration.
During the installation, a mq_install.log file, similar to the
following, might be generated:
========== Entering Publish And
Subscribe Install =========
WEMPS installation directory is 'C:\WebSphere MQ\WEMPS'
ADDLOCAL="wmqebBroker" ALLUSERS="1" ARPNOMODIFY="1" ARPNOREPAIR="1"
REBOOT="ReallySuppress" INSTALLDIR="C:\WebSphere MQ\W=EMPS"
MsiInstallProduct() returning ERROR_BAD_CONFIGURATION (1610)
========== Exiting Publish And Subscribe Install ==========
<<ERROR>> Internal error code ERROR_BAD_CONFIGURATION
(1610) at line 01512.
Entering WASM Rollback
Removing all of MQ
or
05 Jun 2006 15:35:32 MSI product 'WebSphere MQ Server'
{8B80DC38-31EA-44C4-AA98-4E131C3B487F} is installed
05 Jun 2006 15:35:32 MSI product 'WebSphere MQ Client' is not installed
05 Jun 2006 15:35:32 <<ERROR>> MQ registry key not found
(HKLM\SOFTWARE\IBM\MQSeries\CurrentVersion) (code ERROR_FILE_NOT_FOUND (2)
at line 04834)
05 Jun 2006 15:35:32 <<ERROR>> Installed product 'WebSphere
MQ Server' status is inconsistent (code WASM_ERROR_UNKNOWN (255) at line
08506) |
In either case, the Windows registry contains two keys for the embedded
messaging feature for WEMPS (the first two):
-
HKLM\Software\Classes\Installer\Products\1E5744D76F283AA4AAC375A09C50C9A0\SourceList
-
HKLM\Software\Classes\Installer\Features\1E5744D76F283AA4AAC375A09C50C9A0
There are also two keys for IBM WebSphere MQ:
-
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\83CD08B8AE134C44AA89E431C1B384F7
-
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\83CD08B8AE134C44AA89E431C1B384F7
In the following key there is typically a String Value of name
PackageName:
HKLM\Software\Classes\Installer\Products\1E5744D76F283AA4AAC375A09C50C9A0\SourceList
Note: If this value is not there, or is empty, it can cause the
installation to fail. The normal value for this key is IBM WebSphere
EMPS.msi. |
|
|
Resolving the
problem |
Completely uninstall WebSphere Application Server
according the manual
uninstall instructions for your version and operating system in the
Information Center. Then delete the four registry keys previously listed
and reinstall. It is possible that you might only find one of the
preceding sets to delete.
Installation will be successful if this was the root cause of the
embedded messaging failure. If it is still not successful, uninstall
WebSphere Application Server again and follow the instructions in the
following technote to gather embedded messaging debug information: Setting
verbose logging for the WebSphere embedded MQ installation
Note: Make sure that before you change anything in the registry,
you perform a registry backup and that you understand how to restore the
registry if you encounter problems. For more information, refer to the
Microsoft® Web site. A technote on the Windows registry is located at:
http://support.microsoft.com/default.aspx?kbid=256986 |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|