Skip to Content

*upgrade info* BI 4.1 SP01 on Windows – missing installation prerequisites: Microsoft Redistributable Package


It’s recently come to my attention that our BI Platform 4.1 installer is causing some worries to a few Windows customers. This concerns the BI 4.1 SP01 upgrade, for both the in-place update patch or side by side installation.

The installer doesn’t seem to flag all the necessary pre-requisites, missing hotfix updates to windows distributables. The missing piece can be found here: “Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update x86 and x64 executables“.

This problem gives various symptoms, better described by the follow knowledge-base articles:

In brief, the solution is to rollback the update; add in these missing 3rd party components, then reinstall the upgrade again. After this the environment is recovered.

For information, the following errors are captured installation logs:

  • ERROR: An unexpected internal error occurred. The CMS failed to start: CreateProcess error=14001, The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (FWM 23026)

& also in the Event Viewer’s log:

  • Activation context generation failed for “E:\APPS\BI4\SAP BusinessObjects Enterprise XI 4.0\win64_x64\SvcMgr.exe”. Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=”amd64″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.6195″ could not be found. Please use sxstrace.exe for detailed diagnosis.

I hope this information is of use to the community!



You must be Logged on to comment or reply to a post.
  • Thanks for sharing such useful information Henry.

    Many Users have been facing this problem repeatedly.

    Finally we have a good solution to this available now.

  • I appreciate this information.  However, how is it that updates with these issues get released?  I understand there are numerous configuration possibilities and it is not reasonable for SAP to account for and test all of them.

    We had difficulty going from 4.0 SP06 to 4.1 SP01 on our test system.  Our solution was to move right along to 4.1 SP01 Patch 2 and that seems to be working.  We are going to make the 4.0 SP06 to 4.1 SP01 to 4.1 SP01 Patch 2 in our production environment this weekend and hope for the best.


    • Can’t speak to the efficacy of the repair install alone on a BI 4.0 installation, but in the 4.1 install on 2012 it took a full removal and reinstallation to get beyond the log errors. Worth noting that in the 4.1 install the Microsoft Visual C++ 2005 redistributable package SP1 wasn’t enough to resolve it either, it took the specific “MFC Security Update” package version before it worked.

  • Hi Henry,

    Thanks for providing this info.

    Some additions from my side:

    – This issue also occurs when updating to SP2, it’s definitely not limited to SP1!

    – If the installation of the mentioned VC++ 2005 SP1 MFC Update fails
      (Error 1935 in our case),

      check if the Windows Service “Windows Module Installer” is started

    The info about this issue should be easy available to all customers which are updating to 4.1 SPx. I checked all available official release info in preparation for this update for several days and I wasn’t aware of the issue because I didn’t recognize this post, which is unfortunately not part of the official update info. This has caused a complete day of work for nothing on my side, which could have been easily avoided…



    • Many thanks for your diligent feedback. Indeed, this is proving to be a pain-point… the community will surely appreciate your findings.

  • This also occurs with the  BIP 4.1 SP2 full install.  Instead of completely uninstalling and reinstalling, I’m going to try to do a repair install to see whether that will get things up and running.


    • Dell, in my case a repair did not register the 32-bit libraries which are missed during the original install so it required remove/reinstall for that process to happen. Of course after you do the repair check the setupengine.log and search on error. If you see a large amount of them in batches referring to dll’s then the repair didn’t do the trick.

      I certainly hope it does for you; feedback about whether the repair install works for this in your case would really help!

  • Thanks for the write up, I’ve been struggling with this all day. I am attempting to upgrade from BI 4.0 SP04 to 4.1 SP02.  When looking at my Windows program list I also have Microsoft Visual C++ 2008 packages… should those be removed also before re-installing just the two 2005 packages? I fear that other things might depend on them, does anyone know an answer to this?

  • I have been having this problem on one of our servers when upgrading from BI 4.0 to BI 4.1 SP02. I tried the steps mentioned but it looks like the vcredist_x86 and _x64 files that I downloaded from MSFT website just don’t install…I keep getting an error and now I have no VC++ libraries installed.

    I unsintalled 4.1 SP02 and went back to 4.0 SP06 and that seems to be working again. Any ideas what might be going on?

    Here’s the error I get installing the vc++ libs:

    Error 1935. An error has occurred during the installation of assembly


    • Sarang,

      Unfortunately “Error 1935” is the most generic of the Windows Installer errors and doesn’t indicate any specific failure, only that it could not install for some general reason. Run Windows Update and make sure the system is up to date on patches and fixes first. Reboot, and if the error persists try using the replacement for the old Windows Installer Cleanup Utility: the Microsoft Fix It repair utility for the Windows
      Installer at

      Beyond that it’s best to contact Microsoft before doing anything further that involves registry editing or deleting any files.

      • I was actually able to get it to work finally. Uninstalling BI 4.1 didn’t help so I had our Server team restore that VM from an earlier snapshot. Tried the install again with that, and it worked this time around. Not sure what was different!

    • Hi Sarang,

      As stated earlier in this thread:

      – If the installation of the mentioned VC++ 2005 SP1 MFC Update fails
        (Error 1935 in our case),

        check if the Windows Service “Windows Module Installer” is started.

      Starting the service solved the issue in our case.



  • I installed last week a full 4.1 SP6.

    The issue ist not fixed. Same problemens.

    But i think i depends on your image. I only have this problem with one costumer. All other, incl. my local VMs work fine.