Since this update im having a horrible time with the navigation.
Loading Kalimdor_36_33
Activity: Downloading Mesh...
Exception when attempting to download Kalimdor_40_29: System.TimeoutException: This request operation sent to net.tcp://www.buddyauth.com:5031/AuthService.svc did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/***** to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
Server stack trace:
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, *****OperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel*****.InvokeService(IMethodCallMessage methodCall, *****OperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannel*****.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.Real*****.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.Real*****.PrivateInvoke(MessageData& msgData, Int32 type)
at Styx.Auth.SR.IA.Do(Byte b, Object[] args)
at ..Do(Byte , Object[] )
at ..(Byte , Object[] )
at ..(String )
at ...( )
Exception when attempting to download Kalimdor_40_29: System.TimeoutException: This request operation sent to net.tcp://auth3.buddyauth.com:5031/AuthService.svc did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/***** to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
Server stack trace:
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, *****OperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel*****.InvokeService(IMethodCallMessage methodCall, *****OperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannel*****.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.Real*****.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.Real*****.PrivateInvoke(MessageData& msgData, Int32 type)
at Styx.Auth.SR.IA.Do(Byte b, Object[] args)
at ..Do(Byte , Object[] )
at ..(Byte , Object[] )
at ..(String )
at ...( )
Bots stays stuck, dosnt fights just waits and waits and waits.
If i hit, stop and restart i get this:
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
Goal: Flying to <470.02, -3157.72, 94.76>
[FlyTo-v501(debug) @line 53]: Flying to '<470.02, -3157.72, 94.76>': <470.02, -3157.72, 94.76>.
System.InvalidOperationException: DataReader already active on this command
at System.Data.SQLite.SQLiteCommand.InitializeForReader()
at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.SQLite.SQLiteCommand.ExecuteReader()
at Styx.CommonBot.Database.Connection.(SQLiteCommand , Object[] )
at Styx.CommonBot.Database.NpcQueries.GetNearestNpc(WoWFactionTemplate myFaction, UInt32 mapId, WoWPoint searchLocation, UnitNPCFlags npcFlags)
at Styx.CommonBot.Profiles.VendorManager.GetClosestVendor(VendorType type)
Exception when attempting to download Kalimdor_40_29: System.TimeoutException: This request operation sent to net.tcp://auth2.buddyauth.com:5031/AuthService.svc did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/***** to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
4.0
4.0
