Unable to login service stuck in starting state

SUGGESTED

None of the users I have setup for Sage are able to login from either the client or server with an error saying that the data service is not running. I notice on the server the Sage 50 Accounts service is stuck  in a starting state and is consistently eating around 25% CPU.

I phoned support but they just said to restart the service which I'm unable to do as it looks like a protected service and it persists across reboots anyway. Annoyingly there seems to be no logging so I can't see what it's trying to do that may be causing the issue.

It started happening around 19th February and I'm told an automatic update was applied around that time to add cloud based file upload functionality. Is there anyway to roll back this update to rule it out or am I going to have to go back to backups?

  • 0
    SUGGESTED

    Hi Mark,

    It’s not possible to remove or rollback any recent updates to your Sage 50 Account software.

    To resolve this you need to stop and restart the data service. To do this: 

    1. Right-click on the relevant services for the version of Sage Accounts that you’re using, e.g. Sage 50 Accounts v23: Sage 50 Accounts Service v23 and Sage 50 Accounts Control v23.
    2. Stop > right-click again > Start.

    If you’re still unable to restart the data service, what happens, e.g. any error messages, etc?

    Full info on how to resolve the messages ‘Unable to connect to Sage Data Service on machine [computer name]’ and ‘Data service unavailable on this machine’ here.

  • 0
    SUGGESTED
    Hi Paul,
    As mentioned the problem persists after reboots, turning it off and on again didn't solve the problem. Thankfully it now seems to have gone away on its own.

    >any error messages, etc?
    This is part of the problem, I can't see any errors in the Windows event logs and Sage itself doesn't seem to have any! All I've got is what was on the dialogue displayed to the user.

    There seemed to be a different message when logging into the server, "Processing, please wait..." as in this my.sage.co.uk/.../askarticle.aspx

    It therefore seems that the uploading of thousands of records was making it unusable.


    Thanks,
    Mark