What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Bot crashes at start up.

lazaro666

New Member
Joined
Aug 21, 2012
Messages
126
Reaction score
1
It's a short log so here it is,
[15:44:29.223 N] Honorbuddy v2.5.6647.521 started.
[15:44:29.241 N] Logging in...
[15:44:30.499 D] Attached To : D3D11
[15:44:30.761 N] Attached to WoW with ID 6104
[15:44:43.491 D] System.TypeInitializationException: The type initializer for 'Styx.Helpers.LevelbotSettings' threw an exception. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at Styx.Helpers.Settings..ctor(String settingsPath)
at Styx.Helpers.LevelbotSettings..ctor()
at Styx.Helpers.LevelbotSettings..cctor()
--- End of inner exception stack trace ---
at Honorbuddy.MainWindow.LoadSettings()
at Honorbuddy.MainWindow.HandleSuccess()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) --> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at Styx.Helpers.Settings..ctor(String settingsPath)
at Styx.Helpers.LevelbotSettings..ctor()
at Styx.Helpers.LevelbotSettings..cctor()
[15:44:43.491 D] System.TypeInitializationException: The type initializer for 'Styx.Helpers.LevelbotSettings' threw an exception. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at Styx.Helpers.Settings..ctor(String settingsPath)
at Styx.Helpers.LevelbotSettings..ctor()
at Styx.Helpers.LevelbotSettings..cctor()
--- End of inner exception stack trace ---
at Honorbuddy.MainWindow.LoadSettings()
at Honorbuddy.MainWindow.HandleSuccess()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) --> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at Styx.Helpers.Settings..ctor(String settingsPath)
at Styx.Helpers.LevelbotSettings..ctor()
at Styx.Helpers.LevelbotSettings..cctor()

That's all its showing.

My set up is good and dandy since I have other toons running on the same key perfectly fine. Only occurring when trying to start quest bot on this toon.
 
Deleting LevelBot.Settings in the Settings folder under the specific toon name fixes the issue.
 
Apparently most of the Styx exceptions calling a 0x00 error cannot divide by 0 can be fixed by deleting that specific file and letting it regenerate a new one
 
Apparently most of the Styx exceptions calling a 0x00 error cannot divide by 0 can be fixed by deleting that specific file and letting it regenerate a new one

Hi, Lazaro666,

That solution is called a "band aid". The correct thing to do is figure out why the Bot was shut down ungracefully to begin with, and fix that problem. The ungraceful shutdown is what cause the file to become corrupt in the first place.

cheers,
chinajade
 
Hi, Lazaro666,


That solution is called a "band aid". The correct thing to do is figure out why the Bot was shut down ungracefully to begin with, and fix that problem. The ungraceful shutdown is what cause the file to become corrupt in the first place.

cheers,
chinajade

Hi Chinajade
Arelog shuts the bot down ungracefully often, causing the server to be unable to log back in due to the key still being logged in. It also causes plenty of corruptions within the quest and wow caches, but to be honest the benefits outweights the problems. However the occurrence was due to a power outage.
 
Back
Top