Sage 100

Active Users - The migration wizard has detected a process currently running in the source Sage 100 ERP installation.... Trying to to do final migration from 3.71 to 5.0. Have rebooted 3.71 server, rebooted the 5.0 server. Host is definitely shut down on both, Integration engine disabled, running migrate from back end \mas90\migration, not sure what else to try - have to get this data migrated tonight and the stars seem to be aligned against us. We do get an interesting pop at the beginning of the migration, after selecting the source folder - Open File Security warning are you sure you want to run this file (pvxwin32.exe file in Home folder of 3.71) - I can say Run or Cancel and have tried both and either way we end up with the migration detecting a process running in Source installation. Any ideas?

Eric, I had a similar issue. I was doing a migration/server move and change from Standard to Advance. We had a Terminal Server which the IT person had to kill sessions which had MAS files open even though we rebooted the server. Look for open files

Do you have any programs other than Sage 100 that connect via ODBC or OLEDB to the Sage 100 tables? Access, Starship, Valogix, Knowledgesync, SQL Server, etc?

Does the 3.71 install have any unattended processes that run? I had a similar issue with an EDI listener.

Copy the install to another server/computer and try it from there make sure the lck files are deleted

nothing at all running or automated, going to try the suggestion from Nicholas - copy to the new server and delete LCK files

I once had a problem running migration from a mapped drive and wouldn't work right until I ran it manually from the server itself. Good idea to delete LCK files.

Try running from the Migration folder, Migrate.exe, instead of from within 2013.

Have you tried converting to 4.2 and then to 5.0?

well - moved everything over to the new server, deleted the LCK files in the 5.0 install, can't find any LCK files in the 3.71 folder, tried the migration again pointing to the local 3.71 files and get the same message. Going to reboot the 5.0 server, try one more time, and then call it a night. I don't really want to go through a separate upgrade to 4.2 because we've already successfully migrated and converted the data straight from 3.71 to 5.0. Thanks everyone for the responses on a Saturday night!

Since you have migrated once which I assumed was to go to into test why not just copy the company data folders and convert?

will that work straight from 3.71 - I was thinking about that. Can I just copy the ap_xxx, br_xxx, etc. - into the MAS_xxx folder in 5.0 and convert?

Great question. I did not think about that. I would assume you would have to make a company folder and copy the data over by selecting each data folder by module. Might be worth a try.

reboot didn't work so I'm going to give it a shot Ron, it can't hurt anything at this point

As you try this remember the CI data is already created and is at level 5.0 which may cause so issue so keep this in mind. Good luck.

Guys, I gave you the answer. Don't make it so hard. Or maybe I am wrong. Resolution Details TITLE : Task is in use when launching the migration wizard DETAILS : INFORMATIONAL ** THIS INFORMATION HAS NOT BEEN VERIFIED ** Task is in use when launching the migration wizard Entry Type: Informational Product: Sage MAS 90 ERP Sage MAS 200 ERP Application: Library Master Version Reported: 4.20 Subject: Task is in use when launching the migration wizard Possible Resolution: 1.Exit all user's from MAS 90 / MAS 200 2.Open windows explorer 3.Navigate to MAS90\Migration folder 4.double select migrate.exe from the migration folder to launch the migration wizard

Eric said he was doing this in the original post

yes, all of that was checked and double-checked, and then triple checked:) - and we've been running migrate.exe from the migration folder the last 20 attempts. Converting the data now - I'll let you know if it is successful.

Crud. If I could comprehend what I read, sometimes it would be easier. I have had success with Ron's method as well.

no problem Gene - I appreciate the advice and help - getting this type of response on a Saturday is incredible! It's on the I/M conversion now, this might take a while.

To answer the question whether you can just move the data from v3.71 to v2013 folder and convert, the answer is yes. I have done it twice now without issue. My reasoning is that why move all the crap (crystal, report tables, VI's etc) that you just have to delete anyway. The only thing of value might be the users but you have to modify security anyway, so why not start fresh. The only gotcha that may be an issue is if you have UDF's. But in Eric's situation, he had already performed the migration once so the data dictionaries reflected the UDF's. I wonder if you can rebuild the data dictionaries to reflect the UDF tables somehow. I create the data folders first in v5.0, then rename them. Then copy/paste the v3.71 APxxx, ARxxx, etc in place. Of course, get rid of the crap tables (tmp, old, etc) prior to the conversions. For vanilla installs, go for it.

the 3.71 data successfully converted to 5.0 last night after the manual copy paste move, thanks everyone for the suggestions!

I had the same thing happen last week Eric and that was the same solution I did.

For future searchers this is a decent summary of some alternate areas where Sage could think there's a lock in place: Resolution Details TITLE : ""This task is in use"" when running the Parallel Migration in Sage MAS 90 and MAS 200 4.40 DETAILS : INFORMATIONAL ** THIS INFORMATION HAS NOT BEEN VERIFIED ** ""This task is in use"" when running the Parallel Migration in Sage MAS 90 and MAS 200 4.40 Entry Type: Informational Product: Sage MAS 90 ERP Sage MAS 200 ERP Application: Accounts Payable Version Reported: 4.40 Subject: ""This task is in use"" when running the Parallel Migration in Sage MAS 90 and MAS 200 4.40 Possible Resolution: Ensure that all users are out of MAS90 and no pvxwin32.exe, massetup.exe, or pvxcom.exe processes show up in Task Manager on the Server On the Server go to Computer Management / Shared Folders / Open Files and ensure nothing from the MAS90 folder is locked (you can get here in Windows by Right Clicking on ""My Computer"" and selecting ""Manage"") Stop the MAS200 Application Server service on the Server (for MAS200 installs only) If the issue persists, try the migration from a workstation. If the migration is being performed from a workstation, try it from the server. http://infosource.sagesoftwareonline.com/infasp/kdb.asp?isresolutionconceptid=523129