9 Responses

  1. Bjoern Roth
    Bjoern Roth at |

    IIRC it is best practise to use local system as service account for all VMware vCenter services. The connection to the Database is established through ODBC entries where you can enter the Domain Account which has the rights to access the DB. Am I wrong here or did I get something wrong?

    Reply
  2. Matt Lattanzio
    Matt Lattanzio at |

    I just upgraded our new vCenter from 5 to 5 U1 and confirmed that it does set the service account back to local system. Good catch man!

    Reply
  3. syn3rgy
    syn3rgy at |

    Can confirm I had the same issue. Change the service account from Local to my domain account and boom, all good.

    Reply
  4. SzYmOn
    SzYmOn at |

    vCenter Service Status: cannot access the health service!
    I changed to start services via domain account and problem still exists.

    2012-03-30 13:07:51,949 INFO main com.vmware.vsm.vc.KeyStoreManager – Loading keystore
    2012-03-30 13:07:52,058 ERROR main org.springframework.web.context.ContextLoader – Context initialization failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘keyStoreManager’ defined in ServletContext resource [/WEB-INF/vsm-tomcat.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vmware.vsm.vc.KeyStoreManager]: Constructor threw exception; nested exception is java.lang.Exception: Unable to find the vCenter server certificate

    Cert is OK, I checked many times and read *all* articles on KB and Communities.

    Any solutions ?

    Regards,


    Szymon

    Reply
  5. Julian Merkl
    Julian Merkl at |

    same problem. I opened an SR @vmware and hope they will document it in the KB

    Reply

Share your point of view!