Installation prompts at the beginning of the installation with a msiexec help dialogue (NETIQKB70526)

  • 7770526
  • 18-Jul-2007
  • 28-Sep-2009


Security Manager 6.0


Security Manager installation prompts at the beginning of the installation with a msiexec help dialogue. This is actually an indication that the Visual Studio C++ redistributable shipping with Security Manager's installation is in fact failing.


When installing Security Manager, in a few isolated cases an environmental issue causes the installation of a dependency to fail without warning. The installation will appear to succeed, the only indication that the installation will fail is an msiexec /help window popping up three times.

What happens is that in the environment in question, there is a problem with the way the path is built for installing vcredist, a requirement for Security Manager to function, is not built correctly. The result is that the 3 installers for vcredist are not installed, and the subsequent Security Manager installation has many different, random problems.

In order to resolve this, you must perform the following steps.

  1. Start the installation
  2. An msiexec /help dialogue will appear. Do not click on OK. This is where the vcredist distributable fails to install, and you will need to gather vcredist from the file system in order to manually install it. 
  3. Search the file system for vcredist* . The first time you do this, you should find an x86 vcredist installer. The other vcredist installers will be for itanium and ia64.
  4. Copy the vcredist installer into a safe location.
  5. Click OK on the msiexec /help window.
  6. Perform steps 2-4 again. At each prompt do a search, and then find the vcredist on the file system..
  7. Once you have gathered each of the 3 vcredist installers and clicked through each msiexec /help dialogue, cancel the Security Manager installation.
  8. Run each of the 3 vcredist installers. 2 of them will fail, one will succeed.
  9. Once that is done, perform the Security Manager installation.
  10. Restart the central computer.
  11. Launch the Monitor Console.

If these steps were successful, the Monitor Console will launch correctly. If it does not launch correctly, there may be an error about the snap-in not loading, or the class id not being registered.

If the Monitor Console did not launch correctly, you will need to perform the installation again, this time as a local administrator at the physical location, or by using a remote administration card or remote desktop with the /console switch from the run line. You may need to do this multiple times within different user contexts until the installation is successful.


An environmental error is causing this installation problem. Typically this can be addressed by using a different context and following the fix steps below.

Additional Information

Formerly known as NETIQKB70526