Summary
Cause
Access Denied 5 is linked to the Accounts starting the SQL Server (Instance Name) in Windows Services as the Default accounts assigned from SQL Server installation process are denied access from SQL Server
Access Denied 2 Database Files were unable to be created in the Microsoft SQL Server\MSSQL##.InstanceName\MSSQL\DATA directory do to lack of access to private Admin shares on the source or destination locations. i.e. \\server\c$, \\server\d$ etc.
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; font-family: " segoe="" ui",="" "helvetica="" neue",="" "apple="" color="" emoji",="" "segoe="" ui="" helvetica,="" arial,="" sans-serif;="" font-size:="" 14px;="" font-style:="" normal;="" font-weight:="" 400;="" word-spacing:="" 0px;="" white-space:="" box-sizing:="" border-box;="" orphans:="" 2;="" widows:="" font-variant-ligatures:="" font-variant-caps:="" normal;"="">SQL Server Service of the new installation is running with the SQL_Instance Network account instead of the Local System AccountResolution
See Related Resources for resolution "How to upgrade to Sage 100 Premium 2015 or higher"
Steps to duplicate
During Parallel Migration where Sage 100 Premium is on one server and SQL Server is on a different server.
Multiple messages occur ending in “Error Number : 0x80040e14 Description: Cannot open backup device D:\Program Files\Microsoft SQL Server\.....\MAS_SYSTEM.bak. Operating system error 2(The system cannot find the file specified). Setup will now terminate.”
1.Install Sage 100 Premium 2013 – 2015 on Server A
2.Install Sage 100 2016 Prem on Server A, When prompted for SQL Server location point to Server B SQL Instance
3.Default or Name Instance will both end with the same results
4.Begin Parallel Migration
5.First Message occurs
6.“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 \\Server B\C$\Program files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA” Have you copied the .BAK files? Click Yes to Continue” NOTE: The path shown above may vary when using a named instance or defining the SQL path as it uses reference to version of SQL Server on Server
7.Create necessary path on SQL Server Server B and set up share to create UNC path needed
8.Copy in .BAK files from source for MAS_System.back and MAS_XXX company codes where XXX represents company codes being migrated
9.Click on Yes to continue with Parallel Migration
10.Second Message occurs
11.“A MAS_System.bak file already exists in the location \\Server B\C$\Program files\Microsoft SQL Server\MSSQL\MSSQLSERVER\MSSQL\DATA folder. The wizard must overwrite this file to continue with the migration. Do you want to continue?
12.Click on Yes
13.Go to that path and a .tmp file is created which will replace the current MAS_System.bak. The new .bak file created is considerably smaller in size
14.Continue Parallel Migration
15.Error Message occurs
16. “Error Number : 0x80040e14 Description: Cannot open backup device D:\Program Files\Microsoft SQL Server\.....\MAS_SYSTEM.bak. Operating system error 2(The system cannot find the file specified). Setup will now terminate.”
17.This path it wants is on Server A where Sage 100 Premium is installed but not where SQL Server is installed. The error message points now to a local drive instead of the UNC path coming from the SQL Server
18.Create the path wanted on the Server A and copy the MAS_System.bak and company .bak files in
19.Run the Parallel Migration again
20.When the MAS_System.bak file is recreated in step 13 it only replaces the MAS_System.bak file on Server B but it did not touch the one on Server A
21.With all error paths created it still results in the Error Message in Step 16
22.This issue will just loop over and over again and the Parallel Migration will never be successful.