Sage 100

Updated:  I figured out the obvious - can't just swap out MAS90 directories (overwrote my directories anyway and didn't back up the sql dbs), but is there any way to pull the VI jobs from my backup copy of MAS90 and put into the live?

HI

2019 Premium:  Doing an upgrade, made a copy of existing MAS90 directory before remigrating.  Realized after I migrated system files, etc. that I didn't export the VI jobs from the copy.  After converting, I turned off the service, tried to rename the live version and put back the copy version and started the service.  I'm getting a 'SQL is not enabled'.

So couple of questions:

1. is there a way to run a Premium install in MAS90 mode?  I tried on my copy directory and get the SQL is not enabled.

2. is there a way to resolve this SQL is not enabled

3.  any other way to extract the VI jobs from the copy and put into live?

Thanks

N

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------

SQL is not enabled means that MAS_User cannot read the SQL databases. Here's the code you can run in SQL Server Management Studio to fix those permissions (change USE MAS_XXX to match your database names):

--
--­­ Run for every MAS_XXX database, including MAS_SYSTEM after a restore
-- 
USE MAS_XXX 
GO
exec sp_dropuser 'MAS_User'
exec sp_grantdbaccess 'MAS_User'
exec sp_addrolemember 'db_owner', 'MAS_User'

Below is a screenshot of the steps to set up Premium MAS90 mode.  That should get you in, and then you can export/import the V/I jobs.

Thank you Steve, 

----­­ Run for every MAS_XXX database, including MAS_SYSTEM after a restore-- USE MAS_XXX GOexec sp_dropuser 'MAS_User'exec sp_grantdbaccess 'MAS_User'exec sp_addrolemember 'db_owner', 'MAS_User'

A bit late to the discussion but... always back up MAS_System and MAS90 from both target and source systems for any Premium migration (when you have the disk space).  This can save many headaches if you need to reset and restart.

----­­ Run for every MAS_XXX database, including MAS_SYSTEM after a restore-- USE MAS_XXX GOexec sp_dropuser 'MAS_User'exec sp_grantdbaccess 'MAS_User'exec sp_addrolemember 'db_owner', 'MAS_User'