Jump to content

HELP ! - Failed SIMS patch now SQL in Single user mode


Recommended Posts

Posted

Hi

 

I think a patch done out of hours by my support company has failed and keft the SQL DB in single user mode.

 

In SOLUS 3 it says tolerance not met for target SIMS database, deployment stopping (looks like for nearly an hour)

 

Does the Database roll back in time and return the DB to mutli user mode, or if not can I run a command manually in SQL studio to do this, for morning registration?

 

Can't get hold of said company out of hours, so want to avoid early morning registration panic!

 

Thanks as always!

Posted

I will wait a bit longer, I think I could either run the ALTER DATABASE command or go into the SIMS DB properties and drop it down to Mutli User under 'Restricted Access'

 

Lets wait for the rollback complete before I try it!

Posted
Sometimes it helps to cycle the SOLUS deployment service on and off (big button in the deployment centre, top right) to kick it back into life. I patched ours today - hope it hasn’t done the same!
  • Thanks 1
Posted

I had this issue with a failed update before

 

I opened the SQL Server Management Studio, expanded Databases and right clicked on the sims database and selected properties

 

On the left select Options and then next to Restrict Access change it from Single to MULTI-USER

 

I then re ran the update from Solus and it completed OK

  • Thanks 1
Posted (edited)

From my old notes, usual caveats apply:

 

Problem: Database Stuck in Single-User Mode

 

In SQL Manager, run this query, inserting the correct database name.

 

set deadlock_priority high
alter database NAME-OF-DB set offline with rollback immediate;
alter database NAME-OF-DB set multi_user with rollback immediate;
alter database NAME-OF-DB set online with rollback immediate;

 

 

If it's being held open by connections, kill the connections with this query:

 

USE master
GO
DECLARE @kill varchar(8000) = '';
SELECT @kill = @kill + 'kill ' + CONVERT(varchar(5), spid) + ';'
FROM master..sysprocesses 
WHERE dbid = db_id('INSERT-NAME-OF-DB-HERE')
EXEC(@kill);

 

Then try the first query.

Edited by jinnantonnixx
  • Thanks 1
Posted

Thanks guys, you are awesome!

 

I ended up waiting a few hours last night and flipped SIMS SQL to Mutli useer mode in SQL Studio :)

 

all ok for the morning!

Posted
Thanks guys, you are awesome!

 

I ended up waiting a few hours last night and flipped SIMS SQL to Mutli useer mode in SQL Studio :)

 

all ok for the morning!

 

The second 'kill connection' script above will allow you to disconnect whoever has stolen the single-user connection to the database and save you waiting next time!

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...