Sage 100

Premium v15 to v17 unable to migrate data. Can see both SQL instances in SQL Mgmt studio, can login with either ""sa"" or windows authentication in SQL Server Mgmt Studio. Get past the company code list to begin migration and if we use the ""sa"" credentials in wizard we get ""Unhandled Exception Error Number: 0x80040E14 Description: Cannot open backup device, refers to path for new SQL instance MAS_SYSTEM.BAK. Operating system error 1326(The username or password is incorrect.). Setup will now terminate. If we use windows authentication we get ""Unhandled Exception Error Number: 0x80040E4D Description: Invalid authorization specification. Setup will now terminate."" Sages only article on this is for the win. authentication error which says to use the SQL ""sa"", brilliant. Sages idea is to move both SQL instances to the application server, migrate data, then move SQL for v17 back to it's original home and re-point the Sage 100 v17 at that new / final location. This seems like a lot of extra work that really should not be needed - does anyone have advise on this.

Configure the source SQL service to start using a domain admin login, and use the SA account to connect to source during the migration.

Thanks for the suggestion, we have tried that and its not working either. The Sage migration program needs an overhaul...were thinking of installing SQL on same box to see if that helps, if it does we will have to move back where it belongs later.

Hi - did you by any chance change the default locations of the SQL data, log, and/or backup files on the SQL server for version 2017 ?