Sage 50 Accounts - Data Service Stopping...

SUGGESTED

Hi,

I'm been running Sage Line 50 for several years on a shared PC with multiple users using the 32 bit apps.  We've recently upgraded to 64 bit version 31.0 and then 31.1 shortly afterwards.

With this came a problem whereby the data service randomly stops.  It might be after an hour or 2 and I can't identify what's triggering it.  I can easily restart the service and no data has been affected but it is driving us mad!

One thing I've noticed for a few months has been the need to stop and start the service everytime I reboot the host machine.  We use ESET Protect and have carefully following Sage's instructions re opening the relevant ports.  I've been passed back and forth a bit between Sage and ESET.

Please does anyone have any suggestions which might cut to the chase please?!

Thanks!

  • 0

    Hi Alex,

    Thanks for your post.

    I'll leave this thread open in case others have experience of using Sage 50 Accounts in combination with ESET Protect.

    I did find the following Knowledgebase article that refers both to the Data Service and ESET: Data service error... 

    Regards,

    Andy
    Sage UKI

  • 0 in reply to AndyR.

    Hi Andy, thank you for your reply!

    I didn't mention it in my post but we also use tools from Adept and have switched the SDO components to running on 32 bit to make them work due to an ESET incompatibility which now works fine.

    Re ESET, I have removed ESET entirely from the host machine and Sage 50 works absolutely fine for all users until the Data Service stops, so for an hour or so SAGE doesn't have an issue with the ESET configuration and vice-versa.  Am I wrong to think that if it works quite happily for an hour or 2 that it probably isn't ESET - surely it would work or wouldn't work at all?

    Regards,

    Alex.

  • 0 in reply to Alex Franklin

    Thanks Alex, no I agree, you've taken steps to take ESET out of the equation and the data service issues persist. On that basis I'd suggest contacting Technical Support again for further investigation as you've ruled ESET out.

  • 0

    Hi,

    Just in case this might help anyone else, it turns out the issue was caused by a single machine, identified by the person using it remembering doing something just before it crashed each time.  Strangely the trigger was switching between various companies.  I have reinstalled Sage on the machine and so far so good...

    Thanks for being there!

    Regards,
    Alex.

  • 0 in reply to Alex Franklin
    SUGGESTED

    Thanks Alex, really pleased you got to the bottom of it! Thanks for coming back to share that- Andy

  • 0 in reply to AndyR.

    Hi, sorry not to get back to you sooner!  So, as confirmed, switching companies from within Sage stops the data service.  This has been temporarily resolved by telling the user not to bloomin' switch companies from within Sage!  So, the issue hasn't been fixed and is one I'd still like to solve.  This is paired with the data service needed to be manually switched every time the machine hosting it is rebooted (even though it is set to start automatically).  Has anyone experienced either of these issues?