Can't login for 3 days - stuck on 'Logging in'

stuck on 'Logging in' - edit: SOLVED

Solved.

Always using Tyrael bot while raiding and it stopped in the raid 3 days ago.
Tried to restart but since then its stuck on:

'Honorbuddy v2.5.10675.735 started.
Logging in...
T: 5247053093722018482 H: 265080285'

Test on old versions, new clean installation - didn't work. Won't log me in.

Also I get this error msg when I start HB for a week now - http://i.imgur.com/kM6kitJ.png
(it worked even after the message. but not anymore)



Log:

Code:

[13:18:18.211 N] Honorbuddy v2.5.10675.735 started.
[13:18:19.624 N] Honorbuddy was unable to check for or apply update.
System.ArgumentException: Version string portion was too short or too long.
   at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at System.Version..ctor(String version)
   at Honorbuddy.MainWindow.CheckForUpdate()
[13:18:21.008 N] Logging in...
[13:18:22.499 N] T: 5247053089439489066 H: 172282504
[13:18:23.388 D] System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.ArrayList.get_Item(Int32 index)
   at System.Diagnostics.ProcessThreadCollection.get_Item(Int32 index)
   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)

Log 2:

Code:

[13:25:27.437 N] Honorbuddy v2.5.10675.735 started.
[13:25:29.384 N] Logging in...
[13:25:29.615 N] T: 5247053093722018482 H: 265080285
[13:25:30.312 D] System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.ArrayList.get_Item(Int32 index)
   at System.Diagnostics.ProcessThreadCollection.get_Item(Int32 index)
   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)

They all look like this.

Using Windows 8.1 - 64bit [bot worked for months without problems]


Someone has a solution for this?

 

MissFoxilein I had this same error the other day. What I did to fix it was to go into the BNet App and unclick and reclicked run WoW in 32 bit mode and that fixed it. Maybe you've done that already but thought I'd throw in what I had to do to get around that.

 

I've just done that but it didn't change anything.

Mostly starting HB before opening WoW anyway

 

If I'm not mistaken you need to start WoW then Honorbuddy else it wont find what it is supposed to be attaching to. But if it's not working either way I'd double check you have the .Net 4.5 Framework installed but other than that I don't think I can be of much more assistance. And I just viewed the picture you attached and it looks like it is failing to reach an update server. Try disabling your firewall (temporarily) so put it in say shields off 5 minutes or somthing to that effect and see if it then can communicate.

 

Don't have any firewall.
It worked before, even with that popup message. A lot of people have that problem according to the forums here.

 

I just read another post where it confirms what you we're saying it appears that the error message doesn't affect the bot from operating. Hmmm. I guess wait until a dev gets around to the post I just went through what I do most times to get it working. (been here for 4 years I've seem some strange things) But this seems to fall out of my realm of help. Sorry I hope they get a response for you soon. =]

 

Argh.

Problem solved.

Just downloaded windows updates (there was a 4.5.1 .Net security update on 13th may included which probably fixed it).

Thankies

 

Oh good old Windows Updates. Got to love them. I'm happy to hear that fixed the issue.