bot getting errors and getting stuck

[redlne6]

the GB2/PB keeps getting stuck and generating errors while trying to level herbalism using http://www.thebuddyforum.com/archives/24285-professionbuddy-1-525-herbalism.html

 

[no1knowsy]

Please attach the log file.
If it's the most recent log you can click the "Date Modified" column near the top to arrange by which file HB last added.

"//Honorbuddy/Logs/"

 

[redlne6]

i think i attached txt file of it.

 

[no1knowsy]

I'm not sure why, but your Honorbuddy is Unloading Tiles a lot, which of course makes it load them again...

Are you using Windows Vista or Windows 7,
and are you clicking Run As Administrator on Honorbuddy.exe? (Right Click)

 

[redlne6]

checking the run administrator way
i highly doubt it will make a diffrence tho

 

[redlne6]

same thing really and im using windows 7 =/

 

[killgogeta]

same thing here and i used windows 7 64 bits
PB and GB2 made same since 2 update of Honorbuddy.

 

[killgogeta]

after some restart GB2 work (selected manually the good profile) but not PB.

 

[Tony]

i think i attached txt file of it.

[1:06:02 AM:728] MeshesFolderPath: C:\Users\Andrew\AppData\Local\HonorbuddyMeshes
clear your mesh folder and try again

 

[Tony]

same thing here and i used windows 7 64 bits
PB and GB2 made same since 2 update of Honorbuddy.

pick Combat bot as a secondary bot in PB settings

 

[redlne6]

[5:35:37 PM:940] Exception when attempting to download Expansion01_18_25: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
at System.ServiceModel.Channels.SocketConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.DelegatingConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.SessionConnectionReader.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.SynchronizedMessageSource.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.FramingDuplexSessionChannel.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceive(TimeSpan timeout, Message& message)
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at IA.Do(Byte b, Object[] args)
at #h.#nK.Do(Byte b, Object[] args)
at #1J.#6J.Do(Byte b, Object[] args)
at #1J.#6J.#hSc(String file)
at #QH.#SH.#h.#rb.#xQc(#6J s)

 

[Tony]

http://www.thebuddyforum.com/honorbuddy-forum/guides/9859-how-attach-your-hb-log-file-pictures.html

 

[redlne6]

still not working after doing all thats been suggested

 

[Kookajamo]

This exact same thing is happening to me and in my thread countless more people said it is an issue.

I pride myself in being pretty experienced in using the bot and I'm pretty sure if this many people are reporting this as an issue it's most likely not us just doing something wrong.

 

[Tony]

we are aware and its going to be fixed

 

[MoMedic]

we are aware and its going to be fixed

Thanks Tony.

As I'm having the exact same issues as others have posted, I look forward to the fix.