This can also happen when you add a new integration to a new data mart database using the configuration console for Microsoft Management Reporter 2012. The creation of the data mart database fails.
When this happens, check the deployment log at C:\ProgramData\Microsoft Dynamics ERP\Management Reporter\Logs\Deployment-Date_Time.log. The following error message will be displayed in the log file:
There are other applications that may keep a lock on the model database.
'Session ID' = sp.spid
,'Database Name' = db.name
,HostName = sp.hostname
,'Program Name' = sp.program_name
,'Login Name' = sp.loginame
,'Task Manager PID' = sp.hostprocess
,Status = sp.status from sys.sysprocesses sp
join sys.databases db on db.database_id = sp.dbid
where db.name = 'model'
With the results of the above query, review the HostName column using the steps below.
- Log onto the server in the hostname results and open Task Manager.
- Add the PID column in the Processes view.
- Server 2012: Right-click the Name column header and then select PID.
- Server 2008: Click View, click Select Columns... and then select PID.
Compare the Task Manager PID results from the above query with the PID in Task Manager to gain additional information on the process.
Depending on the application running the process, stop the related service or close the program which is holding a lock on the model database.
For example, if the process holding a lock is stemming from SQL Management Studio, close the query window where the Model database is selected.
If the process holding the lock is stemming from an application, go to services on the server and stop the service for that application.