May 30, 2018 at 9:05 pm
HELP! So, I was installing the damn January 2018 security patch... it sat there for over 2 bloody hours and I got impatient. I stopped my sql services to get it to do something. It then said hooray your update was successfully installed, please reboot your computer. Upon reboot, I got the lovely error "Reason: Server is in script upgrade mode" and couldn't connect. This is my production server and I am/was in full panic mode.
So, I changed the startup parameter to -T902. Great, I get in. I changed some of the server configuration settings per below:
EXEC sp_configure ‘show advanced’, 1;
RECONFIGURE;
EXEC sp_configure ‘allow updates’, 0;
RECONFIGURE;
EXEC sp_configure ‘Agent XPs’, 1;
RECONFIGURE;
GO
And then I took the -T902 off the startup. It still won't let me in and gives the same error message. So, I have put the -T902 back on there just so my production server actually works. How in the world do I permanently fix this problem? I have never encountered this before in my many years of being a DBA and I am completely deflated that a stupid security patch took me down.
May 31, 2018 at 12:47 am
Pinal Dave described such an issue several years back. See https://blog.sqlauthority.com/2015/04/10/sql-server-login-failed-for-user-reason-server-is-in-script-upgrade-mode/. Can you check the SQL Error log (from Windows Explorer/Notepad)?
May 31, 2018 at 7:32 am
Yes, I opened the error log last night and I didn't see anything obvious... we are migrating off this server in 3-4 months, so I am not sure if I really care at this point. I assume I can leave it in this "mode" as long as I don't have to install anything else?
June 1, 2018 at 5:58 am
This was removed by the editor as SPAM
June 1, 2018 at 6:58 am
satanicendeavour - Friday, June 1, 2018 5:58 AMamy26 - Thursday, May 31, 2018 7:32 AMYes, I opened the error log last night and I didn't see anything obvious... we are migrating off this server in 3-4 months, so I am not sure if I really care at this point. I assume I can leave it in this "mode" as long as I don't have to install anything else?
I read this comment I have a solution for this post. you can simply take a help of Dell Customer Support to solve out the problem. I also face the same problem and the error message is also shown to me so I take a help of this site.
Umm... thank you for the suggestion... but no, Dell Customer Support wouldn't be of any help to me on a custom VM server owned by the government. Dell has nothing to do with this server. 🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply