Sage 100

I'm trying to do a parallel migration 4.5 and I get the error sy0ctl.soa at the ""from"" location is in use by another task and cannot be opened. I don't believe it is being used so I changed the file name to _sy0ctl.soa and I still got the same message.

Is this Sage 100 Standard or Advanced (formerly known as MAS 90 or 200)?

Any PVXWIN32.exe processes running in the task manager? If so, kill them. If not, try rebooting the server. Rebooting the server is on my checklist of task to perform before starting the conversion. Cleans out the cobwebs...........

Check out permissions and security setting for the source directory. You might also rebuild the system files in the source location. What version are you coming from?

Did you shut down the service (as it may be set to auto start on a reboot)?

this is advanced (200). Customer bought a new server migrating 4.5 to 4.5. Rebooted the old server checked for any pvx processes.

yes, but the weird part, the way I see it, is if I changed the name of the file how could the original file still be used by another task if it doesn't exist anymore?

Sounds like a file lock somewhere. Reboot is best way to clear it after changing the service to manual.

In case it wasn't assumed, powering down is what I recommend vs. reboot. I also seem to recall at some point in the past, I may have had to delete some records from the sy0ctl via dfdm, for a hung record showing in Master Console.

Hmm. Can't power down because I am working remotely. But I will look at the file and see if I see anything weird. Thanks

So you are just changing servers? What kind of parallel migration are you doing. I think Wayne posted how to move servers on the 90Minds web site. Is the new servver's name different than the old?

yes different name. the old server will be used for other things

I would try copying the entire MAS90 folder from the old server to the new server, then do the migration all on the new server.

We usually do what Gene suggested, especially if there is some kind of network storage device involved. Fortunately, the install you are migrating from does not need to be registered in Windows.

Have a customer who is on 4.1 standard who had to restore from a backup due to a virus. Now only one user can get in the system. When a second user tries, they get the error message sy0ctl.soa is in use by another task. Master console only shows the one user. Thoughts? Suggestions?

Any chance this could be an aggressive AV?

Turns out they had to restore two virtual Citrix servers that everyone accesses for Sage and they never reran the workstation setups on them nor did they reboot the MAS server. Did both of those and so far, all is well.