A General System Error Occurred Internal Error Vmodl
Contents |
multiple servers in multiple locations using Hyper-V shared nothing replication on Windows 2012. VMware View Deployment of VMware view. SBS2003R2 Swing Migration to Virtual 2008R2 Migration from a failing SBS2003R2 running retired exchange, SQL2005, SSRS and PLC SCADA Reporting Software IN THIS vmodl.fault.systemerror vmotion DISCUSSION VMware vCenter Server VMware vSphere VMware ESXi VMware 396221 Followers Follow vmodl.fault.systemerror converter Join the Community! Creating your account only takes a few minutes. Join Now Sorry for the Long post but I saw a similar vmware a general system error occurred invalid fault post on VMware site that went unanswered. Scenario - I needed to move my vCenter 4 to a different server. I backed up and moved the SQL DB (2005 Exp) to the new server. This went smoothly I https://kb.vmware.com/kb/1031652 installed same version of vCenter (4.0.0) on the new server and connected the moved DB - fine went to each ESX4 host (4) and edited the ...vpxa.cfg file to reflect the new vCenter and restarted Services -fine installed vSphere client on new vCenter and connected to the new vCenter. All of my Host from previous installation were visible (But Greyed out/ Disconnected as expected) I proceeded to connect them and got SSL warnings which I ignored (as instructed https://community.spiceworks.com/topic/310120-general-system-error-occurred-internal-error-vmodl-fault-hostcommunication by several posts that I read) I confirmed the decision to pull administration from the previous vCenter. 3 out of 4 of the Host connected without issue (these were all on the same sub net as the vCenter [Not sure if this matters]The The fourth Host (on a different subnet) goes through the same prompts as the others and then states "in Progress" for a loooong time and then errors out with a "General system error occurred internal error vmodl.fault.hostcommunication" Troubleshooting so far - First I tried removing the Host and added it again (this didn't help) I saw some post that stated it might be Name resolution issue - - I updated My Windows DNS to contain all Host Names and IPs (Forward and Reverse lookup). I am able to do nslookup and Ping this Host -I have checked the resolv.conf and it contains reference to my nameservers and domain. -host file is empty (just like the 3 Host that Connected) so I left it alone I restarted the vpxa and vmaware mgt. agents based on some posts iread (sorry of this i not the correct name, I'm still fairly new to VMware) -This did not work so I followed the direction in another post that said I could reinstall them but that did not work either. I turned off all VMs on this host and put the host in Maintena
Cisco Cloud CrossFit ESX ESXi feature goals Homelab Linux Load balancer logging Log Insight Mac NAS Network Review Script Security SSL Storage Synology syslog Travel UCS vCenter Server vCS VMworld vR Ops vSphere Windows This is the personal website of Steve Flanders. The opinions expressed here are http://sflanders.net/2011/04/03/a-general-system-error-occurred-internal-error-vmodl-fault-hostcommunication/ mine and may or may not be the same as my employer. Search for: A general system error occurred internal error vmodl.fault.HostCommunication April 3, 2011Steve Flanders I am in the process of building my home https://vmaze.wordpress.com/2010/09/28/a-general-system-error-occurred-internal-error-vmodl-fault-hostcommunication/ lab. I recently purchased two servers and installed ESXi 4.1 on them. In addition, I deployed a test vCenter Server instance so I could run VUM. With vCenter Server up, I attempted to add the two a general ESXi servers. The first one added without issue, but the second one failed with the error messages:Cannot complete the configuration of the HA agent on the host. See the task details for additional information.Misconfiguration in the host network setupI verified that the hosts were in fact configured identically and then tried to add the host again, but the same error messages were displayed. Based on the error messages, I found the a general system following KB article: http://kb.vmware.com/kb/1019200. Unfortunately, the link did not help.Next, I removed the ESXi host from vCenter Server and tried to re-add it. This time I got a different error message:A general system error occurred internal error vmodl.fault.HostCommunicationFrom this error message I found KB article: http://kb.vmware.com/kb/1012154. This article pointed to name resolution (i.e. DNS) being my issue. I know of the importance of DNS with VMware products and was sure I had verified its configuration, but decided to double check. As suspected, DNS was configured and working as expected.At this point, I decided to restart the management services as that fixes a majority of ESX(i) issues. Upon doing so and trying to add the ESXi server to vCenter Server, I received another new error message:Unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problemThis error message pointed me to KB article: http://kb.vmware.com/kb/1003409.Again I tried everything suggested and was still receiving the same error message. At this point, I was frustrated. I decided to reboot the server just in case that fixed the issue. Upon restarting, the error message want back to the vmodl.fault.HostCommuncation one.What was going on and how could this be fixed?At this point I was out of ide
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.  Reolution: Right click on the faulty host and hit connect while connected to the vCenter 4.1 through the VMware vSphere Client. Like this:Like Loading... configuration error, internal error This entry was posted on September 28, 2010, 12:23 PM and is filed under Uncategorized. You can follow any responses to this entry through RSS 2.0. You can leave a response, or trackback from your own site. Comments (0) Leave a comment Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Administration (3) Information (3) Installation (1) Troubleshooting (2) vCenter (1) Uncategorized (1) Archives January 2011(2) September 2010(1) August 2010(1) June 2010(2) Blog at WordPress.com. %d bloggers like this: