July 7, 2003 at 8:24 am
This past weekend I was doing a service pack update. I was installing SP3 on SQL 2k box running windows 2k. I got the message that a previous setup was holding pending file operations which is fairly common. So I rebooted the machine. When it came back up SQL Server started in single user mode. I didn't tell it to start this way and unforutnatley I couldn't get in because I think the NT account that is used to start the services was considered the one account to get in. I went into admin tools and stoped and started the services. And still it stayed in single user mode. Finally I had to hard boot the machine and it came back up fine. Unfortunatly I can't see much help in the event log because I started getting messages about login failures which filled the event log. I guess I am wondering if anyone has seen this before.
Yes I know there is an sp3a but we have to roll out the same sp everywhere here so sp3a was not an option for me since we had already started rolling out sp3.
July 7, 2003 at 11:27 am
I haven't seen it before, but I'm guessing that the Service Pack puts the databases in single user mode 'behind the scenes'. That way it can upgrade without being interfered with by user actions. You just happened to have problems during the short time it was in that mode.
I'm also guessing, but I think you would have been able to log back in with the SA login and password.
-SQLBill
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply