On the new SQL Server:
1. Create MAS_User in Security / Logins and assign these server roles:
db_creator
public
2. Create MAS_Reports in Security / Logins and assign these server roles:
public
And now the part that is prolly causing the error:
3. Run this T-Sql below for EVERY MAS_ database including MAS_SYSTEM
Copy / paste this below into SQL Mgmt Studio.
Login to SQL Mgmt Studio sa' or a trusted login that is a sysadmin
/*
-- START
-- Click database dropdown in SQL Mgmt Studio to change databases
-- Be sure to run for EVERY MAS_ database including MAS_SYSTEM
exec sp_dropuser 'MAS_User'
exec sp_grantdbaccess 'MAS_User'
exec sp_addrolemember 'db_owner', 'MAS_User'
exec sp_dropuser 'MAS_Reports'
exec sp_grantdbaccess 'MAS_Reports'
exec sp_addrolemember 'db_datareader', 'MAS_Reports'
-- FINISH
*/
4. Finally reset the passwords of both MAS_User and MAS_Reports through the MAS SQL Settings Utility so both massql.settings file and SQL Server is updated.