Sage 100

SQL Guru;s Sage 100 2014 SQL Premium installation issue. I am trying to install a new sysyem and we are receiving a create fail for Database MAS_SYSTEM .and that DB Model doesn't allow exclusive rights. This error is similar to attached. Note: I am logged in as SA and I have recently restarted the SQL server. @Sage100UrgentSupportNeeded

Have you looked at this? http://blogs.msdn.com/b/poojakamath/archive/2014/12/24/could-not-obtain-exclusive-lock-on-database-model-retry-the-operation-later-create-database-failed.aspx

I find article by Pinal Dave to be very helpful. http://blog.sqlauthority.com/2010/01/01/sql-server-fix-error-1807-could-not-obtain-exclusive-lock-on-database-model-retry-the-operation-later/

Actually I found this solution too. Solution: Solution 1: Disconnect and Reconnect your SQL Server Management Studio's session. Your error will go away. Solution 2: Root Cause: Root cause of this error may be one of the following reason 1. Somebody exclusively open the Model database in different session 2. If more than one create database statements attempt to run simultaneously

Thanks all~~

related to the solution Jim found, When I find SQL Server acting strange like this, cycling the Service has helped; in this case it would remove any hanging logins. For future consideration.

Still researching . This is that error I am receiving.

I've been meaning to write this up for the Sage 100 Routine group but just haven't found the time. Here's what I've found with 2 Premium to Premium upgrades I've done to the 2015 version (1 was from 4.50 and the other 2013). I create a case with Sage so at least one of their Analysts knows about this (Dan Riddle, nice guy and pretty sharp). I'm not sure if this is exactly what you're seeing, but it might be. I'm assuming when you say you have a ""Sage 100 2014 SQL Premium installation issue"" you are migrating from 2014 Premium to 2015 Premium. If not then disregard the rest of this :-) What is happening is that the 2015 Migration tool is looking on the old SQL server and making backups of the MAS_SYSTEM and MAS_XXX DBs. I'm assuming it does that successfully but haven't verified. Then it is trying to restore those .bak files into the new SQL server so it can use them to migrate the data and populate the new DBs. Unfortunately it doesn't seem to know where to look. It looks in the default path for the Databases in the new SQL Server. The bottom line here is that to resolve I had to: 1. Make MAS_SYSTEM.bak and MAS_XXX.bak files from the source SQL Server (right click - tasks - backup). 2. Copy those into the default path for your target SQL Server (in my case it was C:\Program Files\Microsoft SQL Server\MSSQL11\MSSQL\DATA) 3. Run the migration utility

Are you running the service under a domain admin account or under the local service account? I strongly recommend the domain account.

@JimWoodhead Reboot!! Then install.

Got it working. 2 things were needed. 1st) I had to remove all the reminants of the failed install (MAS_System DB , mas_user & mas_reports accounts) 2) rebooting APP and SQL server. Thanks all

I've worked with SQL for a long time. It still always seems like some witchcraft is needed to get a new one going.

Well done Jim. Thanks for the update.

All of this is good to know as I am starting an upgrade to Sage Premium next week.