Sage 100

We have a client that is on MAS 90 3.71 version. Her computer crashed and we are restoring her existing MAS data. I was able to perform the install but when I attempt to convert the data I received the attached error message. Of course, she does not have maintenance with Sage nor is the current version is supported. Any insight would help. I'm thinking her data may be a higher version than her install. Any help would be appreciated. Thanks in advanced.

Are you sure the files didn't get marked as read-only when they got restored?

Let me verify that. The client is remote so I don't have immediate access to the system.

Confirm that the file exist and that you have permissions to the file. Clicking Info may give more insight.

Why are you getting a conversion message on a re-install?

The GL1 file is the G/L Account Masterfile. Maybe you can restore that single file from backup if actually missing.

I agree with Wayne, now that you have the install completed just copy the backup of her MAS90 (the MAS90 folder and ALL subfolders) over your new installation and no conversion should be required. since this is 3.71 there is no ""uninstall"" directory to worry about.

correction the version is 3.51. I believe that the data may be at a higher patch level where as I only installed a base install of 3.51. She is not 100% sure on what version she was on before the crash.

To verify the version, go to the \SOA folder and look at the APREAD.TXT file. That file contains the version, A/P is normally the most current.

There was no patches except for hot fixes back in these days. If you are getting a message to convert are you installing 3.71? If so I beleive a conversion from 3.51 to 3.71 was a in-place conversion. I would verify that the GL1 file is there otherwise I agree with Kenneth to restore this file.

Then I would stick with my earlier suggestion. now that you have an installation rename that MAS90 folder on your new installation and copy your backup of her MAS90 directory with all the programs and data directories, run workstation setup and you should be ready ,to go without any data conversion.

For version 3.51, each module data folder should have a yy0xxx.soa file where yy is the module code, 0 is a zero and xxx is the company code. The last record should be a version record with the current level of the data. If the install is not functional, you can use Data File Display and Maintenance from any working install from which you can see and have permission to access the data. I always forget this stuff so I dug out my notes.

Thanks for all your help guys. I was finally able to determine that user was missing 4 files necessary in order to complete the conversion. I was able to replace the file but not with a backup. The client did not have the GL1xxx.soa file and will have to recreate her GL account information. Thanks for all of your help.