Very weird - it turns out there must be a bad record somewhere pointed to that workstation - it works correctly everywhere else, and on that workstation once we renamed it.
Original Message:
Sent: 03-24-2026 12:11
From: David Overholt
Subject: Sage Custom Office Utility Rebuild Customizer Log. screwup now points all users/groups to std uncustomized screen.
if you run the utility to rebuild the log files first - that should set the pointers to whatever it finds in the "custom" folders so if you can verify the correct .M4L files are in there before and after you run that utility, running the update to current level utility should work as expected. (of course, "should" is always a term that I use cautiously with Sage utilities)
------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655
------------------------------
Original Message:
Sent: 03-24-2026 11:38
From: Lee Graham
Subject: Sage Custom Office Utility Rebuild Customizer Log. screwup now points all users/groups to std uncustomized screen.
All,
It is those mysterious pointers that are the problem - They are pointing at the wrong files. They probably exist to speed-up processing.
Restore from backup and re-do the 2022.2 to 2025.1 conversion again - but we don't know what went wrong so this could happen again. 38 user system.
Lee
------------------------------
Lee Graham
Friendly Systems, Inc.
Original Message:
Sent: 03-24-2026 11:15
From: David Overholt
Subject: Sage Custom Office Utility Rebuild Customizer Log. screwup now points all users/groups to std uncustomized screen.
I have never seen or heard of the utility doing that before. Are the "Custom" folders still in the various program folders? MAS90\SO\Custom for example.What are the dates on the .M4L files in those directories? if they are dated prior to when you ran the rebuild log file utility, it might mean that everything is still there, but custom office it not "linked" to those .M4L files running the rebuild Log files might fix it
if you ran the utility "update custom panels to current level", then a backup was probably created with a .BAK extension.
Keep in mind that you can't rename the .M4L files in those "custom" folders, Sage somehow knows you renamed it and points to whatever file you renamed it to.
------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655
Original Message:
Sent: 03-24-2026 10:07
From: Brett Zimmerman
Subject: Sage Custom Office Utility Rebuild Customizer Log. screwup now points all users/groups to std uncustomized screen.
I assume restore from bkup?
------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
Original Message:
Sent: 03-23-2026 22:33
From: Jeff Schwenk
Subject: Sage Custom Office Utility Rebuild Customizer Log. screwup now points all users/groups to std uncustomized screen.
probably the same reason that the printer files have every printer, every workstation and every user since the beginning of the first Sage installation.
------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444
Improving bottom lines for over 25 years!
Original Message:
Sent: 03-23-2026 21:14
From: Lee Graham
Subject: Sage Custom Office Utility Rebuild Customizer Log. screwup now points all users/groups to std uncustomized screen.
All,
Their S
Y_Personalize file has 10,837 records dating back to Sage 100 version 4.4 why?
Lee