So… I’ve not been impressed with Sage Accounts 2015 so far. First they block installation of the software on Small Business Server 2011 and I had to call to get the information on how to get it to actually install.
Secondly I was told that you can no longer use a mapped drive as your location for Sage files, this causes problems with the backup method now? I had to go around each computer and replace the z:\COMPANY.XXX path with \\fileserver\sageaccounts\COMPANY.XXX !
Then… I find the server has massively slowed down and at least one of the client computers are dog slow too.
In the case of the server it seems to start a scheduled backup using the windows Temp folder as a scratch area and never completed it, abandoned it(?) and then did the same the next day. This, after a while, filled up the server hard disk.
Sage Scheduled backups (a new feature in this version of Sage as far as I know) seems to use the “c:\windows\temp\YYYY-MM-DD HH-MM-SS” folder structure to stage it’s backup. It seems to, when working correctly, copy the sage company files into the temp folder and then compress them into c:\SageBackups and delete the Windows Temp folder. (The server wasn’t managing to complete the backup so the temp files just accumulated).
I’ve solved this one simply by turning off the inbuilt Sage backup off.. the server already has a robust and regular “versioned” backup onto external hard disks.
The problem I can’t fathom out so far is the one of the client computers on the network. The symptoms are constant hard disk activity and the machine being awfully slow. There is no sign in Task Manager that the cause might be Sage… It isn’t using a huge amount of RAM or CPU.
The only way I found out was using Process Monitor from Sysinternals / Microsoft.
Process Monitor shows sg50svc.exe copying random crap, such as Google Earth and some Chrome files from the users AppData folder into the “c:\windows\temp\YYYY-MM-DD HH-MM-SS” folder! What?! Anyway.. end the process and the machine speeds up and everything is normal again, until the next day when it starts doing the same thing again.
I checked that the scheduled backup option was off and, again, it is.
Sage have been contacted with a video showing this madness.. watch this space. It seems their new scheduled backup option and code needs some work!