Protocol Error In Vmx
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphereโข > VMware ESXi 4 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 2 Replies Latest reply: Jun 17, 2012 7:28 PM by Lesta A general system error occurred: Protocol error from VMX Lesta May 3, 2012 7:19 PM Really just posting this for someone else who gets this weird errorThis is a good one!Running Symantec BE2010 R3 all hotfixes (according to live update)Vcenter 4.1.0 258902ESXi 4.1.0 502767VMs2003 SP2 32 bit2003 R2 SP2 64 BitVM Tools 8.3.12In the BE log get the "usual error""The job failed with the following https://kb.vmware.com/kb/1007346 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 https://communities.vmware.com/thread/400746?tstart=0 more on the host ), their times move ahead 8 hours and the backup failsIf 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 againThe 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.The resolution was to check the Host. Its time was set 8 hours ahead.EVEN THO the VM Tools client was set NOT to update time from hostA snapshot in vCenter with Quisce, worked fine. It was only when thet backup was run that the error occurredStange but true catergory 1792Views Tags: none (add) vmxContent tagged with vmx, quiesceContent tagged with quiesce This content has been marked as final. Show 2 replies 1. Re: A general system error occurred: Protocol error from VMX Rubeck Jun 13, 2012 12:00 AM (in response to Lesta) Hi..I know this thread is a few days old, but here goes:You say you can snapshot with quiesce just fine
me and DiscoPosseEventsMedia and PrintOther GoodiesMusic and MediaFitness and FoodPodcast × 05 Sep 2010Cloud, Virtualization and ArchitectureVMware tip - Protocol error from VMX By DiscoPosse / 7 Comments Small tip, big victory. I have weekly snapshots and clones that are scheduled through vCenter. Suddenly one of the clone tasks stopped http://discoposse.com/2010/09/05/vmware-tip-protocol-error-from-vmx/ working and threw this error:A General System error occurred: Protocol error from VMX.Hmmm…that's odd. It's run fine up to now right? Luckily the fix couldn't be too much simpler than this.SOLUTION: Restart the VMware https://arcserve.zendesk.com/hc/en-us/articles/202153069-AE0577-AE0580-A-general-system-error-occurred-Protocol-error-from-VMX Tools service in the guest machine and restart the tasket voila!Share this:Click to share on Twitter (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Google+ (Opens in protocol error new window)Related Tags: error, esx, tip, vmware, vsphere DiscoPossePeople, Process, and Technology. Powered by Community! You might also like AWS Route53 Step-by-Step - Redirecting Domains GUI VMworld 2016 - Quick Takes on the Event and Announcements Part 2 of 2 TechForward.io - Crash Course in Mesosphere DC/OS VMworld Presentation7 Comments khuiwongDecember 13, 2012 at 1:19 pmThanks so much! This works for me. I have this error while using VEEAM protocol error in to backup a vm. Reply Waleed QassemMay 6, 2013 at 5:54 amI had a similar problem, and I have searched the internet for a solution, but couldn't find a proper solution, it kept failing, until I came a cross this tip, tested it and it worked like a charm. Thanks alot, this was really helpfull Reply EricMay 6, 2013 at 8:48 amThat's great to hear! I'm glad that it helped out ๐ Reply AsimOctober 29, 2013 at 3:21 amAwesome, Thank u so much ๐ Its works for me also.i was unable to do cloning. ๐ Reply EricOctober 29, 2013 at 4:50 amThat's great to hear! Reply RichardMay 14, 2015 at 5:07 pmExcelente… me tomo semanas encontrar una solucion hasta que llegue aca… me funciona de maravillas..Muchas Gracias. Reply ShababJuly 14, 2015 at 10:05 amYou really saved my day.. thanks a lot for your tip. it worked like miracle for me.. Excellent.. ReplyLEAVE A COMMENT Cancel replySign me up for the newsletter! Notify me of follow-up comments by email. Notify me of new posts by email. Proudly Sponsored By GC On-DemandSubscribe to the BlogEnter your email address to subscribe to this blog and receive notifications of new posts by email. Email Address Upcoming events:Tue04Oct2016Wisconsin VMUGThu06Oct2016Atlant
Phone: Company:* Customer Type: Select Customer TypeEnd CustomerTrial CustomerResellerDistributerMSP Arcserve Employee Language: EnglishFrenchGermanItalianJapanesePolishPortugueseSpanishTurkish Country: Region: North AmericaJapanAsia PacificEMEA (Europe MiddleEast Africa)Latin America Time zone: Select Time Zone GMT-11:00 :: American Samoa GMT-11:00 :: International Date Line West GMT-11:00 :: Midway Island GMT-10:00 :: Hawaii GMT-09:00 :: Alaska GMT-08:00 :: Pacific Time (US & Canada) GMT-08:00 :: Tijuana GMT-07:00 :: Arizona GMT-07:00 :: Chihuahua GMT-07:00 :: Mazatlan GMT-07:00 :: Mountain Time (US & Canada) GMT-06:00 :: Central America GMT-06:00 :: Central Time (US & Canada) GMT-06:00 :: Guadalajara GMT-06:00 :: Mexico City GMT-06:00 :: Monterrey GMT-06:00 :: Saskatchewan GMT-05:00 :: Bogota GMT-05:00 :: Eastern Time (US & Canada) GMT-05:00 :: Indiana (East) GMT-05:00 :: Lima GMT-05:00 :: Quito GMT-04:30 :: Caracas GMT-04:00 :: Atlantic Time (Canada) GMT-04:00 :: Georgetown GMT-04:00 :: La Paz GMT-04:00 :: Puerto Rico GMT-03:30 :: Newfoundland GMT-03:00 :: Buenos Aires GMT-03:00 :: Greenland GMT-03:00 :: Santiago GMT-02:00 :: Brasilia GMT-02:00 :: Mid-Atlantic GMT-01:00 :: Azores GMT-01:00 :: Cape Verde Is. GMT+00:00 :: Casablanca GMT+00:00 :: Dublin GMT+00:00 :: Edinburgh GMT+00:00 :: Lisbon GMT+00:00 :: London GMT+00:00 :: Monrovia GMT+00:00 :: UTC GMT+01:00 :: Amsterdam GMT+01:00 :: Belgrade GMT+01:00 :: Berlin GMT+01:00 :: Bern GMT+01:00 :: Bratislava GMT+01:00 :: Brussels GMT+01:00 :: Budapest GMT+01:00 :: Copenhagen GMT+01:00 :: Ljubljana GMT+01:00 :: Madrid GMT+01:00 :: Oslo GMT+01:00 :: Paris GMT+01:00 :: Prague GMT+01:00 :: Rome GMT+01:00 :: Sarajevo GMT+01:00 :: Skopje GMT+01:00 :: Stockholm GMT+01:00 :: Vienna GMT+01:00 :: Warsaw GMT+01:00 :: West Central Africa GMT+01:00 :: Zagreb GMT+02:00 :: Athens GMT+02:00 :: Bucharest GMT+02:00 :: Cairo GMT+02:00 :: Harare GMT+02:00 :: Helsinki GMT+02:00 :: Istanbul GMT+02:00 :: Jerusalem GMT+02:00 :: Kyev GMT+02:00 :: Kyiv GMT+02:00 :: Pretoria GMT+02:00 :: Riga GMT+02:00 :: Sofia GMT+02:00 :: Tallinn GMT+02:00 :: Vilnius GMT+03:00 :: Baghdad GMT+03:00 :: Kuwait GMT+03:00 :: Minsk GMT+03:00 :: Moscow GMT+03:00 :: Nairobi GMT+03:00 :: Riyadh GMT+03:00 :: St. Petersburg GMT+03:00 :: Volgograd GMT+03:30 :: Tehran GMT+04:00 :: Abu Dhabi GMT+04:00 :: Baku GMT+04:00 :: Muscat GMT+04:00 :: Tbilisi GMT+04:00 :: Yerevan GMT+04:30 :: Kabul GMT+05:00 :: Ekaterinburg GMT+05:00 :: Islamabad GMT+05:00 :: Karachi GMT+05:00 :: Tashkent GMT+05:30 :: Chennai GMT+05:30 :: Kolkata GMT+05:30 :: Mumbai GMT+05:30 :: New Delhi GMT+05:30 :: Sri Jayawardenepura GMT+05:45 :: Kathmandu GMT+06:00 ::