Information Server / DataStage client install fails with error smks49040.

Resolving The Problem

The set of installation errors listed in the abstract all have one thing in common -- the Information Server install failed because the Microsoft MKS Toolkit failed to install.

There are several reasons why this can occur including:

• A prior copy of MKS Toolkit exists at a lower maintenance level that is broken, incomplete, or cannot be overwritten. It may be necessary to remove it before running the installer again.
• Site is installing Information Server Client or Server components into a virtual machine (VM) image which contains an improperly mapped drive (a drive which existed at the time the VM image was created but is not currently accessible).
• Other errors detected by the MKS Toolkit installer, but with no error detail provided to the calling program. In this situation we need to run the GUI version of MKS installer to observe the actual error.

When this error occurs while installing Information Server (server or clients) to a Windows machine on which a prior version of Information Server, DataStage or MKS tools were installed or uninstalled, check the Windows Add/Remove Programs dialog in the Windows Control Panel to confirm if those products or the MKS toolkit are still listed.

If you have prior versions of Information Server, DataStage, or MKS toolkit still installed then you can either uninstall them, or if you do not wish to uninstall them (such as when using multiple versions of the DataStage client), then you will need to perform step 3 in the list below to determine why the MKS installer fails.

If the uninstall of these products does not allow a new install to proceed, then you will need to perform the following steps to manually cleanup any remaining traces of those programs on disk and in the registry and then run MKS installer manually if problems persist. Please note that the step 3 below is for Information Server 8.1 only. If using Information Server 8.0 then the process is still possible but the name of directories where the MKS installer exists are different than listed below.

NOTE! : Only perform these steps if you have already uninstalled Information Server / DataStage from the machine.

1. Remove the following registry key groups if they exist:
   HKEY_LOCAL_MACHINE\Software\Ascential
   HKEY_CURRENT_USER\Software\Ascential
   HKEY_LOCAL_MACHINE\Software\Mortice Kern Systems
2. Remove the following directories/files:
   C:\Program Files\MKS Toolkit
   C:\Program Files\Common Files\InstallShield\Universal\IBM\InformationServer

If the above steps do not resolve the problem, then the next action is to unpack the MKS installer assembly in the IIS Suite Installer and then manually run the full MKS Install using the steps below.   The full install will either fail and provide a more detailed error about cause of failure (such as R/O file, or inaccessible drive), or it will succeed in which case you can then reboot, uninstall, then reboot again, which should remove any remaining conflicts for a new MKS install.

1. If using Information Server 8.0, unpack the install image and navigate to subdirectory:
   client_IA-suite/assemblies/mksinstaller/8.0.0.0
   
   Then copy assembly.dat to a temp directory, rename it to assembly.zip and unpack it and navigate to subdirectory:
   55112414db1327f5682c351288516514
   
   and then unzip file: expandMksClientArchive_compressedFile
   
   Finally, run the setup.exe command in the above unpacked directory to begin the MKS install.
   (Skip to step 4 below)
   
2. If using Information Server 8.1, unpack the install image and navigate to subdirectory:
   client_IA-suite/assemblies/mksinstaller/8.1.0.0
   
   Then copy assembly.dat to a temp directory, rename it to assembly.zip and unpack it and navigate to either of the following 2 subdirectories:
   9b0bd7e69c6dd12fedb83914578c677d
   0e66b19169ab40241848ce72ceee2676
   
   and then unzip file: mks.jar
   
   Finally, run the setup.exe command in the above unpacked directory to begin the MKS install.
   (Skip to step 4 below)
   
3. If using Information Server 8.5, 8.7, or 9.1, then unpack the install image and navigate to subdirectory:
   \is-client\payloads\Shared\MKSClient\payload\oe
   
   Then run the setup.exe command in the above unpacked directory to begin the MKS install.
   
4. The setup.exe command begins the graphical / GUI installation of the MKS Toolkit client software. Just select the default options and progress through the install panels. Once you get to the last panel and start the installation, you should see a more detailed error explaining why the installation failed.
   
   If you are installing into a VM image, then the most common cause of problem is that a drive definition which was valid at the time the VM image was created is no longer attached/valid. If the MKS installer finds any invalid/inaccessible drives mapped, or any inaccessible directories from those drives in PATH, then it will stop the installation. When this happens the error message will indicate the drive letter or path that is causing the problem and you will need to work with your virtual machine administrator to either remove the invalid drive definition, or attach the missing drive.
   
   If there is any error other than invalid drive letter which is reported, and for which solution is not obvious, you may need to discuss the details of error with the Information Server technical support team.
   
5. If instead the MKS install succeeds, then you can do a full uninstall of MKS now via add-remove programs dialog which should clean up everything and allow IIS installation to now proceed past the MKS toolkit install. However, if step 5 fails, then note of the specific error that occurred and correct it since this same error is blocking the MKS install when IIS Suite installer calls the MKS installer.  After correcting, you should be able to then run the IIS Suite installer without installing MKS first.

After any successful install or uninstall of MKS Toolkit, you should then reboot the Windows machine before attempting a new Information Server installation.