03333 445950
What are 03 numbers?



Making I.T. Happen
Accounting and Information Technology, Assistance and Support
All about Sage 50 - Data Errors

Sage 50 can get it's data corrupted as a result of random events it can also get corrupted due to issues with hardware and software.

There are 3 things that all sage users should know.

1/ You MUST check your data before you backup, backing up worthless corrupt data is pointless.

2/ DO NOT run the fix option until you have made a separate backup of your corrupt data.

3/ Backups are really important.

Unfortunately this advice come too late to some users, they have corrupt data and they do not have good backups or even have no backups at all.

We have the ability to repair data and fix some errors. HOWEVER where data is destroyed there is no way to reconstruct it.  fixing data is only part of the bigger picture, you need to put in place a good backup procedure to be able to recover better form a future corruption and you get regular corruption you need to find the cause and fix it.

Sage offer a data repair service for customers on SageCover Extra this is available at no extra charge  however, it takes days for Sage to fix your data and you may need to be doing work now.  If you need data sorted quickly or do not have sage cover, things can get very expensive.

We offer a range of data repair services to help users in these situations.  We can do overnight repair, we can merge data sets, we can rebuild new data sets from old data.  We understand that you need to keep your business going and can not be without core systems for days.

What causes data errors?

There are many causes and there is plenty you can do to reduce the risk.

  • Natural events
    • The odd gamma rays, that flips bits on a disk.
    • Power cuts - (UPS would avoid this)
    • Power spikes (Power filters may help with this)
  • Corruption of the communication between the client running sage and the server.
    • Hardware Issues
      • Faulty Data Switch or bad port on switch or a loose connection, (Swap all the cables into different ports, try a different switch)
      • Damaged Cables(Swap the cables)
      • Loose Connections (unplug and replug listen for a nice click, check cable is firm)
      • Low Bandwidth causing large packet loss
        • Old 100Mbit networking  (Upgrade to gigabit)
        • WiFi (NEVER NEVER use sage over WiFi it is too unreliable)
      • Faulty network cards 
      • Electrical Interference arc welders, high current high power equipment.
      • Testing software, for bandwidth, packet loss etc is available, we can help you with this if needed.
  • Software Issues
    • Faulty drivers for network cards
    • Running Mixed SMB environments (SMB 1 was used by XP if you use XP and Windows 7 or later then there are issues, ask for our sheet on SMB configuration if you think this may apply to you)
    • AntiVirus issues (Anti Virus software slows things down, the sage data files are not a high risk item and can be excluded from being "real time" scanned, ask for our anti virus notes if you need them) 
    • Firewall Issues (fire walls should stop external communication and nothing in the local network under normal circumstances)
    • Access rights issues (all sage users should have FULL access rights to the directory with the sage data and all its subdirectories, reset the permissions and be absolutely sure they have FULL access rights)
    • PowerSaving
      • hardware that goes "to sleep" (Disable hardware from sleeping)
  • User Issues
    • Ignoring the warning about the username still being in use when logging in. (Educate users, create spare users so that if you need to log in but are already logged in you can use a different username if you clear your user forget you did it and go back to your desk and use the disconnected login you will corrupt data)
  • Probability
    • The more data you have, the larger the databases the more traffic, the more potential for things to go wrong, you can improve your odds by reducing your data set in size and doing a year end procedure as we recommend (our year end procedure recommendations can be sent to you on request)

Types of error

The most common problem is one of overwriting data, this is where one user writes data and another user writes data in the same place.  This is what happens when one of the users fails to "talk" to the central store and so other users don't wait for them.  This results in Headers not being linked to the Splits and having splits transactions that are orphaned or that belong to different headers to those they are linked to.






Home Account Apply Terms
Pay- as- you- go Sage 50 Support, Data repair, Sage Reports, Excel- Sage 50 Data Links and Reports,3rd Party integration and more!
Copyright © Making I.T. Happen 1995 - 2018