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.
Anyone?
abugeja so far that's the easiest way to fix this issue man.
So why not upgrading to VCenter v5.5U3d ?
vSphere 5.1 will be out of support soon this year.
We are upgrading to 6.0 Update 2 but this wont be for a few months. Until then we need a fix and upgrading to 5.5 U3d is not one of them.
Hi all,
I have too this error after a patching this weekend. i think that the root cause is a KB yes....
Have a nice day
Upgrading just the vSphere client to 5.5U3D fixes the issue. You can leave your actual vCenter at 5.0 or 5.1
I'm still relatively new to vcenter, so I think i'm must be missing something obvious.
How do you get just the vSphere client to 5.5U3D?
I've looked all over and don't see any download links...
TIA
Trying to use a newer vSphere client on a legacy version VC doesn't work as the client will always try to use the connect using the correct version.
I.e trying to connect to a VC 5.1 using a vSphere 5.5 client will have the vSphere 5.5 client try to download and install the vSphere 5.1 client instead (if not already present).
And if I might add, on Windows 2012R2 it is the KB3142026 that needs to be uninstall (same KB, same purpose than on Windows 2008R2, just different number).
I was able to resolve this issue by running a repair on the Visual J# installation, the download can be found below. Hope this helps.
Thanks upgrade the vSphere client to latest version fixed this issue
for me 5.5 wasn't an option, J# didn't do the trick and I couldn't find the mentioned KB
What I did find was MS16-065 ( https://support.microsoft.com/nl-nl/kb/3155464 )
To be more precise the registry settings from ManualOptOutSchSendAuxRecord20.reg did the trick for me
Thank you for the information.
What is the version of the vSphere client that solved trhe issue?
marius
I realize this is a bit old but for those whom are still struggling with this, below is the short answer (English).
Do this: Workaround
To temporarily disable the secure mode described in this article, click the appropriate link to download a .reg file, and then double-click the downloaded .reg file to make the registry changes.
For applications targeting the Microsoft .NET Framework 3.5:
Download the ManualOptOutSchSendAuxRecord20.reg file now.
Details:
--Jody