Sage 100

I have an existing MAS 90 (not 200) 4.50 client who owns Custom Office. For some odd reason Custom Office is not installed. Their Keys are valid and Sage has verified by starting a new installation on their system that Custom Office installs. When I try to install over the existing installation and the Module List appears, Custom Office is not in the list. If I start an installation in a new area on the server, Custom Office does show up in the list of modules. What system-level file is screwed up where it doesn't think Custom Office is a valid module for the keys? I seem to remember some file, like a .ini file, that holds a big string of module information. Does anyone know what is causing this? I don't want to have to go the route of installing MAS in a new area on their server, have new workstation setups, people lose their personalizations, yada, yada. Ideas?

Can you copy the mas90 folder out to a temp folder then delete or rename the current folder and then install and migrate back from the copy?

Long ago wasn't custom office not included on a small user license sales? Perhaps that's the issue.

Can you no longer customize and pick a module (whether you have valid unlocking keys or not)? Then try to access custom office with your current keys.