Why won't MQ install for me? Common install problems for WebSphere MQ on Windows
TiffanieWatkins 060000CVJ9 Visits (7901)
Installing WebSphere MQ on Windows should be easy. Once you have performed your backup and installed the prerequisites, you should have smooth sailing. You click the setup.exe file from the cd, make your installation choices and there it goes! You might even walk away to get a coffee because you just expect that it will complete successfully. You come back and find that MQ did not install. What?! Why? There are various causes but let's look at a few very basic reasons why MQ does not install.
The most basic and most common cause is that the installing user does not have the correct authority to run the installation. The userid MUST have local administrator authority when you are installing. This authority is defined through the Windows facilities. More information about security can be found in the Security considerations section of the WebSphere MQ information center.
Another common issue is that the installation hangs while doing the install of gskit. You can determine this by looking at the end of the install log for an entry for gskit. To get around this, you can manually install GSKit using the instructions found in the technote entitled WebSphere MQ V7.0 Installation hangs at almost 100% showing status as writing to temp file amqt0001.txt.
Lastly, the amount of time that the installation takes (when upgrading to V7) can be perceived as a problem. This has been researched and there is no part of the install that is lagging. For more information, see the technote entitled Length of install when migrating to Websphere MQ V7.