just bought a trial code. the client hangs on 'logging in', then HB crashes.

the HB client version i'm using is 2.5.10121.730

if i remember correctly, it was doing this the last time i bought a trial code. i'd like to be able to get some use out of my purchase, please.

edit: should also mention, i've tried running the client as an administrator. i'm sure that i'm running 32-bit WoW and DX9 is enabled. i've tried turning on compatibility mode and running it with windows XP sp3 compatibility. no dice. the client displays "logging in" for about 4 or 5 minutes, then the crash window pops up. i've sent a report through this function.

edit2: and here's the crash log:

 

the log file is now attached

 

make sure your not running any applications that can interfere with wow and honorbuddy.
http://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-guides/108771-help-desk.html#post1292171

 

i'm not running any of those applications that cause interference. in windows firewall i chose to allow Honorbuddy to connect, and i opened the outgoing ports 5001 and 5031. now i get the crash report almost immediately upon singing in.

attached is most recent crash log.

 

We couldn't find a free WoW process to attach. Please make certain your toon is standing in game world and you are running latest version of Honorbuddy.


are you logged in and fully in game before starting honorbuddy?

 

yes, I've tried it on multiple toons as well
i may have mistakenly attached a log from where i wasn't in the game but I've tried multiple times to sign into HB while logged in and in the game world. it never successfully logs in. and i'm using the latest version i believe. the version # is in my original post.

 

then clear your log folder, reproduce the issue and upload the correct log.

 

here it is. looks exactly the same as the first log i posted.

 

yes, both WoW (32 bit) and HB are being run as administrators. HB was not moved from it's download/zip folder, and i'm not using shortcuts or launchers to launch either application.

my account on my pc is an administrator account.

here's another more recent crash log.

 

no. maybe? i downloaded the zip file, and extracted all it's contents into a folder (named the same thing as the zip file is titled). in the folder i run Honorbuddy.
i'm not running the app from a zip archive.

 

you should be doing it like this.
https://www.youtube.com/watch?v=DOoUsfeyYsw

 

that's more or less how i'm doing it. the only way the video differs from how I did it, is that the guy extracts the HB zip into a folder that's on the desktop as opposed to "my downloads" which is where mine is.

i'm going to reinstall WoW and let the game re-download while i'm at work and see if it works later today. i'll be sure to attach a log if it gives me trouble.

 

yea, that guy is me.

well let us know.

 

this is bizarre. the game re-installed just fine, and again i made sure to launch the 32-bit client (as administrator) from the WoW folder in Program Files. and Honorbuddy is also launched as administrator, and not until i'm logged in and my character is in the game world. the error log isn't giving any more details other than "logging in...". it crashes much quicker now, and the error/crash pop-up window says "access is denied".

are there any Windows services that are required by Honorbuddy that i might have disabled? i don't mess around in the services settings very much but maybe something got turned off, something that it needs to communicate online or maybe find a resource located in Windows?

this is so frustrating but i'm glad the staff is helping me figure it out, i appreciate that

attached is the crash log

 

well, i can do that, but i made some changes to my registry and services recently. a few other issues i was having with my PC, are now resolved. and upon logging in to HB, it doesn't crash anymore - but it does tell me that my key expired. do i have to buy another one or can you guys issue me another 3 day trial pass? i don't want to buy more time unless i know it's going to run on my PC.

edit: i suspect (but don't know how to prove) that what fixed this issue came from fixing an error with Microsoft's .NET Framework registry values. there were either duplicates or corrupt entries in my registry which were removed, so alot of services that relied upon it (HB being one of them) are now working properly.