VMware Cloud Community
ufo8mydog
Enthusiast
Enthusiast
Jump to solution

A general system error occurred: Internal Error

Hi there,

I'm completely puzzled by this error "A general system error occurred: Internal error"

I am using a trial VI Client (55 days remaining) with one ESX 3.5 host. The VMs are stored on an iSCSI SAN. I added several VM's and was able to load the O/S and start them up.

However, for no good reason after a couple of days it started popping up with "general system errors" when I attempted to power on the virtual machines. I can still create new VM's, there is a VM that is still running, and judging from the SAN the host has had a continuous connection to the LUNs.

Just to finish off the saga, last night I changed the time on the ESX host. It miracously started working and powering up VMs on command - but as soon as I added an additional VM things went pear shaped.

Reply
0 Kudos
1 Solution

Accepted Solutions
mattjk
Enthusiast
Enthusiast
Jump to solution

Quite possibly your problem / related: http://communities.vmware.com/thread/162377

Cheers, Matt

View solution in original post

Reply
0 Kudos
10 Replies
ryath
Contributor
Contributor
Jump to solution

I am also suffering this problem. Just setup 1 new server, ESX 3.5 Update 2 and configurd the basics and boom internal error. I setup a HP server last week, VM's ran fine. Now its internal error.

Time is correct on both.

License is trial with at least 40 days left on both.

So yeah no idea.

Reply
0 Kudos
BUFFALOIT
Contributor
Contributor
Jump to solution

I am also suffering this problem.

problem happend on 4 ESX 3.5 U2 Servers.

License is not trial but perchaced.

Reply
0 Kudos
timw18
Enthusiast
Enthusiast
Jump to solution

Check out the following post for possible solutions to this issue http://communities.vmware.com/message/523893

Reply
0 Kudos
McBain
VMware Employee
VMware Employee
Jump to solution

Might be this issue see here -> http://communities.vmware.com/thread/162377?tstart=0

mattjk
Enthusiast
Enthusiast
Jump to solution

Quite possibly your problem / related: http://communities.vmware.com/thread/162377

Cheers, Matt
Reply
0 Kudos
krival96
Contributor
Contributor
Jump to solution

http://www.vdi.co.nz/?p=18

same issue with us

kris http://www.vdi.co.nz
Reply
0 Kudos
ufo8mydog
Enthusiast
Enthusiast
Jump to solution

Hi there,

That was exactly the problem, thanks for that. As soon as i changed the time back to Aug 10 and turned off NTP everything turned back to normal.

I can imagine that a lot of people would be affected by this bug!

Reply
0 Kudos
c1nt4x3rr0r
Contributor
Contributor
Jump to solution

I too am having this error, and it started this morning. I have 5 ESXi hosts, all licensed, all exhibiting the same behavior. If I set the time back (a few days) on the host using the VIC, I am then able to start up my clients.

I called Support, but since I didn't have a valid contract I was shot down.

This is a great product, but if VMware won't help me with something that's obviously broken without charging me $1200, then I'll probably have to switch to Hyper-V. I've already got all the licensing and support for it...

Reply
0 Kudos
Gonecase
Contributor
Contributor
Jump to solution

This is some bug in ESX 3.5 U 2. The workaround for the moment is to stop NTP service and change the date of the system to anything before 12th Aug. And wait for the patch/fix from VMware

Reply
0 Kudos
Rumple
Virtuoso
Virtuoso
Jump to solution

They have obviously coded the date function incorrectly (probably like a CDN region) where the first number is day, second is month and so as soon as the 13th month rolls around it pukes...

I usually see it with american software when someone decides that they should run their computer with the Canadian region and half their apps fall down and go boom...

Reply
0 Kudos