Sage 100

2016 premium to 2017 premium. Same physical server, 2 SQL instances. Logged on as administrator. Using the SQL sa user for everything. The wizard cannot copy the backup files needed to continue. I copied and renamed the SQL .bak files to the folder specified in the message. The message keeps displaying. Any ideas?

Are you logging into the sql servers with domain accounts or SQL ""sa"" accounts ?

Try changing the security on the .bak files to Everyone full control. I also remember something about that location not actually being where it looks but I can't find the details - try putting the .bak files in the backup folder

I had a bizarre situation the SQL service had to be running as a user account and not the system account

I'm also working on a SQL upgrade and have the same error. I think Robert's suggestion to change user credentials on the SQL services will be worth a try. I don't have time to do that right now but will try later and report back on success/failure.

Changed the security on the bak files to everyone has full control. The SQL service and the SQL agent are running with user accounts that have admin rights. Same message.

Doug do ever schedule upgrades during the week????

Never during the week. I need the weekend to figure out issues like this. What a rcf this is. Aborting the upgrade until I get this resolved. I can't remember any other upgrade ... ever... that I have been dead in the water, until today. Thankfully this is small company that doesn't require the upgrade and they don't care if it is done this weekend or next. Still I have spent an entire weekend trying to figure this out.

@JeffFiddelman SQL sa

I've done a few of these SQL to SQL upgrades and never had a smooth migration process. This weekend's is the first in a while. I went through the usual steps, ensuring that the MAS_User is setup as the owner of the MAS_System DB on the new SQL instance and having sysadmin permissions in both SQL instances. I too have given up at this point and will talk things over with Sage Support tomorrow.

@DougHiggs - Feel you pain. Took a client from 2016 STD to 2017 Adv earlier this month. Took four tries at go live to get err done!

Wtf

@JohnKerr Please post what you find out. I will be calling first thing tomorrow morning also and will post any breakthroughs.

Very good. I will keep you posted on what I find out, although I won't be able to try the migration process till after 5:30 pm EST tomorrow at the earliest.

Just talked to Sage tech support. Below is KB 64522 that doesn't appear on the KB when I do the exact same search as the Sage rep. I will try this tonight when everyone is out of Sage 100. Error ""The wizard cannot copy the backup files needed to continue. Use SQL server Management Studio to backup the MAS_System.bak and company databases that you want to migrate."" Description ""The wizard cannot copy the backup files needed to continue. Use SQL server Management Studio to backup the MAS_System.bak and company databases that you want to migrate. Then copy the .bak files to the following location on the server where SQL Server is installed: \\(local)\C$\Program Files\Microsoft SQL Server\...\MSSQL\Data Have you copied the .BAK files? Click Yes to continue. Click No to exit the Wizard"" (local) Cause ""(local)"" used instead of ""ServerName"" when selecting Target SQL Server Instance during migration Resolution Include the (SQL) Server name when entering the Target SQL Server Instance (i.e. ServerName\InstanceName) on the 'Database Server Login'page of the Migration Wizard ID:64522 Last Modified Date:5-22-2017

Hi - One more thing to look at - if the above does not resolve - do you know if the default file locations within SQL server have been changed on the Target SQL. I am not sure that the utility that backs up, transfers, and restores is ""happy"" when the default file locations have been changed..... We have had to leave them at the original, then move the SQL server files after the transfer is complete.... (and update the default locations when done). Good Luck

Was there ever a resolution to this? I'm running into it on a 2018 Premium to 2020 Premium.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

For my specific issue I found: 

- Couldn't access the SQL server using \\servername\
- IT could not ping by SERVER or IP
- IT could RDP to server
- IT logged into SQL server and updated firewall
- Found that File and Print Sharing (SMB-In) rule for Domain Profile connections is disabled. Enabled that firewall rule.

Will retest later tonight

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Hi Wayne,
Any luck yet?

https://community.90minds.com/communities/community-home/digestviewer/viewthread?GroupId=13&MessageKey=60a5f44e-b160-42d3-a040-5df1967bee25&CommunityKey=4593d843-4557-43ff-ba4d-6240681ed696&tab=digestviewer&ReturnUrl=%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3d4593d843-4557-43ff-ba4d-6240681ed696%26tab%3ddigestviewer

------------------------------
Cesar Varela
Blytheco LLC
------------------------------

Original Message:
Sent: 07-15-2020 11:58
From: Wayne Schulz
Subject: 2016 premium to 2017 premium. Same physical serve

For my specific issue I found:

- Couldn't access the SQL server using \\servername\
- IT could not ping by SERVER or IP
- IT could RDP to server
- IT logged into SQL server and updated firewall
- Found that File and Print Sharing (SMB-In) rule for Domain Profile connections is disabled. Enabled that firewall rule.

Will retest later tonight

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Yes- it turned out that we needed to activate something on the SQL box so that from another server I could \\servername\share connect to that SQL box. 

Here are the notes from the IT tech

Tried to ping and navigate to the server, but am unable to.
~ Was able to RDP from the new application server to the new SQL server (SQL16-2020) successfully.
~ Checked the Firewall settings and found that File and Print Sharing (SMB-In) rule for Domain Profile connections is disabled. Enabled the that firewall rule.
~ Was able to navigate to the server via File Explorere successfully.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Original Message:
Sent: 07-18-2020 03:56
From: Cesar Varela
Subject: 2016 premium to 2017 premium. Same physical serve

Hi Wayne,
Any luck yet?

https://community.90minds.com/communities/community-home/digestviewer/viewthread?GroupId=13&MessageKey=60a5f44e-b160-42d3-a040-5df1967bee25&CommunityKey=4593d843-4557-43ff-ba4d-6240681ed696&tab=digestviewer&ReturnUrl=%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3d4593d843-4557-43ff-ba4d-6240681ed696%26tab%3ddigestviewer

------------------------------
Cesar Varela
Blytheco LLC
------------------------------


Original Message:
Sent: 07-15-2020 11:58
From: Wayne Schulz
Subject: 2016 premium to 2017 premium. Same physical serve

For my specific issue I found:

- Couldn't access the SQL server using \\servername\
- IT could not ping by SERVER or IP
- IT could RDP to server
- IT logged into SQL server and updated firewall
- Found that File and Print Sharing (SMB-In) rule for Domain Profile connections is disabled. Enabled that firewall rule.

Will retest later tonight

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Original Message:
Sent: 7/21/2020 11:35:00 AM
From: Wayne Schulz
Subject: RE: 2016 premium to 2017 premium. Same physical serve

Yes- it turned out that we needed to activate something on the SQL box so that from another server I could \\servername\share connect to that SQL box. 

Here are the notes from the IT tech

Tried to ping and navigate to the server, but am unable to.
~ Was able to RDP from the new application server to the new SQL server (SQL16-2020) successfully.
~ Checked the Firewall settings and found that File and Print Sharing (SMB-In) rule for Domain Profile connections is disabled. Enabled the that firewall rule.
~ Was able to navigate to the server via File Explorere successfully.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------


Original Message:
Sent: 07-18-2020 03:56
From: Cesar Varela
Subject: 2016 premium to 2017 premium. Same physical serve

Hi Wayne,
Any luck yet?

https://community.90minds.com/communities/community-home/digestviewer/viewthread?GroupId=13&MessageKey=60a5f44e-b160-42d3-a040-5df1967bee25&CommunityKey=4593d843-4557-43ff-ba4d-6240681ed696&tab=digestviewer&ReturnUrl=%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3d4593d843-4557-43ff-ba4d-6240681ed696%26tab%3ddigestviewer

------------------------------
Cesar Varela
Blytheco LLC
------------------------------