Sage 100

I am trying to migrate data on a Sage 100 advanced upgrade and I continue to get a message that the migration wizard has detected a process running on the target installation. However, the application server service is stopped and all users are out. We have stopped all back-ups and anti-virus as well but still receiving the message. The server we are migrating from is running on Server 2000. Does anyone know of any other service or program that Sage may see as a conflict in this migration process?

Depending on the version you are upgrading from, is there an Integration Engine service running? Have you tried rebooting the source server?

No integration engine and yes we have rebooted the source server, still to no avail.

We are upgrading from 4.10

Somebody have FRx open? If a local install, not sure a reboot would close the pvxwin32 on the workstation.

Nancy, good thought, but they are not using FRx

shawn, open the server manager and look at your open files on your shares. close any pvxwin32.exe files listed as open. If you need help private message me and I can give you my cell and try to help. I've run into this before.

Any pvxwin32.exe's in Windows Task Manager? If so, kill 'em. I get the sense this is a server migration, therefore be sure to check all this same stuff on both servers (incl that the Application Server is closed, Application Server Service is stopped, Integration Engine (Sage CRM) is stopped) - and reboot new server.

Is the ProvideX IO service running? Also, any programs using ODBC such as Valogix, Alerts & Workflows, Access, SQL etc can cause this.

My bet is pvxwin32 running on the server. I like to use procss explorer from sysinternals to find all the processes. The tree view makes it eazy to see orphaned tasks. You can also hover to see the path to the exe. This makes it easier when running multiple apps that use pvx.

All pvxwin32 processes killed on both servers and rebooted, no ProvideX IO, Application Server, or Integration Engine services running on either server. All open files on shares have been closed. Still no dice. Appreciate all the suggestions...but the IT manager and I are calling it a day and starting over tomorrow. If anyone thinks of anything else to check, your suggestions are most welcome.

Instead of selecting Parallel Migration Wizard from within the new version of Mas (and maybe you didnt do it that way) have you tried directly running Migration.exe (or is it Migrate.exe) via rt-click / Run as Administrator from Windows Explorer? It Is under the /mas90/Migration folder. Also you may want to consider just copying the whole /mas90 folder from the 2000 server to the new one and then run Migration again pointing the Souce to the copied folder on the new server (instead of the 2000 Server). I know that seems nonsensical given the error is about the target but I've had so many adventures with Migration bonking with useless unrelated to the problem errors.

Thanks Alnoor. I will give that a try.

There was a bug at one time where you had to start the migration wizard from outside the MAS Shell by launching it directly from the executable.

Yep, I tried launching the executable and still ran into an issue. So I am going to try Alnoor's idea of copying the MAS90 folder to the new server and migrating from their this evening. Thanks everyone for your ideas...they are much appreciated.

All just wanted to keep you updated. We tried migrating with a copy of the MAS90 directory on the new server still with no success. In addition, we cleared the LOCK folder in the MAS90 directory, and tried renaming the SY_Console and SY_Workstation file, still with no success. If anyone has any additional ideas, they would be most welcome.

Do you have any ghost users visable in the Master Console in the source system?

You could try installing MAS to a laptop or workstation and also copying the source programs and data to your laptop or workstation. See if you can run the migration. If successful the copy the data to the server.

@Dan, no ghost users are visible.. @Doug, thanks will try that.

Did you check file permissions on the mas90 folder and confirm it is set to all subfolders/files?

Wonder if your new install is corrupt. Have you tried removing it and reinstalling? I would still be inclined to at least start any migrating with a local copy of the old system.

I'm running into this same thing with a v4.5 to v2013 migration. What I'm trying to do is migrate from a copied version of their full MAS system (which is the only way I can have exclusive access to the data since people are in almost 24 hours a day). I'm doing this on the server that is also running the live copy of MAS200 though I'm not the account running the host. I wonder if something is conflicting there.

Solution: Found Application Server was sitting on task bar. Don't think it was still running but closed it and the conversion kicked off (I used the right click on migrate - run as administrator)

Wanted to update everyone as to the resolution to this issue. We ended up having to install 4.10 on their new server, copy the company data folders into the new installation as well as the MAS_SYSTEM folder. We were finally then able to migrate the data.