General Consultant Discussion

Has anyone else encountered such corruption? My seemingly simple project to reset a company startup wasn't so simple thanks to data corruption like I've never seen. Or seen reported. The only thing that I know of that causes this type of corruption is power interruptions but this was bad. So I have to ask - could this be caused by anything else? Examples: Sales Order, detail file has 486 records doing into DFDM to view, yet Crystal Reports extracted over 13,000 records. (WT?) Review of the exported data shows over 400 detail lines for one order which actually only has 3 detail lines none of which have been cancelled, overwritten, and the SO number new. Reinitializing a data entry file, empty through DFDM has a file size of 233KB - should be 13kb. Even the primary Role corrupted, not allowing access to approved areas (this was the event that got my attention). I created a new Role, assigned to users and haven't had any further issues in that area. Is this really all because of power issues or are there other places to check? What else could cause something like this?

Version of Sage, Server OS, Workstations?

Of course, Sage 100 ERP 2014 Advance, PU6, Running application as service on Windows Server 2008 R2 SP1, Users on Windows 7 (64bit)

Of course, Sage 100 ERP 2014 Advance, PU6, Running application as service on Windows Server 2008 R2 SP1, Users on Windows 7 (64bit) -(did I answer in the correct method-what is the difference in Answer vs Comment)

The cause would take investigation. However I've seen most of what you've described and for me it was never massive data corruption. What you could try is clicking the Optimize box in RKF for SO_SalesOrderDetail then doing regular RKF. When finished view through Crystal again. The bloated file size is not unusual especially for history files where a purge took place. When you reinitialized did it actually return back to a normal file size? It's very important that happens. On the security role stuff, seen that a bunch of times. You fixed it perfectly. That is a Sage issue btw not system issue.

The extent of the corruption was indeed surprising and thus drove me to this inquiry. 233kb was the file size after reinitializing the file. The file has since been renamed and manually replaced. And thank you for the Optimization reminder. I did optimize the rebuild, It's a rare occasion that I don't optimize. You taught me well when we were at Sage and I still hear the words of Alnoor in my head. Thankfully. (To clarify that statement, I hear words in my head, not voices. The voices are mine. :) ) There is so much talk about bugs/virus' and systems being hacked these days the client has some concern that these might have caused the corruption, and not the power interrupts or outages that occurred. What I am hearing in the responses is that in our experiences, ""none of these things have ever been known to or has been reported to cause this type of data corruption"". Correct? JD

www.eversafe-backup.com LOL

LOL, Sharp eye Mark. Not one to miss out on a potential lead. Well Good for you! But they are covered-thank you. Client opted to reset then restore based upon some other factors involved.