"Bot stopped! Reason: Could not create current in quest bot!"

So I've been using the quest bot for the entirety of leveling this toon, from nil to 83 now. Just got into Uldum last night. I ran into this problem earlier this afternoon, where my bot wasn't completing one of the quests in the Harrison Jones final series. It was just simply hovering over Harrison endlessly while loading tiles. So I stopped the bot, closed Honorbuddy, and restarted it. And then I got the message that Honorbuddy should update to the release offered today. So I updated, but the strange behavior still persisted. So I stopped the bot, finished the quest, and now I'm getting this error. "Bot stopped! Reason: Could not create current in quest bot!"

It seems odd to me, and I really hope that it doesn't mean that I need to finish questing in this zone manually in order to continue. I've tried a clean install of HB and I still receive the error. Here is the log. View attachment 6220 2013-11-21 00.57.txt

Any assistance you fine folks can provide would be greatly appreciated. I've never really had any irreversible trouble with this bot before. I'm using Kick's questing profiles, and the Questing bot. All my settings haven't changed throughout the course of my leveling. I haven't tried to run anything else yet, will update if any other characters encounter the same error.

 

Either delete the quest out of your log first then try to run the bot or complete it manually then restart the bot.

Just a Fancy Cockroach - Quest - World of Warcraft

Edit: Don't forget to keep the Kick Scripts updated daily, SVN provided.

Code:

http://kicks-scripts.googlecode.com/svn/trunk/

 

Thanks for the reply, you're awesome!

I did as you instructed and cleared the quest from my log, and it seemed to work for a moment. My toon ran to the quest barer and picked up the quest "Shaping Up" from Salhet.
But unfortunately, after doing so, it failed with the same error. View attachment 6840 2013-11-21 01.33.txt
I'll try finishing the quest now and see what error or success awaits me after. Any insight would be great.

edit: Finished the quest, and much to my disappointment, it still encounters the same error, even with no quests in my quest log.

 

Hey Tony, you're awesome man!

I did as you instructed, manually clearing the caches, in all the various locations, and then remained logged out for about 10 minutes after to make sure everything had repopulated. I even ran the clear cache script written by RobertPaulsen just to make sure. I logged back into WoW, and subsequently HB, and everything loaded fine, but I still encountered the same error script. View attachment 6872 2013-11-21 11.02.txt
Theres the log. Thank you guys for your continued effort.

 

Update: So I tried instead gathering the quest manually that appeared in the error. Its a quest that begins in Uldum automatically after you kill a scarab inside the Chamber of Stars, and has no actual quest giver. I wonder if that is maybe what caused the error, seeing as it couldn't locate a quest giver. Anyway, I killed a scarab, got the quest, loaded up HB and after a few minutes of loading data it began to kill all the scarabs required for the quest. Once finished, it turned in the quest and proceeded to run into a near by wall while navigating to a quest giver. There are no quests in that area, so I piloted my toon out of the Chamber up to the top, and now is perpetually loading tiles.

edit: Restarted HB, and now its just sat here loading tiles, and has been so for about the past ten minutes. Not run any behaviors. Just sitting there.

 

Yes, the bot completed the quest, and turned it in after I began it.

 

Done good sir.