cancel
Showing results for 
Search instead for 
Did you mean: 

Help - A general system error occurred: Protocol error from VMX.

Lesta_G
Level 6

This is a good one!

Running BE2010 R3 all hotfixes (according to live update)

Vcenter 4.1.0 258902

ESXi 4.1.0 502767

 

VMs

2003 SP2 32 bit

2003 R2 SP2 64 Bit

VM Tools 8.3.12

 

In the BE log get the "usual error"

"The job failed with the following error: Unable to create a snapshot of the virtual machine. The virtual machine may be too busy to quiesce to take the snapshot"

In the VMWare log - "A general system error occurred: Protocol error from VMX."

Yet the machines that gets the error in the log can snapshot with quiesce in VCenter fine.

 

For some reason , when the backups run on these two machines (many more on the host ), their times move ahead 8 hours and the backup fails

If I re-run they backup job immediately, the time is still 8 hours ahead so the backup works.

If I retry after the time has been reset, the job will fail again

The time stays forward for the duration of the backup job.

I am not sure if the time is reset at the end of the job or that a standard windows time sync resets it

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Lesta_G
Level 6

The answer was that the hosts time was 8 hours ahead. Resetting the ESX host to the correct time solved the problem.

As to why it did not effect all the VMS on the host , i have no idea

View solution in original post

1 REPLY 1

Lesta_G
Level 6

The answer was that the hosts time was 8 hours ahead. Resetting the ESX host to the correct time solved the problem.

As to why it did not effect all the VMS on the host , i have no idea