Posts Tagged internal error
The below error commonly occurs when you try to add or connect an ESX 4.1 host to a vCenter 4
A general system error occurred: internal error: vmodl.fault.HostCommunication
The initial connection will work and the vCenter will start to deploy its agent on the ESX, but afterwards you’ll get this error. In my case the ESX host was trying to connect to an old retired vCenter 4 which was started by mistake.
Right click on the faulty host and hit connect while connected to the vCenter 4.1 through the VMware vSphere Client.
I got that error after upgrading my VMware Cluster from vSphere 4 update 2 to vSphere 4.1. Also, I had to migrate my vCenter 4 update 2 (on 32-bit Windows 2003 with MSSQL 2005 installed locally) to vCenter 4.1 (on 64-bit Windows 2008 R2 with a remote MSSQL 2008 R2 Cluster) as vCenter must be install on 64-bit OS.
Anyways, after the upgrade everything went fine escept for some issues like this error:
This error may occure because you are using a custom SQL server database with a custom Java Database Connectivity (JDBC) SQL port
Here are the steps to fix it:
- On the vCenter Server system, navigate to: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter
- Open the vcdb.properties file.
- Comment out the string usevcdb = true.
- Ensure that the values for url, driver, and dbtype are as follows or add them (after the “usevcdb = true” line) if they don’t exist:
url = jdbc:sqlserver://<hostname>:<port>;integratedSecurity=true
driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
dbtype = mssql
- Restart the VMware VirtualCenter Management WebServices service.