help for missioner

[bombolo]

hi all
one question: missioner actually work?
used for month form some week don't work, launch bot go in station, find agent, open mission window, and try to open journal but the window is empty and this is the error:

13:45:30: obj_Agents: DEBUG: amIndex.Used = 0
13:45:30: obj_Agents: DEBUG: Setting agent to Asata Doisoro
13:45:30: obj_Agents: SetActiveAgent Asata Doisoro
13:45:30: obj_Agents: SetActiveAgent: Found agent data. (93)
13:45:35: obj_Agents: Starting conversation with agent Asata Doisoro.
13:45:35: obj_Agents: Waiting for conversation window...
13:45:36: Asata Doisoro :: Yes, I have something for you. We've decided to do our agents in Kisogo a favor. They've been complaining for quite some time of being overworked and underpaid, so we've decided to send them the perfect gift to soothe their nerves. A few packs of tobacco should do the trick, heh heh. It's at least something, until we come up with a better solution.<br><br>Deliver the batch to Kisogo VII - State War Academy School and a local supplier will pick it up from there and deliver it to where they're staying.
13:45:47: obj_Agents: ERROR: Did not find mission! Will retry...
13:45:50: obj_Agents: DEBUG: amIndex.Used = 0
13:45:50: obj_Agents: DEBUG: Setting agent to Asata Doisoro
13:45:50: obj_Agents: SetActiveAgent Asata Doisoro
13:45:50: obj_Agents: SetActiveAgent: Found agent data. (93)
13:45:55: obj_Agents: Starting conversation with agent Asata Doisoro.
13:45:55: obj_Agents: Waiting for conversation window...

after some minutes bot stop

 

[bombolo]

partially solved
if somebody have this problem here the solution

from forum stealthbot:

Q: I'm having occasional crashes when StealthBot starts conversation with an agent. It doesn't always happen but when it starts happening it won't stop happening. How can I fix it?
A: This is another ISXEVE issue. For a short term fix, manually start EVE, log in, and make sure the journal is closed. Restart (manually) EVE, log in, open journal, and start conversation with the affected agent. If the conversation came up, and it should, the problem is now fixed.
(http://www.stealthsoftware.net/forums/topic?id=24)