locked
Cannot start SQL Server Express 2017 RRS feed

  • Question

  • I setup SQL 2017 Express.

    I chose custom install and the installation directory was different from the default one.

    I create a new database and then two tables in this database.

    I entered a wrong query in SQL management studio and then SQL management studio was disconnected from the SQL server.

    Then, I cannot connect again.

    I typed sqlcmd -S myPC\SQLEXPRESS -E and obtained:

    Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Shared Memory Provider: Could not open a connection to SQL Server [2]. .
    Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
    Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

    Then, I typed "D:\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS, I obtained a long message. Here is the last few lines:

    2018-11-30 11:02:39.29 spid6s      Uploading data collector package from disk: D:\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Install\SqlTraceCollect.dtsx
    2018-11-30 11:02:39.29 spid6s      Uploading data collector package from disk: D:\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Install\SqlTraceCollect.dtsx
    2018-11-30 11:02:39.29 spid6s      Error: 2775, Severity: 17, State: 12.
    2018-11-30 11:02:39.29 spid6s      The code page 65001 is not supported by the server.
    2018-11-30 11:02:39.30 spid6s      Error: 912, Severity: 21, State: 2.
    2018-11-30 11:02:39.30 spid6s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, 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.
    2018-11-30 11:02:39.30 spid6s      Error: 3417, Severity: 21, State: 3.
    2018-11-30 11:02:39.30 spid6s      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.
    2018-11-30 11:02:39.30 spid6s      SQL Server shutdown has been initiated
    2018-11-30 11:02:39.32 spid6s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    What happened to my SQL server?

    Why can't I start it?

    How to make it work?

    In fact, I have reinstalled it for 3 times and I really want to know how to solve this problem.

    Can anyone help?

    Thank you very much.




    • Edited by hkman2014 Friday, November 30, 2018 3:15 AM
    Friday, November 30, 2018 3:13 AM

Answers

  • I see the below error in your errorlog,

    2018-11-30 11:02:39.29 spid6s      Error: 2775, Severity: 17, State: 12.
    2018-11-30 11:02:39.29 spid6s      The code page 65001 is not supported by the server.

    Can try the details mentioned in this forum post and see if it helps?

    Regards;
    Vivek Janakiraman

    • Proposed as answer by pituachMVP Friday, November 30, 2018 6:01 AM
    • Marked as answer by pituachMVP Sunday, December 2, 2018 1:17 AM
    Friday, November 30, 2018 4:01 AM

All replies

  • It seems like your SQL server instance was patched and the script upgrade mode after the patching is having  issues.

    Please refer this article for more details. Let us know if you have any questions.

    Regards;
    Vivek Janakiraman


    Friday, November 30, 2018 3:21 AM
  • I typed NET START myPC\SQLEXPRESS /T902, it shows:

    System error 123 has occurred.

    The filename, directory name, or volume label syntax is incorrect.

    Friday, November 30, 2018 3:34 AM
  • I see the below error in your errorlog,

    2018-11-30 11:02:39.29 spid6s      Error: 2775, Severity: 17, State: 12.
    2018-11-30 11:02:39.29 spid6s      The code page 65001 is not supported by the server.

    Can try the details mentioned in this forum post and see if it helps?

    Regards;
    Vivek Janakiraman

    • Proposed as answer by pituachMVP Friday, November 30, 2018 6:01 AM
    • Marked as answer by pituachMVP Sunday, December 2, 2018 1:17 AM
    Friday, November 30, 2018 4:01 AM
  • Uncheck Beta: Use Unicode UTF-8 for worldwide language support in Control Panel -> Region -> Administrative -> Change System Locale and restart the computer.

    It works.

    Really thanks for your help, Vivek.


    Friday, November 30, 2018 4:52 AM
  • I am glad to hear that you solve the issue :-)

    Please mark the answer above which helped you solve it


    signature   Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]    [Linkedin]

    Friday, November 30, 2018 5:57 AM
  • Thanks, you are a genius.
    Friday, November 22, 2019 2:17 PM