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

Authentication failed.

H

Hacked1111

New Member
Joined
Dec 5, 2011
Messages
105
Reaction score
0
I've been using HB for a while now, and am very satisfied.
I bought a lifetime supscription btw.

But today i cant log in. It says authentication failed.
I've tried relogging wow, HB, my comp and I even re-installed HB.

Please help.
 
Same Prob here, updatet HB and now this pops up:


[15:11:11:980] Logging in...
[15:11:12:245]
[15:11:12:869] Error attaching Honorbuddy to WoW! - System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei Styx.WoWInternals.ObjectManager.Initialize(Memory blackmagic)
bei Honorbuddy.MainWindow.#TUc()
[15:11:12:869] -------------------------------
[15:11:12:869] You have not selected a valid instance of WoW to attach to!
[15:11:12:869] Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
[15:11:12:869] This version of Honorbuddy only supports WoW Build #15354
[15:11:12:870] You are currently on build #15354
[15:11:12:870] -------------------------------
[15:11:15:162] Honorbuddy is up-to-date
 
Solnaciente said:
Same Prob here, updatet HB and now this pops up:


[15:11:11:980] Logging in...
[15:11:12:245]
[15:11:12:869] Error attaching Honorbuddy to WoW! - System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei Styx.WoWInternals.ObjectManager.Initialize(Memory blackmagic)
bei Honorbuddy.MainWindow.#TUc()
[15:11:12:869] -------------------------------
[15:11:12:869] You have not selected a valid instance of WoW to attach to!
[15:11:12:869] Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
[15:11:12:869] This version of Honorbuddy only supports WoW Build #15354
[15:11:12:870] You are currently on build #15354
[15:11:12:870] -------------------------------
[15:11:15:162] Honorbuddy is up-to-date
Click to expand...

make sure your wow is in windowed mode,32bit and dx9

also you can try to run is as admin as well
 
OK downloaded "the old version" again and it works fine... Dunno smth is wrong with that update i made 20 mins ago.
 
Solnaciente said:
OK downloaded "the old version" again and it works fine... Dunno smth is wrong with that update i made 20 mins ago.
Click to expand...

you did an update of your old existing installation or a fresh clean installation?
 
I updatet the version i was using all the time, after that the bot f.. up. So i downloaded the Version here at the Dl section unzipped it and now it works with that version.

Not updatet or anything yet. Just a fresh Dl , unzip and go.
 
Ok, now it's messing up again.
I relogged HB and got the authentication failed message again.


[14:41:19:075] Logging in...
[14:41:19:344]
Max Sessions
[14:41:19:384] Authentication failed!
[14:41:22:912] Logging in...
[14:41:23:079]
Max Sessions
[14:41:23:097] Authentication failed!
 
Thanks for the reply, but what does "kill my sessions" mean?
Doesnt sound like something i wanna do, but im guessing it has something to do with me buying a lifetime sub?
 
I get the same error. I had been running AV and noticed that the bot log said there was an update.
When I left the BG, I paused my relogger, closed the bot and ran the Updater.exe
Read through the change log, clicked update (though now I think I will begin backing up previous versions)
Started the relogger again and .... drum roll

Logging in...

Error attaching Honorbuddy to WoW! - System.NullReferenceException: Object reference not set to an instance of an object.
at Styx.WoWInternals.ObjectManager.Initialize(Memory blackmagic)
at Honorbuddy.MainWindow.#TUc()
-------------------------------
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #15354
You are currently on build #15354
-------------------------------
Click to expand...

I am running OS Windows XP 32b, there is no need to "log in as administrator"
I am using DX9, not 11
The previous version, as stated above, and obviously as it was just running moments ago, worked

fluke with update?
subnote: the auth portal "sessions" just kills your existing session with the auth server, but this isn't an auth issue, its not detecting the wow client even though it outputs the required version, and the existing version (matching).

Reverted to build 2.0.0.580 (I do keep archives) patiently awaiting a reply/fix.

Thank you



mello
 
Last edited:
Hacked1111 said:
Thanks for the reply, but what does "kill my sessions" mean?
Doesnt sound like something i wanna do, but im guessing it has something to do with me buying a lifetime sub?
Click to expand...


Do u use 1 day Keys!? I think even with that it can be done. Not sure but should work. To "kill a session" is a manual reset for the bot. Its like "ok bot ure done now, im logged out"...
 
Im afraid I dont know what one day keys are.
I really just bought the program, downloaded it and started botting.

But i guess ill try killing my account on that page.
Thanks.
 
I get this error when i try to log on to kill stuff:

Server Error in '/' Application.

Data is Null. This method or property cannot be called on Null values.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
 
There is obviously a problem with this new update. I am running everything "as needed" or whatever, and it did just work moments ago until i updated the bot.
 
Hacked1111 said:
Im afraid I dont know what one day keys are.
I really just bought the program, downloaded it and started botting.

But i guess ill try killing my account on that page.
Thanks.
Click to expand...

The reason you are that you have the "lifetime sub" because they merged it, and it now costs 25 euros one time fee. Unfortunately they havent' had time to update all pages since theyre working on new releases etc. :)
 
mellome said:
I get the same error. I had been running AV and noticed that the bot log said there was an update.
When I left the BG, I paused my relogger, closed the bot and ran the Updater.exe
Read through the change log, clicked update (though now I think I will begin backing up previous versions)
Started the relogger again and .... drum roll



I am running OS Windows XP 32b, there is no need to "log in as administrator"
I am using DX9, not 11
The previous version, as stated above, and obviously as it was just running moments ago, worked

fluke with update?
subnote: the auth portal "sessions" just kills your existing session with the auth server, but this isn't an auth issue, its not detecting the wow client even though it outputs the required version, and the existing version (matching).

Reverted to build 2.0.0.580 (I do keep archives) patiently awaiting a reply/fix.

Thank you



mello
Click to expand...

tried and fresh and clean installation?
 
Hacked1111 said:
I get this error when i try to log on to kill stuff:

Server Error in '/' Application.

Data is Null. This method or property cannot be called on Null values.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Click to expand...

make sure you are using the correct login info
 
You must log in or register to reply here.
Back
Top