• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Stuck at "Logging in..."

    Discussion in 'Honorbuddy Support' started by qztr, Sep 2, 2016.

    1. qztr

      qztr Active Member

      Joined:
      Mar 31, 2012
      Messages:
      1,932
      Likes Received:
      17
      Trophy Points:
      38
      Got 5 bots running perfectly fine, all using the same settings and such.

      Tried a fresh install, got the same error.

      Code:
      [16:40:42.005 N] Honorbuddy v3.0.15990.847 started.
      [16:40:42.194 D] Reloading AssemblyLoader<BotBase> - Initializing bots
      [16:40:42.194 D] Reloading AssemblyLoader<HBPlugin> - Initializing plugins
      [16:40:42.194 D] Reloading AssemblyLoader<CombatRoutine> - Initializing routines
      [16:40:45.872 N] Logging in...
      [16:40:46.060 D] T: 5247770330886126438 H: 2154177962
      [16:40:46.061 D] Logged in to the Europe region (37.187.151.148)
      [16:40:47.628 D] System.ComponentModel.Win32Exception (0x80004005): Only part of a ReadProcessMemory or WriteProcessMemory request was completed
         at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
         at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
         at System.Diagnostics.Process.get_MainModule()
         at GreyMagic.MemoryBase.get_ImageBase()
         at GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
         at Honorbuddy.MainWindow.kfm mVZ\*:JV\,;79x8$G/q05V'.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Honorbuddy.MainWindow.79I\]9JYu#jv_ZgfPO|%_="uF!.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Honorbuddy.MainWindow.|\[i?Y3v's\,A'"IT?=^=8i'4D!.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
         at Honorbuddy.MainWindow.vN''=yha"9!3EhF)5eS$aW(@$.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Honorbuddy.MainWindow.Ppp\[L\.-O8s/\*|hq)L07\,\,/j"".MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
         at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
         at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
      
      Any help is appreciated.
       
    2. evialtah

      evialtah New Member

      Joined:
      Dec 16, 2011
      Messages:
      322
      Likes Received:
      1
      Trophy Points:
      0
      Same me.
       
    3. Tevious

      Tevious New Member

      Joined:
      Sep 21, 2011
      Messages:
      2
      Likes Received:
      0
      Trophy Points:
      0
      same same
       
    4. Tevious

      Tevious New Member

      Joined:
      Sep 21, 2011
      Messages:
      2
      Likes Received:
      0
      Trophy Points:
      0
      ok so I got it working on one toon at least. The problem was a remaining wow.exe process. Check in tast manager for a wow process that takes up 0.1mb of ram
       
    5. qztr

      qztr Active Member

      Joined:
      Mar 31, 2012
      Messages:
      1,932
      Likes Received:
      17
      Trophy Points:
      38
      [​IMG]

      Killed the task and it's now working, thanks :)
       

    Share This Page