October 25, 2012 at 9:20 am
Hi
I have installed SP2 on 2008 R2 successfully,but when i tried to connect got error
Login failed for user '<Domain Name>\<user name>'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. (Microsoft SQL Server, Error: 18401)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18401&LinkId=20476
------------------------------
I reboot the server but no use. SQL Service starts successfully but stops when tries to login.
Please help
October 25, 2012 at 9:27 am
Looks like you have installed SP on one of the nodes in the cluster.
I think installing SP on other other node would fix the issue.
October 25, 2012 at 9:30 am
Thanks for the reply. Its not a cluster just a standalone server.
October 25, 2012 at 10:06 am
Check the setup log and Windows event log. You might find details if any thing failed during setup.
October 29, 2012 at 7:24 am
Got this from windows error log. Going for master rebuild as i dont have a backup.
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 537, state 3, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
October 29, 2012 at 8:40 am
I did master rebuild using the below script but still getting the same error
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts [ /SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]
December 7, 2012 at 12:20 pm
We have ran into this issue on several servers. This is the fix:
Start sql server in upgrade disabled mode
From the command prompt:
"C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQL\MSSQL\Binn\sqlservr.exe" -sMSSQL -T902
Be sure to update the path above as needed to reflect your environment.
Via ssms:
From msdb:
Delete:
dc_admin role
Dc_operator role
Dc_proxy role
UlitityCMRReader role
UtilityIMRReader role
UtilityIMRWriter role
Stop the sql service;
Start the sql service via failover cluster admin or services;
Do not use the command line to start the sql server for normal use if it is a cluster instance;
January 30, 2013 at 3:32 pm
We recently ran into this same issue. At the time the best advise we found was to "...wait and retry starting the sql server server after a few minutes...", seems that many people on the web have had the same problem and waiting a few minutes [I'm guessing of the script to finish...?] worked.
In our case, this did work, but it took over two hours! We had opened a ticket and were waiting for MS to call us back and decided to "give it one more try", and it worked. So we dropped the ticket.
So, the moral is, apparently ... wait if you run into this error.
January 30, 2013 at 4:32 pm
script upgrade mode is the last step in the upgrade of an instance for 2008 onwards (IIRC). After you install the upgrade, the next time you start SQL it will run a bunch of scripts, this can take a few minutes. So if you get this message when logging on....just wait.
monitor the errorlog until you see the 'recovery is complete' message, at that point the upgrade is complete and you can log on normally
---------------------------------------------------------------------
January 31, 2013 at 1:19 am
Thanks everyone for the reply
December 2, 2014 at 3:56 am
Hi,
I have the same problem, where the instance will not start after a service pack upgrade.
If I go to the alertlog file, I see this:
2014-12-02 10:53:47.93 spid7s MODIFY FILE failed. File 'MSDBLog' does not exist.
2014-12-02 10:53:47.94 spid7s Error: 912, Severity: 21, State: 2.
2014-12-02 10:53:47.94 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2014-12-02 10:53:47.94 spid7s Error: 3417, Severity: 21, State: 3.
2014-12-02 10:53:47.94 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
These are my registry settings:
HKHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.I2008\Setup\SQLDataRoot
F:\Program Files\Microsoft SQL Server\MSSQL10_50.I2008\MSSQL
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.I2008\MSSQLServer\DefaultData
K:\MSSQL.1\MSSQL\Data
As per http://blogs.msdn.com/b/sqlserverfaq/archive/2010/10/27/sql-server-2008-service-fails-to-start-after-applying-service-pack-1.aspx I tried to change the latter path to
F:\Program Files\Microsoft SQL Server\MSSQL10_50.I2008\MSSQL
and I tried
F:\Program Files\Microsoft SQL Server\MSSQL10_50.I2008\MSSQL\Data
, but that does nothing.
On the folder with the MSDB database, these are the permissions:
SYSTEM: Full controll
SQLServerMSSSQLUser$<servername>$<instancename>: Full control
Administrators: Full control
I tried adding the service account that rns the SQL Server instance, but that that didn't work as well. Also, there is enough space on al harddrives. What should i do?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply