- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Installation of component VCSServiceManager failed for vCenter 6.0
Hi
When installing vcenter 6.0 i get the below errors; I see that there are solutions on the vcenter release notes page -https://www.vmware.com/support/vsphere6/doc/vsphere-esxi-vcenter-server-60-release-notes.html they are not working for me.
Error 1:
An error occured while starting invsvc.
VMWARE workaround: Workaround: Use the IP address or the host name of the database server to create a DSN.
Does not work for me, i use the full hostname on my DSN
Error 2:
Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.
VMWARE Workaround: Before you install VMware vCenter Server 6.0.0, make sure the IPv4 stack is installed. If the command netsh interface ipv4 show interfaces results in a message: The request is not supported., the IPv4 stack has been uninstalled and should be reinstalled. To reinstall the IPv4 stack, run the netsh interface ipv4 install command and reboot the machine.
I don't get the error the request is not supported. No errors at all. Even if i uninstall the ipv4 stack and install it again, problem still persists.
or
VMWARE Workaround: http://kb.vmware.com/kb/2113068
My DSN sql server connection string dont have a trailing white space, and i even changed the DSN name, I changed the sql server connection name to the IP. Same error.
I even tried the solution provided on this site: http://christopher-technicalmusings.blogspot.com/2015/04/installing-vcenter-600-gives.html
Does not solve my problem.
Your assistance will be appreciated. Thanks
Regards,
Mervin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Mervin, I keep getting the same exact errors as you when installing vCenter 6.0. Let me know if you come across a solution! I'll be looking into this as well.
-Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fixed my issue. I went into SQL Configuration Manager and enabled "Named Pipes" and "TCP/IP" and it works. Don't know if Named Pipes is necessary.. maybe only TCP/IP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having this same issue, but in my case the installer seems to be failing when trying to install the syslog collector. I have a case open with VMware, but they aren't very helpful at this time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We got the same Issue - Installation fails with error 1603 during Syslog Collector installation..
2015-07-21 14:42:23.432+02:00| vcsInstUtil-2800572| I: ParseStatusFile: Failed to parse file "C:\ProgramData\VMware\vCenterServer\logs\firstboot\fbInstall.json" containing: "{
"status": "error",
"info": [],
"question": null,
"progress_message": {
"args": [
"VMware Syslog Collector"
],
"id": "install.ciscommon.component.starting",
"localized": "Starting VMware Syslog Collector...",
"translatable": "Starting %(0)s..."
},
"warning": [],
"error": {
"resolution": {
"id": "install.syslogcollector.fileSR.resolution",
"localized": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a support request.",
"translatable": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a support request."
},
"detail": [
"Operation exceeded maximum number of retries",
{
"id": "install.syslogcollector.error.install_service",
"localized": "Unable to install the Syslog Collector Service.",
"translatable": "Unable to install the Syslog Collector Service."
}
],
"componentKey": "vmsyslogcollector",
"problemId": "install.syslog.fileSR.resolution"
},
"progress": 80
}"
@ Services.msc we noticed that the Syslog Collector is installed and we are able to start it, but the installer thinks different ![]()