Pages:
Actions
  • #1 by binsey on 06 Mar 2014
  • Hi,  had MFP quit unexpectedly this afternoon losing me a small fortune.
    2 questions, I can't find anywhere in the log a reason for it quitting and it's never done it before. Secondly I seem to remember a post some time ago from a  senior member who was using a script he had developed which constantly checked that the programme was running and if it had quit, it signed back in automatically ?
    Can you help me on either of these fronts, as if I can't rely on the programme to function without error I might as well stop using it .
    Regards
  • #2 by 1oser on 06 Mar 2014
  • Hi,  had MFP quit unexpectedly this afternoon losing me a small fortune.
    2 questions, I can't find anywhere in the log a reason for it quitting and it's never done it before. Secondly I seem to remember a post some time ago from a  senior member who was using a script he had developed which constantly checked that the programme was running and if it had quit, it signed back in automatically ?
    Can you help me on either of these fronts, as if I can't rely on the programme to function without error I might as well stop using it .
    Regards

    check my posts
  • #3 by mcbee on 07 Mar 2014
  • hi
    can you please include a screen shot of your program log.

    mcbee
  • #4 by binsey on 07 Mar 2014
  • Hi, the program appears to have quit at 15.55, I logged back on at 17.25 when I realised  what had happened, but there is nothing in the log at all .
    Many thanks
  • #5 by mcbee on 08 Mar 2014
  • hi
    can you check to see if your windows or other software has updated at the same time please.
    maybe the computer was re started due to an auto update requireing a restart.

    mcbee
  • #6 by binsey on 10 Mar 2014
  • Hi, I checked whether the computer restarted and it definitely hasn't. I configure windows updates manually. Any other ideas  ?
    Thanks for your help
  • #7 by mcbee on 11 Mar 2014
  • hi
    how long have you been running the software without this happening.
    if it is over a month then there must have been some software on your computer that updated or scanned at that time causing the bot to shut down.


    mcbee
  • #8 by racepro on 11 Mar 2014
  • Hi,
    I had the same experience a few times late last year however seems to have been resolved.
    I have had my broadband drop 3-5 times a day/night since installing it last September.
    Please check to make sure your broadband is stable. MFP is usually stable but sometimes the link with Betfair is lost during a drop out.
    Cheers
    R
    ps.... coincidence has it that BT are finally coming out tomorrow on a no fee (£169) basis.
    I was beginning to think there was more chance of Jennifer Aniston rocking up.  :)
  • #9 by binsey on 11 Mar 2014
  • happened again yesterday ,this time got the following error messages

    error 32503 error getting funds at BF
    error while updating the account statement api error no session
    failure to reinstate session invalid vendor software id current betfair ststus online

    any thoughts ?
  • #10 by racepro on 11 Mar 2014
  • Hi,
    Just a thought, perhaps you could open a new profile and see if that makes any difference.
    The "api no session" message sounds like a line drop. Is your broadband connection stable and a good speed?
    R
  • #11 by mcbee on 11 Mar 2014
  • hi
    Quote
    error while updating the account statement api error no session
    Quote
    api error no session

    it looks like the api was at fault, they are doing changes all the time ready for the switch over to the new api

    mcbee
  • #12 by Oxa (WellDoneSoft) on 11 Mar 2014
  • binsey, what version of MF Pro do you currently run?
  • #13 by binsey on 11 Mar 2014
  • It's 7.1.0.10
  • #14 by Oxa (WellDoneSoft) on 11 Mar 2014
  • If you upgrade to 7.1.0.11, there is a much better chance that the software will be able to reinstate the BetFair session after its loss, so definitely recommend that.

    Download links
  • #15 by mithcd on 27 Mar 2014
  • By the way, did version 7.1.0.11 fixed this by any chance?
Pages:
Actions