Is anyone seeing issues with checking or backing up data from a server?

SOLVED

Hi,

Is anyone having issues in the last week or so with checking data or backing up data where the data is stored on a server?

We are an accountancy practice and have multiple clients using Sage, both on their own systems and also on our internal copy of Sage.

In the last week or so we are seeing issues with both the check data and backup routines failing when trying to create the checkpoint, saying either 'Check data terminated unexpectedly' or 'Backup failed unexpectedly; (I'm typing from memory - the exact error may be slightly different).

Doing some digging, the problem is affecting multiple versions of Sage from 26 to 28, but only seems to be happening where the sage data is stored on our server. If i manually copy the data from the server to a local machine, then checking and backing up the data works fine.

We are running the latest version of 26, 27 & 28, have made no changes since Christmas (when things worked fine) and also, crucially, we have at least one client suffering the same problem.

We are running Server 2019 and the client is running 2016. Is it possible that a windows update is doing something that Sage doesn't like?

Ross

Parents
  • 0

    Update - turning off the option to allow backups while other users are logged in fixes the issue as long as everyone else is logged out of the dataset. This allows us to backup but it's not ideal.

    It looks like it doesn't create a snapshot this way, so it definitely seems the issue is with creating the snapshot.

    If anyone from Sage is reading this, is there a way to tell where the snapshot is being created so I can check if there's any issues with permissions etc?

  • +1 in reply to Ross Nicol
    verified answer

    Final update - the problem is now resolved.

    Not sure exactly what the issue was, but the server involved was re-started for other reasons (we don't normally reboot them as a troubleshooting step, especially in the middle of January when we have tax returns to prepare and the server involved is key to producing them) and the probem has vanished.

    Sorry for taking up anyone's time un-neccessarily - our client having the same issue threw me and made me look for a more widespread solution than our own server Disappointed

    Ross

Reply
  • +1 in reply to Ross Nicol
    verified answer

    Final update - the problem is now resolved.

    Not sure exactly what the issue was, but the server involved was re-started for other reasons (we don't normally reboot them as a troubleshooting step, especially in the middle of January when we have tax returns to prepare and the server involved is key to producing them) and the probem has vanished.

    Sorry for taking up anyone's time un-neccessarily - our client having the same issue threw me and made me look for a more widespread solution than our own server Disappointed

    Ross

Children
No Data