In System Administrator - Automatic backup fails

SOLVED

I am curious if anyone else is having issues with the Automatic Backup Feature failing in the System Administrator.

I can backup manually just fine, but the auto backup gives me this error:

2018-12-25 20:00:00 Starting backup
2018-12-25 20:00:15 Folder does not exist: C:\ProgramData\SageReplicator
2018-12-25 20:01:05 There is no SQL Server service named “SQL Server (MSSQLSERVER)” running on this machine.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

The system cannot find the file specified
2018-12-25 20:01:05 Canceled

This is what I get from a manual backup:

2019-01-09 06:42:13 Starting backup
2019-01-09 06:42:30 Folder does not exist: C:\ProgramData\SageReplicator
2019-01-09 06:43:09 Successfully created C:\Users\administrator.AD\Desktop\Backup\backup190109_064213.zip

Any input would be appreciated.

Mary

  • 0

    I'm also getting the same error as Mary, using version 18.2.2.20 of the System Administrator for Sage 300 Construction and Real Estate.


    Automatic backups with "Files -> All" selected for most company folders fails with the same message:

    2019-11-20 23:34:57 Starting backup
    2019-11-20 23:36:58 Folder does not exist: C:\ProgramData\SageReplicator
    2019-11-20 23:44:51 There is no SQL Server service named “SQL Server (MSSQLSERVER)” running on this machine.
    
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    
    The system cannot find the file specified

    A manual "Back Up Now" works fine with the same options chosen.

    Not using Sage Replicator.

    Thanks

  • 0

    I spoke to Sage about this and it is glitch in the current system.  They should have fixed in the next update.

  • 0 in reply to McMahan

    Thanks for the follow up, good to know it isn't specific to our install.

  • 0

    I realise this post is a little old now.  However, my company has just been upgraded to 18.2.2 in June 2020 (in Australia we have been told this is the latest version available in Australia).  I rely on this automated backup process as part of my backup routine.  I am now faced with running these backups daily manually  (which can only be done when everyone is out of the system).  This is very frustrating and and annoying to the users - when it previously worked perfectly.  Has there been any solution to this?

  • 0 in reply to Fozzie
    SUGGESTED

    I agree that this backup solution is a step backwards.  The backups can be automated through the Sage Admin interface however you are correct in that if anyone is in the system they fail.  Running this is especially important if using the SQL Replicator.  We actually host our Sage system on a virtual machine and that backup, with the SGL Database on the same machine, is how we feel assured of being safe as it takes a time in place snap shot.  But I do check on these backups every few weeks and make sure they run occasionally. 

  • 0 in reply to Jeff Rudacille

    Thanks for your reply.  However my issue is that since the 18.2.2 upgrade - that automated backup within Sage System Administrator is no longer working at all. 

    I can run these backups manually but the automated backup worked perfectly prior to the upgrade and now fails. 

    Therefore I have to run these manually (at a time when no-one is on the system - which means staying up late to do it).

    Is there any solution to fixing the automated System Administrator backup in this version please?

  • +1
    verified answer

    I thought I would add to this thread.  We upgraded to 18.4.1 and now the automated backups are working.  It seems to be fixed.  I have it set to backup at 10:00 each night.  Then at Midnight I have a third party program back the backup files to the cloud.  Each night a new individual zip file is created so I keep about 4 months worth before I delete them out.

    I still get the Replicator can not be found message, but then it backs up.  Here is a small sample of my log.

    2020-05-16 00:00:00 Starting backup
    2020-05-16 00:00:17 Folder does not exist: C:\ProgramData\SageReplicator
    2020-05-16 00:01:02 Successfully created C:\Users\administrator.AD\Desktop\Backup\backup200516_000000.zip
    2020-05-17 00:00:00 Starting backup
    2020-05-17 00:00:17 Folder does not exist: C:\ProgramData\SageReplicator
    2020-05-17 00:01:02 Successfully created C:\Users\administrator.AD\Desktop\Backup\backup200517_000000.zip
    2020-05-18 00:00:00 Starting backup
    2020-05-18 00:00:17 Folder does not exist: C:\ProgramData\SageReplicator
    2020-05-18 00:01:02 Successfully created C:\Users\administrator.AD\Desktop\Backup\backup200518_000000.zip
    2020-05-19 00:00:00 Starting backup

    I have broken out the files from the zip and they are all correct and everything is included.  So I think it is fixed in 18.4.1

  • 0 in reply to mmccleary

    Thank you.  Yes that was the backup process that I used prior to the upgrade also (SageBackup to .zip file on disk and then backup to cloud - keeping the zips for 6 months) .  It is good to know that this has been resolved in 18.4.1 - however I have been told that we are unable to upgrade further than 18.2.2 in Australia at this stage.  I am working on a script  (still testing)  which can be run with Task Scheduler to do backup to a .zip file etc.  to try to get around the issue until we can upgrade. 

  • 0 in reply to Jeff Rudacille

    thank you - looks like a similar issue (however, the txt file doesn't exist in in our folder structure).  Will test to see if it works.