Sage 100

I have a client with major data corruption in Payroll after a server crash. The files I can't get fixed are PR_22 and PR_23 and there are no backups for 2013 (last backup is 12/31/2012). When I go into DFDM, the program stops on the record before the bad record so that I can't correct the bad record or possibly the first of many bad records. Any ideas? Any guru's that could correct these files for my client? Thanks in advance.

Can you write a Crystal and get whatever good data there is out?

I tried exporting to Excel and it failed so I think trying to go to anything that uses the ODBC won't work, but I'll give it a try.

At this point in the game, I find several shots of good whiskey helps with taking the edge off.....

Try exporting via VI. VI doesn't use the ODBC and will usually export the garbage informaton so you can find/fix it.

http://www.s-consult.com/support/activekb/questions.php?questionid=34

DSD has a program call data rebuild master. (DRM) that should work on non-business frame files. What version are you on?

It uses an different method than the Normal rebuild and it is very effective. How big are the files?. I can do a test run for you on them if you would like.

Www.disaster-recovery-solution.Com Sent from my Samsung Galaxy S3

Version is 4.5.3. The files are very large. 1500 employess per year with about 10 years of data.

Zip them up and check what is the size is then. Soa files usually can compress up to 90%. Email me and we can arrange to review the files.

Thanks Jim. I'll be in touch in the morning. Wayne - sorry, it has been a long day - do I substitue pr22xxx for sy0ctl.soa?

Exactly Jane. Be sure to backup the file before running UFAR.

I agree with @RobertWood and @WayneSchulz, *ufar is the only way to go at this point since both of those files are keyed files and always backup. The golden rule of support - 'If you have a backup, you won't need it'

Or the even bigger mantra of, ""If you don't have a backup, you will need it"".

So in all seriousness, what was there scenario in not having a valid backup for 4 months? Some of you know we are rolling out a backup & disaster recovery solution, and I like to understand better as to how these things happen and what percent of companies are living on the edge and may not even know it. I can't imagine a ton of $5m+ companies knowingly not backing up so I wonder why these emergency data recovery companies stay so busy.

Usually it's the IT department and they either don't understand where Sage is loaded, try to do some awful incremental backup that they learned in college 30 years ago or they're just flat out incompetent at IT.

I don't know all of the details, but there was something about mirrored drives not working and outsourced backups not being done. I guess this shows that if you pay someone to do your backups, you better be sure they are being done. Wonder if there is a lawsuit on the way.

Or IT thinks of losing the accounting data like losing an Excel file. This IT department didn't seem to think reconstructing months worth of data would be a big deal (or that was my impression anyway).

Regardarding backups, I find one a backup device, process is put in place the Accounting Departmner, IT, all departments forget about it, no testing is usally done and it is tested only if we suggest to test or something happens where they needed a file or files then find out oops, can't get it. I don't know why though I have always beleived this is a hugh hole for companies. No diaster planning what so ever.

It's not a BACKUP system, it's a RESTORE system.

Thanks everyone for your help. *ufar did a pretty good job of cleaning up the perpetual history data. The issue we are having now is that the people who did the data recovery weren't able to recover the files very well.