Wednesday, April 1, 2015

Installing vCenter 6.0.0 gives: Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.

I'm rolling out a new vCenter 6.0.0 install from scratch to test our environment on it, and quickly ran into a show stopper:

 Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.

I was installing on a fresh new Windows 2012R2 server with all the updates, but I hadn't installed the .NET 3.5 feature. 

The release notes from VMware mention this exact error, but in the context of an ipv4 address issue, so that wasn't much help, as all of my ipv4 addressing was correct. 

After a bit of poking around, I noticed that a 1603 error in a MSI is often due to .NET being missing.

After installing .NET 3.5 and updates, the install worked properly.

There is no mention of .NET being required in the Release Notes, the Windows Requirements, etc. 

Hopefully that saves someone a bit of time. :-)

Now let's see what that new Web Client performs like. 
Posted by at
Labels: , , , , ,

10 comments:

  1. UnknownApril 21, 2015 at 11:27 PM

    Thanx dude, you saved my day

    ReplyDelete
  2. UnknownMay 22, 2015 at 5:07 PM

    I'm installing .Net 3.5 on my 2012 R2 server as I write. If it works... You Da Man!!! (I'm guessing it will).

    ReplyDelete
  3. ChristopherMay 22, 2015 at 5:09 PM

    I am Da Man, this is true..

    ReplyDelete
  4. UnknownMay 22, 2015 at 5:26 PM

    I just finished installing .Net 3.5 on my Windows 2012 R2 server. It allowed me to install vCenter Server 6.0 successfully. Thanks for the info!!! ...and no thanks to VMware for not mentioning that little factoid!

    ReplyDelete
  5. ChristopherMay 22, 2015 at 5:30 PM

    Yeah, I'm starting to notice that vVMware's KB articles are not as accurate as I'd like them to be - I have 3 or 4 regular errors that all have KB articles with VMware, and each article states that the error is fixed in 5.1, or 5.5 U2, etc.. yet they still happen.

    ReplyDelete
  6. UnknownSeptember 29, 2015 at 8:25 PM

    I spent all day trying to get vCenter 6 to install on my 2nd vCenter. The first one I apparently installed .NET 3.5. I created a template which the second one was deployed from and I missed that.

    Thank you for making me feel a touch less crazy...

    ReplyDelete
  7. SlavkoApril 22, 2016 at 3:49 AM

    Thank You!!!

    ReplyDelete
  8. Black LionJune 7, 2016 at 9:04 PM

    Have the same problem but .Net installed and nothing :(

    any help? :(

    ReplyDelete
    Replies
    1. Márcio LuizFebruary 22, 2017 at 1:16 PM

      Worked to me, but it was impossible using the same server. But worked after I deplopyed a new one. First of all, add a .NET 3.5 Framework and then windows updates, reboot e voilá!

      Thanks!!!

      Delete
  9. BrendanFebruary 14, 2017 at 5:46 PM

    can also be if you have disabled IPv6 on NIC https://www.pickysysadmin.ca/2016/06/24/error-1603-when-upgrading-vcenter-6-0u1-to-6-0u2/

    ReplyDelete

Subscribe to: Post Comments (Atom)