Sage 100

converting v3.71 to 4.5 standard... cant get past GL out of balance pre-migration. The file PL Options is being used by another task. unable to find anything similar in the KB. No open files on the server.

Did you reboot the server(s). That is my sledgehammer fix-all

Agree with @JimWoodhead - One of my SOP's which is not followed 100% of the time is to reboot the server prior to starting the migration. Clears out many cobwebs. Did you run the Crystal OOB report that Sage developed many moons ago to see how bad the OOB's were? Also, did they have any BB JE's. another PITA from the v3.XX days?

Rebooted the server. Didnt run the crystal OOB report and yes they do have BB journal entries... source code is BB from year 1999.

You can try to run this report outside of Sage if you have Crystal Reports installed. Or just ignore it if you are sure you are in balance. Sage will let you know if you are oob when doing the actual migration.

My recommendation is to purge up 2004 or more in 3.71 prior to migration. You can copy the data to and back company if they really want to refer back to it after the conversion. That used to solve a lot of issues

The data migrates if I skip the GL OOB pre conversion... but when I run the conversion from in Sage 100 I get the following error: I am going to try and rebuild the GL detail.

Anyone remember how to start version 3.71 without installing the client?.... Don't want to mess with the 2014 version I have installed on the server.

Almost The same but change ../soa/startup.m4p to. ../soa/mas90

Thanks Jim.

@DougHiggs - Still hard at it??

Have to call Sage tomorrow.. Still can't get past the ""Object gl_levelconversion... "" error. Tried every trick I know. Hopefully I will get Ronnie Aspe or one of the other competent tech support reps.

I have run into a ""Object gl_levelconversion... "" type error in the past and it was normally caused by a blank or bad conversion level field in the MAS_System\Sy_Module.M4t file. You can check it and fix it using DFDM.

Checked sy_module and conversion level field was populated.

Issue resolved!... Called Sage and they recommended installing the latest 4.5 product updates ( I should have done this before beginning). After installing pu 7 the gl_levelconversion mysteriously went away. Thanks everyone for working weekends!