Sage 100

In the process of a final migration for a Sage 100 v440 to 2016 PU2. I'm getting a ""The migration wizard has detected a process current running in the source Sage 100 Installation ... "" And, boom, dead in the water. On server I'm migrating from: a. Sage Service shut down b. No integration engine c. No CRM d. There is no PVXWIN32 running in task manager on server e. Checked the Keys for source - Migrate_Activate.pvx - nothing f. Run Migration as admin standalone from the server I'm migrating to g. No users are logged in per console h. No open files per Computer Management Not quite sure what else to check short of a server reboot which when it comes back up is going to tell me someone is in the system because more than likely a boatload of services automatically re-start

Hi Wayne - how about trying copying the entire mas90 folder from the old server to a temp folder on the new server and converting it from there ..... Have done this before for other reasons....

That's what I'm about to start doing

During the copy activate.pvx comes up as in use but I don't see any network shares to it in computer management. Makes me think they have some other third party solution which is still connecting that I am unaware of.

Ideally, I'd like to just drag MAS_xxx and reconvert but if the customers has paperless of links to attached documents you screw up their ability to view documents added during the testing phase. It would be awful nice if Sage architecture re-imagined the way customers move servers and make it easier to copy those bolt-on attachments. Relink works ok (sometimes) but I think it depends on the linked file locations already being in a Sage system file and if you drag/drop MAS_xxx those Sage system files won't come along.

Agreed, but we all have to work around these type of things - you can skip the activate.pvx and regenerate it in the copy using the batch file, etc.... are you able to continue your conversion ?

Do you know if they have any 3rd party apps, e.g. EDI, KnowledgeSync, Scanco, or CRM? Those are sometimes culprits.

Unfortunately after the copy job I still get the ""migration wizard has detected a process

To get Activate.pvx when locked, copy and paste to the same folder. Then move and rename the copy.

Looks like the second issue on the ""migration wizard"" was complaining about the target server -- shutting down the apps server on that appeared to work.

After the move, open the copy by the back door, check the master console then log out. I had this happen during a test migration a couple days ago, and taking a fresh copy worked for me.

I have renamed the InstLock file to old that is under the Migration folder and then started the Migration over. The Migration then worked.

I have experienced this problem. Look for any ""folder"" that is not native Sage 100; then remove those folders. I usually have to check each individual folder under the ..\\MAS90\ folder, on the system. You can put them back after the migration is completed.