This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SEC 5.41 fresh install, DB failing to install.

I've been attempting to install 5.41 for a few days now.  I originally started out with attempting an upgrade on my 5.22 install but that resulted in more errors which caused me to end up clearing out everything that I had installed regarding Sophos and SQL on that server and start bare.  My initial issues started with a registry problem preventing me from re-installing C++ 2005 and 2008 run-time.  I've since sorted that out by doing a in-place upgrade on the server aka a repair install of Server 2008 R2.  I'm now attempting a FRESH install of SEC 5.41 and I'm getting problems every time it attempts to install the DB.  The error I get every time now is the same and I am unable to get passed this error.  I'm unfamiliar with SQL and working with it since we have no other active SQL databases here so I simply don't have the experience in it. I'm sure and I hope this is a very simple problem to solve and it's just something that i'm not familiar with so that's why I can't see the light at the end of the tunnel.

I am using the two recommended SophosManagement and SophosUpdateMgr accounts that were created for my 5.22 install when prompted for the DB users during the install.

Here is the error I receive every attempt to install it.

InstallDB (local)\SOPHOS BACKUP SOPHOS540 "C:\ProgramData\Sophos\Management Installer\Sophos_InstallCoreDB.log"
Started
Wed 02/08/2017
08:04 AM
==========
Msg 1807, Level 16, State 3, Server BACKUP\SOPHOS, Line 1
Could not obtain exclusive lock on database 'model'. Retry the operation later.
Msg 1802, Level 16, State 4, Server BACKUP\SOPHOS, Line 1
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

 

it's also happened on the security DB... not sure why it changes.

 

InstallSophosSecurityEx (local)\SOPHOS BACKUP SophosSecurity "C:\ProgramData\Sophos\Management Installer\Sophos_InstallSophosSecurityDB.log"
Started
Tue 02/07/2017
03:49 PM
==========
Creating database SophosSecurity ...
Msg 1807, Level 16, State 3, Server BACKUP\SOPHOS, Line 2
Could not obtain exclusive lock on database 'model'. Retry the operation later.
Msg 1802, Level 16, State 4, Server BACKUP\SOPHOS, Line 2
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

 

Any info would be greatly appreciated.



This thread was automatically locked due to age.
Parents Reply Children
  • I've currently stripped all SQL 2012 programs off, but yes I will be reinstalling 2012 runtime and then the management studio.  Once I have that all on there I will be poking around to see if I can find out how to do this.

     

    "Put model in RESTRICTED_USER mode, then app was able to create a new DB….which was in RESTRICTED_USER mode.  Put both DBs back into MULTI_USER mode."

     

    Since I do not know how to do this.

     

    "So we dropped and recreated the login XLOGIN\Administrator and the issue hasn’t occurred after this."

  • Once SQL Management Studio is installed I would probably connect to the Sophos SQL instance.  

    Then in a new query window execute the commands in this article:

    https://blog.sqlauthority.com/2016/05/25/sql-server-fix-error-1807-not-obtain-exclusive-lock-database-model-retry-operation-later-part-2/

    If the Kill command is successful, then you can close SQL Management Studio and retry creating the database.

  • Installed SQL express 2012 SP2 manually, installed the Management studio and then attempted this "fix"

    "Put model in RESTRICTED_USER mode, then app was able to create a new DB….which was in RESTRICTED_USER mode.  Put both DBs back into MULTI_USER mode."

    And that did not fix it or allow me to install SEC 5.4.1.

    I then attempted to run the Kill script from the link on the blog.sqlauthority.com site and I had to run this script multiple times till it came back with no result and then I was able to install SEC 5.4.1  So at this point I'm up and running.

    Query that I ran using SQL Server Sanagement Studio.

    SELECT 'KILL ' + CONVERT(varchar(10), l.request_session_id)
     FROM sys.databases d, sys.dm_tran_locks l
     WHERE d.database_id = l.resource_database_id
     AND d.name = 'model'
  • Good news!

    Thanks for the update.