This is a long shot,  but I once had something that sounds similar because I had invalid custom windows (or was it custom report folders).

I had renamed a folder ABC-TOM to something like ABC-TOMBACKUP.   Got rid of the ABC-TOMBACKUP and all was well again.

Hi BL,

Surprisingly DSD says it is not one of their programs :-)

Did you know Nathan is no longer there? Just found out.

Hi Tom,

Part of my list of "Usual Suspects" involves going through and removing any file or folder that doesn't look right. It may be that something like what you describe has so far eluded my gaze.

Now that I have temporarily abandoned the quest I am taking their SQL Database and their MAS90 directory and throwing them onto a virtual machine so I can really get tough with the files and find out what's going on.

I'll update if/when I figure this out, for those who may be curious.

Ahh.  Sage 100 Premium!

We've had issues with company copy when we've added an extra table (in SQL, non-UDT) to a MAS_### database.  However this seems more like a dll issue.  Have you disabled UAC?

We've had issues with company copy when we've added an extra table (in SQL, non-UDT) to a MAS_### database.  However this seems more like a dll issue.  Have you disabled UAC?

UAC was not enabled, but thanks for the reply.

After copying the client's MAS90 directory to my test system and replacing the SOA directory with a "clean" one from a Premium System I had installed I could then get the update to install without error*. So I have proven that the problem lies within the SOA folder. I won't really know if this is resolved until we do this in the live system and the users test to make sure data and functionality are intact.

* Steps, if you're curious:

1. Install base Sage 100 Premium system over top.

2. Install current PU to match live system.

3. Install PU 8.

4. Install PU 8 programs for DSD Multi-Currency

5. Convert.