Upgrade from 2005 express to 2008 r2 express - provisionsystemaccounts.sql error

• mattech06

  SSCrazy

  Points: 2484

  More actions

  March 21, 2015 at 9:23 am

  #302328

  Hi,

  I’ve been upgrading several of my clients and ran into this problem for one of them.

  When doing the upgrade I got..

  

  Looking at the error logs indicated..

  2015-03-21 11:54:07.58 spid7s Database 'master' is upgrading script 'provisionsystemaccounts.sql' from level 0 to level 2.

  2015-03-21 11:54:07.59 spid7s ----------------------------------------

  2015-03-21 11:54:07.59 spid7s Starting provisionsystemaccounts.sql ...

  2015-03-21 11:54:07.59 spid7s ----------------------------------------

  2015-03-21 11:54:08.02 spid7s Error: 15151, Severity: 16, State: 1.

  2015-03-21 11:54:08.02 spid7s Cannot find the user 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP', because it does not exist or you do not have permission.

  2015-03-21 11:54:08.03 spid7s Error: 912, Severity: 21, State: 2.

  2015-03-21 11:54:08.03 spid7s Script level upgrade for database 'master' failed because upgrade step 'provisionsystemaccounts.sql' encountered error 15151, state 1, 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.

  2015-03-21 11:54:08.03 spid7s Error: 3417, Severity: 21, State: 3.

  2015-03-21 11:54:08.03 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.

  2015-03-21 11:54:08.03 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.Running the Repair from the Installation centre brings up the same error.

  I noticed that the instance appears to be upgraded but basically the service won’t run. I can start it but it just stops again.

  So I found this which seems the same as my problem..

  https://ilkirk.wordpress.com/2011/03/07/in-place-sql-upgrade-error-2005-to-2008/

  Even though I can start the SQL Services using point 1 from the link above I can’t connect to sql using DAC.

  The sqlcmd won’t work and trying to connect through SSMS.

  > SQLCMD –E –A. I’ve also tried >SQLCMD FILESERVER1\ORSQLEXP –E –A and get the same results

  HResult 0xFFFFFFFF, Level 16, State 1

  SQL Server Network Interfaces: An error occurred while obtaining the dedicated administrator connection (DAC) port.

  Make sure that SQL Browser is running, or check the error log for the port number [xFFFFFFFF].

  http://www.sqlservercentral.com/Forums/Skins/Classic/Images/RichTextBoxTable/tbl_bottomleft.gif

  When I try to connect to DAC via SSMS I get ..

  

  So I seem to currently have 2 problems, one using sqlcmd/DAC and the other with provisionsystemaccounts.sql.

  The sqlbrowser is running but from 90 (not sure if that matters) and I have removed (following online research) the 80 and 90 binn settings from the PATH just leaving 100 but this hasn’t changed the errors.

  I’ve tried enabling DAC using this advice below but it hasn’t made any difference. The service keeps stopping and no SQLCMD action.

  http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition

  So after trying numerous options I currently stumped.