chriscounter07
asked on
Why does Sage 2008 get corruptions in first place and can they be fixed by us and not Sage?
When we backup Sage each evening we always run a data check to ensure no corruption. On two occasions, last Friday and about a month ago, it came back with error. The message normally goes along the lines of certain transactions references do not balance. This should be impossible, and clearly shows corruption within the data.
There are only 2 options to resolve the issue. One is to upload the program data as a file to Sage who have their techies fix it for free (part of insurance we pay) but it takes up to 3 days and we would not be able to use sage until they return the corrected data! They can usually do this without losing any of the work done that day.
They're only suggestion is that a power surge might be involved. But this is a network - with normal network traffic? Surely the Sage techie is relating his/her answer to a server actually being offline at any given point i.e. hard reset mid way through operation.
The second is to reload the last uncorrupted backup (in our case the day before), which obviously means that the work is lost but is the quicker option.
Questions are:
- Why does this happen?
- How can you tell which type of database, be it Access or SQL, you have - we do have SBS 2003?
- Can it be fixed manually?
- I have seen an EE answer suggesting a program which backs up every hour or so? Any thoughts on this?
There are only 2 options to resolve the issue. One is to upload the program data as a file to Sage who have their techies fix it for free (part of insurance we pay) but it takes up to 3 days and we would not be able to use sage until they return the corrected data! They can usually do this without losing any of the work done that day.
They're only suggestion is that a power surge might be involved. But this is a network - with normal network traffic? Surely the Sage techie is relating his/her answer to a server actually being offline at any given point i.e. hard reset mid way through operation.
The second is to reload the last uncorrupted backup (in our case the day before), which obviously means that the work is lost but is the quicker option.
Questions are:
- Why does this happen?
- How can you tell which type of database, be it Access or SQL, you have - we do have SBS 2003?
- Can it be fixed manually?
- I have seen an EE answer suggesting a program which backs up every hour or so? Any thoughts on this?
Nick Denny
Just to clarify, which "flavour" of Sage are you referring to? Line 50, 100, MMS 500 etc....
ASKER
Line 50
I had a client last month who had this problem. I put it down to two possible things:-
(1) They have a Vista pc on their network which hooks into Sage, but I believe this pc to be only used for Enquiries, not for posting. But worth mentioning anyway.
(2) The main thing that I thought of is to do with Record locking and forcing records to be flushed to disk, rather than being cached. This involved some Registry changes.
The data is stored in a proprietary format, it does not use any SQL engine.
Sage do not support network issues - that's the official line, so I am told.
(1) They have a Vista pc on their network which hooks into Sage, but I believe this pc to be only used for Enquiries, not for posting. But worth mentioning anyway.
(2) The main thing that I thought of is to do with Record locking and forcing records to be flushed to disk, rather than being cached. This involved some Registry changes.
The data is stored in a proprietary format, it does not use any SQL engine.
Sage do not support network issues - that's the official line, so I am told.
Found the reference I worked with. Do this on ALL the workstations: disable Opportunistic locking:-
http://support.microsoft.com/kb/296264/en-us
http://support.microsoft.com/kb/296264/en-us
sorry, forgot to explicitly mention:-
...and on the server.
...and on the server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Very good, thankyou