Visual Studio setup fails to launch when SAP GUI client is installed


I have heard of a few cases where Visual Studio .NET 2002, 2003 or 2005 setup fails after launching the main setup.exe launcher screen and clicking on the first link to start the setup process.  The error dialog that appears has the title Setup Initialization Error and an error string that looks something like the following:



Setup cannot access the required initialization file ‘C:\PROGRA~1\SAP\FRONTEND\SAPGUI\FILC\ODBC\AUNCHER=”C:\DOCUME~1\USERNAME\LOCALS~1\TEMP\”‘.


There is a compatibility issue that prevents Visual Studio setup from being able to copy itself to the %temp% directory and relaunch itself if the SAP GUI client application is installed on the computer.  The telltale indication that you’ve hit this problem is the \SAP\FRONTEND\SAPGUI\ information in the path listed in the error dialog during VS setup.


As a workaround, you can temporarily uninstall the SAP GUI client, install Visual Studio and then re-install the SAP GUI client if needed.


 

Comments (21)

  1. Des Browne says:

    Over the last few years I have run into so many MSI setup issues that were caused by SAP Gui.

    One customer was unable to install many software products they had bought because of MSI issues caused by SAP Gui. I spent an entire day editing the registy to find and fix the issues caused by SAP Gui, the customer then had to deploy the fixes (they had over 3000 PC’s at the time, a significant number were running the SAP Gui).

    Needless to say the customer was extremly happy that things worked after my fixes and we got the sale, but SAP was such a mission critical program to them that had I not fixed it then employees would not have benifited from the other software.

    Those SAP Gui setup guys and girls should get their act together.

  2. Sander Hoogwerf says:

    I had the same problem error and found a workaround by renaming the registry entry HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionApp Paths<b>setup.exe</b> to something else e.g. <b>sapgui_filc_odbc_setup.exe</b>.

    After this I could update my Visual Studio 2003 setup without the need to reinstall the SAP GUI client.

  3. Rob Pringle says:

    Thanks Sander – worked for me

  4. Samus Aran says:

    Worked for me too, does it matter if I leave the setup.exe entry that way permenently?

  5. Christian Zalto says:

    Thanks a lot, Sander! This information just saved me hours of work…

  6. jordi says:

    Also worked for me. Thanks !!

  7. Really great… It works for me too… Great discovery dear 🙂

  8. Philip says:

    thanks thanks thanks thanks 🙂

    problem solved

  9. Bhaskar says:

    Problem solved Thanks a lot .Really very great .

  10. Antonio says:

    Excellent!

  11. Thomas says:

    Tanks a lot! Great!

  12. Bruno Luz de Souza Nogueira says:

    Solved!

    Thanks

  13. Robert says:

    works for me too… thanks for the time saver

  14. Julian Yap says:

    Brilliant, Sander.  Saved me hours.

    Thanks.

  15. Jared says:

    All Hail Sander!!!

    Thanks a ton.

  16. Adi says:

    Hello, Thanks very much .. worked for me too 🙂

  17. jayson says:

    You saved lots of my time. Thanks a lot.

  18. John P says:

    Actually, it is better to clear the data from the "(Default)" value, and delete the "Path" value completely, yet leave the other two values there and untouched (BlockOnTSNonInstallMode and RunAsOnNonAdminInstall) because they are standard entries for the "setup.exe" registry key.

  19. Richard Acton says:

    Sander’s solution worked for me too.

    Thanks chaps.

  20. mreddish says:

    Thanks so much for helping me with this.

  21. abhishekkhaitan says:

    Thanx sander…worked for me too….

    Cheers!

    Abhishek