Problem
You attempt to install VMware View Composer on your Windows server but the process fails with the following error:
The exception unknown software exception (0xc0000409) occurred in the application at location 0x6d3afe35.
Click on OK to terminate the program
![clip_image001[4]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiiwk5FJeuiqpgUe5-LIkG5LY1zdQNCVsgS2URAgq2QvH7GGItaYVMXXQZC8AGLCpfgBpHrfHe2uTpoiDVlKMIk6YO7aI9nHlU0g5lLvKxIBf7p-2RVd91W1E6SAV_p9Rjn2H23BvMKX4XM/s1600-h/clip_image001%25255B4%25255D%25255B2%25255D.png "clip_image001[4]")
Solution
I’ve encountered this issue back in the View Composer 2.x days and was surprised that even at version 3, we would still need to run the install as an administrator regardless of whether UAC was turned off:
![clip_image001[6]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgTVEzuZIkdwtHRSnOSIIIxE9q8DV3WY-NEOtFXMzgqVKzka2CeiZsuEnzYZAoilUFqbGE9gGHv5HAMb8yZDnrcdzXWtrY0BaS_vvKosyfDQjjoY8F9qiqLs1fHInBPV74pwNA_UvlN4-e-/s1600-h/clip_image001%25255B6%25255D%25255B2%25255D.png "clip_image001[6]")
Proceed with closing the failed install wizard and run the installation executable as an admnistrator:
![clip_image001[8]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9SwKHv58X0MoqhLPiuhmXxV1fnvEg6qmE9twqtQSC9mCZ2e_LaJ6DAxMv-Afxy-tps3-pe6lDLVcMpSH8mU37IdXEJpoIHLMtiZdQ4YljLSPfRQsJu60jldoIXlllkkyYLQ0JJ9BPankr/s1600-h/clip_image001%25255B8%25255D%25255B2%25255D.png "clip_image001[8]")
The install should now complete:
![clip_image001[10]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiEI84dQeZAGAd5y3hYqGUq4gR0f2b8NZksHqyJBoJWPrkuebE3bzCHTfCuZ-JHZmD9XpR4RCMho0b-k_9FvCnc0hrUisAhLhqLcRnCpAhM1L27uDNGYvG5_ZuKx6KYES1mD_PTAURUVB16/s1600-h/clip_image001%25255B10%25255D%25255B2%25255D.png "clip_image001[10]")
6 comments:
thanks buddy this was helpful
Helped me too!!!!
Thanks!
Thanks a lot for solution!
Nik
Thank a lot for this solution. I met it in version 5.3
Saved me a ton of time .. thank you!
As simple as this was, I found this post very useful. It did give me a chance to verify the Product Compatibility Matrix while troubleshooting, though, which let me downgrade to vCenter 5.5 Update 1 from Update 2. This was for Composer 5.3.
Post a Comment