• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Honorbuddy stuck on login

    Discussion in 'Honorbuddy Support' started by dougy109, Jul 3, 2014.

    1. dougy109

      dougy109 New Member

      Joined:
      Jul 3, 2014
      Messages:
      3
      Likes Received:
      0
      Trophy Points:
      0
      Hey
      When loading Honorbuddy the bot will got get past the stage of logging in.

      The text looks like this:

      Honorbuddy v2.5.11034.745 started.
      Logging in...
      T: 5247086301173895930 H: 1931720292

      I have tried reinstalling and im not sure how else to fix this.
       
    2. dougy109

      dougy109 New Member

      Joined:
      Jul 3, 2014
      Messages:
      3
      Likes Received:
      0
      Trophy Points:
      0
      Log File here:

      [23:55:11.774 N] Honorbuddy v2.5.11034.745 started.
      [23:55:13.615 N] Logging in...
      [23:55:14.307 N] T: 5247086303564422660 H: 3067246408
      [23:55:15.281 D] System.IO.FileLoadException: Could not load file or assembly 'RemoteASM, Version=2.5.11034.745, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
      File name: 'RemoteASM, Version=2.5.11034.745, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda'
      at GreyMagic.ExternalProcessMemory.Init(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
      at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm)
      at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits)
      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)

      WRN: Assembly binding logging is turned OFF.
      To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
      Note: There is some performance penalty associated with assembly bind failure logging.
      To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
       
    3. CodenameG

      CodenameG New Member

      Joined:
      Jan 15, 2010
      Messages:
      38,369
      Likes Received:
      231
      Trophy Points:
      0

    Share This Page