Hi, I have a client where on two terminals the SambaSettings.txt file changes back to the original file every +/- 20 days and we have to setup Massaging Server and DB settings again. What could cause this? TIA.
The settings are written when saved and also on (graceful) application exit.
One of two things might be happening:
a) there is an instance of SambaPOS running with the wrong settings that get saved when closed
b) someone is messing with the settings
My money is on b.
Yes that file does not randomly get changed by sambapos. That is not possible… the 20/21 days you explained really sounds like someone is messing with it. Maybe unknowningly.
As with any request… it helps if you explain what version of SambaPOS you are on, and you provide some screenshots… In this case it may be hard for us because given what we know about that file, it really sounds like someone is messing with it.
Thank you for the info. I think I found the problem. If I do a continues Ping on the Server it loses packets. Testing to see if it is the cable or network card. (Client uses ver. 5.7.14)
The settings are stored locally, so network connectivity will not have anything to do with the settings getting reset.
Another reason I have seen a few times in the past is if the system runs out of disk space - in this case when SambaPOS is closed, it cannot save the settings file properly and ends up with no settings file. On next load, a new settings file is generated with the default settings.
When you say it happens around 20 days, this could be when the database backups are filling up especially if its a larger database then clearing the old backups is giving more available disk space. An easy solution for this is to just turn off automatic database backups within SambaPOS and use a third party solution to automate SQL backups - I have used SqlBackupFree many times which is free and lets you set how long backups should be kept locally (plus gives added features like uploading backups via FTP to a remote server).
Thank you. I will check that.