SQL server goes into single user mode randomly

F

f1y

Supreme [H]ardness
Joined
Dec 30, 2005
Messages
8,109
Actually not randomly. It's normally after weekly reboots. This causes the Great Plains DB to be locked to 1 person, so other people get errors.

Sometimes I can just unrestrict access, other times it's grayed out and I have to drop the DB and restart the services to take it out of single user mode.

SQL 2k3.

Anyone ever encounter this glitch?

edit* meant sql 2000, on win server 2k3 :(
 
Last edited:
Ugh Great Pains "In the ass" lol

Are there any locks on the DB when its put into Single user mode? Check the activity logs to get a clue as to what is going on
 
2011-01-12 19:45:06.90 server Copyright (C) 1988-2000 Microsoft Corporation.
2011-01-12 19:45:06.90 server All rights reserved.
2011-01-12 19:45:06.90 server Server Process ID is 2716.
2011-01-12 19:45:06.90 server Logging SQL Server messages in file 'd:\MSSQLDATA\MSSQL\log\ERRORLOG'.
2011-01-12 19:45:06.92 server SQL Server is starting at priority class 'normal'(8 CPUs detected).
2011-01-12 19:45:08.04 server SQL Server configured for thread mode processing.
2011-01-12 19:45:08.06 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2011-01-12 19:45:08.12 server Attempting to initialize Distributed Transaction Coordinator.
2011-01-12 19:45:09.48 spid2 Starting up database 'master'.
2011-01-12 19:45:09.82 server Using 'SSNETLIB.DLL' version '8.0.311'.
2011-01-12 19:45:09.82 spid5 Starting up database 'model'.
2011-01-12 19:45:09.87 spid2 Server name is 'PINNSTRDC'.
2011-01-12 19:45:09.89 spid8 Starting up database 'msdb'.
2011-01-12 19:45:09.89 spid9 Starting up database 'pubs'.
2011-01-12 19:45:09.89 spid10 Starting up database 'Northwind'.
2011-01-12 19:45:09.89 spid11 Starting up database 'DYNAMICS'.
2011-01-12 19:45:09.90 spid12 Starting up database 'PINN'.
2011-01-12 19:45:09.90 spid13 Starting up database 'TWO'.
2011-01-12 19:45:09.90 spid14 Starting up database 'PTEST'.
2011-01-12 19:45:09.95 server SQL server listening on 10.0.0.16: 1433.
2011-01-12 19:45:09.95 server SQL server listening on 127.0.0.1: 1433.
2011-01-12 19:45:10.01 server SQL server listening on TCP, Shared Memory, Named Pipes.
2011-01-12 19:45:10.03 server SQL Server is ready for client connections
2011-01-12 19:45:10.54 spid5 Clearing tempdb database.
2011-01-12 19:45:11.17 spid15 Starting up database 'Shipper'.
2011-01-12 19:45:11.29 spid9 Starting up database 'Contracts'.
2011-01-12 19:45:11.37 spid11 Recovery is checkpointing database 'DYNAMICS' (7)
2011-01-12 19:45:11.40 spid8 Recovery is checkpointing database 'msdb' (4)
2011-01-12 19:45:11.70 spid5 Starting up database 'tempdb'.
2011-01-12 19:45:15.79 spid9 11 transactions rolled forward in database 'Contracts' (12).
2011-01-12 19:45:15.82 spid9 0 transactions rolled back in database 'Contracts' (12).
2011-01-12 19:45:15.89 spid9 Recovery is checkpointing database 'Contracts' (12)
2011-01-12 19:45:39.98 spid12 6472 transactions rolled forward in database 'PINN' (8).
2011-01-12 19:45:41.17 spid12 0 transactions rolled back in database 'PINN' (8).
2011-01-12 19:45:41.21 spid12 Recovery is checkpointing database 'PINN' (8)
2011-01-12 19:45:42.90 spid2 Recovery complete.
2011-01-12 19:45:42.99 spid2 Launched startup procedure 'smDEX_Build_Locks'
Click to expand...

not sure about that last line... I'm unsure about the recovery too..

Dynamics is our bitch database.

There's more of the logfile... I just posted this.
 
There is a company out there that support Great Plains now, i can get the name for you later. But i would give them a call
 
not something as simple as a temp file using all the disk space on the drive where GP has its SQL database.
 
Yeah Great Plains support is pretty decent. If we ever have issues we call them right away. Good people there.
 
You must log in or register to reply here.
Back
Top