Sage 100

Sage 100 2016 Standard 2 user system. After working normally for months, the customer is getting screen errors in certain modules today. The system is acting as if something is wrong with Custom Office except there is no Custom Office installed on this machine. I have attached screen shots of the the error when trying to open AP Invoice Data Entry. Payroll and GL seem to open fine and I can run many (most) reports. The underlying data seems to be intact so there seems to be something wrong with screen settings.

Did they change their resolution on their monitor? That can sometimes cause this to happen. Or if they use the new setting to make things larger.

Check the Application Scaling setting and their monitor resolution. Anytime a panel is drawn and any part of the panel goes beyond the bounds of the monitor, you will get errors like this.

I'm with David, I assume the custom office line means that they don't have the custom office module? if not you could always try changing to classic ui. Also check the application scaling in windows (I cant see the launcher so i cant be sure with that one) but that's often a cause of unwanted activity.

They do not have the custom office module. They have been a simple 2 user system for years.

I had a customer on terminal server a few weeks back getting a similar message (see attached) they rebooted TS and it went away. This is probably a longshot but I didn't expect a reboot to fix it.

He claims that he hasn't changed his resolution and it is currently set to the maximum resolution. I had him reboot and that didn't help.

The M4L screen libraries are data files and viewable in DFDM. You could try to open AP_invoice.M4L with DFDM to see if you get an error there. You could alternatively restore the AP folder from backup. The first thing I might try though is renaming or reinitializing Sy_Personalize.m4t in MAS_System. It holds the screen size and position including whether you have maximized the screen.

Suggest that they consider upgrading to v2017 as this is the standard Sage feature meant to encourage upgrading...

@AlnoorCassim , I have tried refreshing the Sy_Personalize.M4T and it clears up the first error box but not the second. I even tried copying a fresh AP_Invoice.M4L from a working 2016 install. Could this be damage from a virus? This was working fine last week. Could this be from a Windows update?

Chuck - Sent you a chat msg.

We were able to resolve this issue. The best that we can figure out is that a file became corrupted. This could have been the result of a virus scan (they use Webroot) or a Windows update. I had replaced the Sy_Personalize.M4T and the various M4L files in question. I restored those from a backup copy created when the system was first installed. This didn't work. I also restored the Sy_Console.M4T and that didn't work. Actually, as I said above, the Sy_Personalize.M4T replacement DID get rid of the first error box. I stumped the Sage support people and they scheduled a specialist to look at it this morning. He agreed that there must be a corrupt file and we reviewed what I had restored. his next suggestion was to find the corrupt file in the ""Home"" and/or ""Launcher"" directories. Instead, we renamed those directories and restored backup copies from a snapshot taken immediately after the initial install. That cleared up the problem. I'm not going looking for the corrupt file but will be weary for the future.