Hi All,
I'm using Windows C# client as below version:
Somehow I got random / intermittent error popped up:
Error:Unexpected character '' (code 65279 / 0xfeff) in prolog; expected '<' at [row,col {unknown-source}]: [1,1]
So I wonder if that's recent issue with the Windows 10 .NET framework update ?
My other C# client same version on Windows Server 2008 R2 is not having the issue.
FYI,
No need to upgrade to vSphere 6.0 yet. I have upgraded the vSphere client as part of the VCenter server upgrade project into 5.5U3d last week, so far it is resolving the problem:
See the above screenshot for the stable version.
I'm happy (ish?) to hear that I'm not alone. Myself and 3 other colleagues have experienced the same issue and haven't found a resolution as of yet. What version of .NET are you running? We're at 4.6.01038.
I have been seeing the same exact issue since mid April and it's becoming more and more annoying. My other colleague just started seeing the pop-up message a couple of days ago. Will try to see what updates have been applied that might have caused it. I am using a vSphere Client v5.5 on Windows 10.
jordanrecknagel
AlmazIsakov
I'm on Windows 10 with the latest .NET Fx 4.6.2 using all vSphere 5.1 clients and vCenter.
I guess this is must be the problem that comes with .NET Fx
Hi,
Got the same error, Windows 10 with vSphere Client v5.1.0 Build 1235233
Hello,
You can setup .net 3.5 and J#
http://blog.pragbits.com/it/2015/09/07/vsphere-client-install-windows10/
Thanks you,
Regards,
Same error here. Windows 10 - vSphere Client 5.5.0 Build 1618071. No random popups on Win 7 with same vSphere client. Started happening after a recent windows .NET update.
Thanks for the updates everyone! I have uninstalled the latest Cumulative security patch dated April 12, 2016 — KB3147458 (OS Build 10586.218) and the issue has been resolved.
Not sure if VMware is going to do something about it. All we know is that they are actively working on to get everyone off the thick client.
But if you uninstall the https://support.microsoft.com/en-us/kb/3147458 you'll be prone to the security vulnerabilities ?
So after uninstalling the patch above, what is your Windows 10 version now ?
Yes, same vSphere client but no problem on Windows Server 2008 R2.
ditto...this is happening to me too.
for what it's worth. i'm running two versions of ESXi. This issue occurs on version 5.0 on my client. but, does not seem to occur on version 6.0. I am not running 5.1 as you guys are.
Same here, did not see that error with vSphere Client 6.
Uninstalling KB3147458 worked for me!
I am seeing this on a Windows 7 SP1 PC accessing a 5.1 vSphere client.
vSphere client version 5.1.0 build 1880906
vCenter Server version 5.1.0 build 947673
FYI,
No need to upgrade to vSphere 6.0 yet. I have upgraded the vSphere client as part of the VCenter server upgrade project into 5.5U3d last week, so far it is resolving the problem:
See the above screenshot for the stable version.
Updating to 5.5 is not an option for me at the current time.
In win 2008R2 uninstall KB3142024. It worked for me.
Ciao
I was just coming back on here to say that I uninstalled that same update (KB3142024) on my Windows 7 PC and the client seems to be behaving better.
Is anyone aware of other options for the 5.1 client other than removing the Microsoft patch or upgrading to a later version of vcenter?