XmlException: Document element did not appear. Line 2, position 1.
Mono.Xml2.XmlTextReader.Read ()
System.Xml.XmlTextReader.Read ()
System.Xml.XmlReader.MoveToContent ()
System.Xml.Serialization.XmlSerializationReaderInterpreter.ReadRoot ()
System.Xml.Serialization.XmlSerializer.Deserialize (System.Xml.Serialization.XmlSerializationReader reader)
Iâm on windows 8 just fired up Unity this morning and bam! Seems to only effect our main project so far, all other projects are fine⌠canât seem to isolate the issue yet though.
I have the same problem since today. I have a dozen different project backups all the way back to early June, and every single one is suddenly throwing this error non-stop when I launch the editor. It doesnât just throw the error once, it throws it thousands of times and doesnât stop.
Win 7 64bit + Unity 5.1.1f1
Edit:
Alright, this is spooky, I just opened the editor for the 50th time today, and I now get a different error (also thousands of times):
InvalidOperationException: Received a error response from the server:
<b>Parse error</b>: syntax error, unexpected 'version' (T_STRING) in <b>/home/unityn7/public_html/unity/asset_store/message_builder.php</b> on line <b>129</b>
FxProNS.ServerGateway.ProcessServerReply (UnityEngine.WWW www, System.Object args) (at Assets/WaterPlus/Scripts/editor/InfoMessage.cs:106)
FxProNS.ServerGateway+<StartWWWRequest>c__AnonStorey1.<>m__3 () (at Assets/WaterPlus/Scripts/editor/InfoMessage.cs:99)
FxProNS.ContinuationManager.Update () (at Assets/WaterPlus/Scripts/editor/InfoMessage.cs:393)
UnityEditor.EditorApplication.Internal_CallUpdateFunctions () (at C:/buildslave/unity/build/artifacts/generated/common/editor/EditorApplicationBindings.gen.cs:264)
Same prob on OSX. I was logged out. Signed in and the original xml error went away. Then I got the server response error. We happen to be using Water+ also. Maybe their server is down. Is everyone using that? It does do some deserializing etc. but the original error pointed at monodoc.xml. Not sure if theyâre related. I just commented out the calls from Update in InfoMessage.cs (there are two Updates in there). No more console spamming.
I fixed my issue. I am not sure if others have the same problem or not.
To start I have upgraded to Windows 10, Visual Studio 2015, and UnityVS 2.0 so I was expecting some issues.
I figured out that my error was caused because I was coping the â.mdbâ file for my library dlls into the plugins folder in unity along side the â.dllâ and â.pdpâ files. The â.mdbâ file appears to no longer be needed by UnityVS, and in fact seemed to be causing the error. I fixed my â.batâ file to no longer copy the â.mdbâ files, and I also deleted the â.mdbâ files from the plugins folder.
That fixed it for me. I hope this helps someone else.
Hmmm, I also am using water+ and had a different error after removing the â.mdbâ files that related to it. I also removed water+ to resolve that other error. I would be interested in what others find.
Iâm still not sure if the errors were related but itâs one thing in common.
Water+ is calling unityninjas.com to check for updates. Those calls are made from InfoMessage.cs. They either changed their php script or somethingâs up with their server. Results in the bad response error which is a Debug line in InfoMessage.cs. Commenting out the update calls prevents the calls into the server. So, of course, you donât get a bad response. It wonât check for updates though. If you want it to, youâll have to uncomment later and try again.