Sage 100

3.71 to 4.5.4.0 upgrade. Migrated 3 companies. In all 3 cases, GL didn't convert beyond 4.05 (when look at Company Maintenance). Also, the conversion on one company halted when it couldn't create CI_MiscItemHistoryByPeriodWrk. Permission denied. Activity log shows 2 Error 108's at the beginning of the migration process after lines in the activity log indicating ""files created for module SYS"" and ""data files updated for system."" Error 108 SY_LEVELCONVERSION 01917 followed by Error 108 SY_LEVELCONVERSION 01862. Anyone seen any of this?

Did you run the pre-migration utilities for 3.x? I'm thinking they were mostly for GL...

Yes, rebuilt data files on them, too.

Couldn't find these error 108s in either Sage KB.

You might try a two step upgrade process - 3.71-4.00, then 4.00 to 4.50.

Yeah, me either... Any enhancements/customizations?

Does /MAS_SYSTEM/SystemConversionLog.txt show anything of interest?

@ThereseLogeais, I don't think so. Although I found a folder in their MAS90 folder labeled SP and SPSetup. @BillPfahnl, hmm. 4.00 huh? Why that one? @WayneSchulz, the only thing that looks wonky is this - the last one in the log file: Error emptying directory 'M:\MAS45\MAS90\soa\SOATEMP\': ERASE_ERR

Thanks for your help folks. I'm going to call it a night and pick this up in the morning. But keep those cards & letters coming!

For the Error 108 Line 1917 error this version of Sy_LevelConversion.pvc attached will place the name of the data file in play into the Windows clipboard. In other words, run the Migration again, say Yes to convert system files. When it's complete, open Notepad and do an Edit / Paste (Ctrl-V). It should give you the culprit file.

Thanks @AlnoorCassim , I'll try that and report back.

You know I remember seeing something like this a long time ago and one of these 3 logs had the problem file listed in it: SystemConversionLog.txt ( in \MAS_SYSTEM) Migration.Log (in \Migartion) Migration.Txt (in \Migartion) Check there first

Barbara, We have had a few strange conversion issues as well, coming from 3.71 what we have seen is in one of the modules options file there was a record that was not correct. So the last on we had which stopped at the GL conversion and CI, we found in comparing a company that converted that AP_options had three records, the company that did not convert had a fourth record, we delete the fourth record in 3.71, migrated and converted.

A few updates (haven't had a chance to remigrate yet): I'm 99% sure I only selected 3 companies to migrate, but in 4.5, there is a company record for a 4th company (but no data was migrated). They have many company codes, by the way. Some of them use alternate directories, but not the ones I migrated. The 4th company uses alternate directories for all modules except IM(?). The company on which I got the CI_MiscItemHistorybyPeriodWrk error - the file DID get created in the MAS_Company folder. Weird.