Sage 100

v2017 Std (pu1) migration from v2013 - WIN SBS 2011 Standard server - xCopyFile returned the following error - Access is denied. Simple migration. Financial modules. Getting this message while migrating. Click ok, processes, get error. Finally finishes. Try to convert companies. They convert but version no. does not change in company maintenance. Only thing on KB is attached. AV has been removed. Logged on as Administrator. No indication as to which file is denied. Have rebooted server. Same results when I remigrate. Grasping at straws. A few xcopyfile threads in history. Thoughts??

I searched 90Minds and saw several posts on this, a couple of which were posted by you :) Do a search to find suggestions. I saw that in some cases people did the conversion on different computers. Others just manually copied the company data files from the old version to the new install. It looks like you rebooted the server and logged in as Admin to resolve the problem once. Others point to apparent permission issues.

Last part of the attached may help with the version info

@MaryJoKrueger - Amazing how some issues just come back long after you have forgotten about them. Yep, I did post some of them. All were resolved by the software gods, I had no clue how they just one day worked. Administrator login, no AV, reboot, still have issues. Go figure.

Can you move the error window to see what it's trying to copy?

@MoiraGoggin I think the conversion issues are a part of the xcopyfile issues.

@MaryJoKrueger - Hadn't thought of that. Will give it a try.

Just trying to be helpful @JeffSchwenk

@MoiraGoggin Any and all comments are appreciated. The xcopyfile error pops up at different times during the migration process. I think I tried it four times. Trying to do an install on a local workstation after moving the files from the server.

Have you ever used ycopy? The guy that builds my PCs always puts on the system. Better messages on why a file won't copy and after the routine runs I can save the job log results to a csv file. Much easier to find what copied and what didn't.

Process Monitor (Procmon) is a good tool for seeing Access Denied errors for file or registry objects. You run the trace only during the Migration and stop it (when you get the error. Prior to or after running you can have it filter for Migrate.exe, pvxwin32.exe, Launch32.exe (CTRL-L). Then export results to tab delimited and open in Excel. Then sort by the Result column if I remember correctly. The ACCESS DENIED entries will float to the top and you'll see the file it's blowing up on. You can have that cantankerous Boris fellow run it after he stops whining about it - https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

@AlnoorCassim - We should have done vodka shots with Boris last year in Chicago!!!!! I am not inclined to mess with server setting/programs, etc when installing Sage. I let that to the cantankerous IT people (Boris or not) to do. I don't like them messing with Sage so I don't mess with their software. What I ended up doing as a workaround was to copy the 2017 and the 2013 folders from the server to a workstation. Installed the 2017 client, launched Sage and ran the migration tool from the workstation on the Sage local install. Migration ran without a hitch. Now converting data locally (about 40 companies). So far so good. Once done, I will copy the MAS90 folder back to the server and attempt to access it from there. FWIW, I think there is something amiss with this server. I am logged in as the Administrator but weird is happening.

I'm glad that I found this post. I'm at a customer site where I'm upgrading them from 2016 to 2018, and got this exact error when trying to migrate. Had the IT guy turn off all kinds of stuff, but no joy. So I copied their 2016 and 2018 folders to my laptop and ran migration. That worked. Copied 2018 back to their server. Works!