Sage 100

Have a client with remote users that experienced a communication break while processing yesterday. It appears to have corrupted a few files in the Launcher folder; mnumod.txt to name one. Per Sage support, we restored the Launcher and System directories from backup made Monday night. I just want to play a little CYA here and make sure I'm not forgetting something that may jump up an bite me in the shorts latter down the road by restoring these folders and not the company folders. Per the client, no changes were made the following since Monday night: users, security, zip codes, sales tax tables, payroll tax tables (PR not used). They have run reports in AR, AP, IN, and WO to make sure nothing looks amiss. No posting was underway when the communication failure occurred. Am I missing anything?

Shawn, I think with the Launcher folder no worries, with System folder your correct as lon as no Security was changed, Tax Codes or Schedules were setup, VI jobs etc I think you should be okay.

What version is this in? For some reason the SOA file comes to mind.

@JoanSerr, sorry for not providing version info. 4.50.4.0.

@RonPeterson no VI changes either.

At least for me, in this release I would keep the 'system file' family together, Restoring Home, SOA, Launcher and MAS_System especially since WO is mentioned and that is legacy still today.