Share via

installing SQLExpress 2022

eddy sels 45 Reputation points
2023-07-25T19:04:55.1333333+00:00

After successfull uninstalling SQL Serve2022, I wanted to install the lighter Express version.

The log file extract with the errors:

2023-07-25 20:49:44.03 spid26s Error: 17190, Severity: 16, State: 1.

2023-07-25 20:49:44.03 spid26s Initializing the FallBack certificate failed with error code: 15, state: 29, error number: 0.

2023-07-25 20:49:44.03 spid26s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.

2023-07-25 20:49:44.03 spid26s Error: 17182, Severity: 16, State: 1.

2023-07-25 20:49:44.03 spid26s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.

2023-07-25 20:49:44.03 spid26s Error: 17182, Severity: 16, State: 1.

2023-07-25 20:49:44.03 spid26s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.

2023-07-25 20:49:44.03 spid26s Error: 17826, Severity: 18, State: 3.

2023-07-25 20:49:44.03 spid26s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

2023-07-25 20:49:44.03 spid26s Error: 17120, Severity: 16, State: 1.

2023-07-25 20:49:44.03 spid26s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

As a simple user this is cryptic to me. Are the errors a result of the first one or are these all unrelated errors? How to solve this?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,364 questions
Accepted answer
  1. Erland Sommarskog 107.2K Reputation points
    2023-07-25T19:37:48.2666667+00:00

    Those errors often indicate that the default profile in Windows has been corrupted. And thus profiles for new users will also be corrupted.

    This is not the tag for going into details on fixing a corrupt file, but I had to do this once. I think one Google hit suggested copying from another machine. (I think that in the end I restored from a backup.)

    An easier, but necessarily not better, may be to pick a different service account, for instance Local Service. Since you had the real McCoy installed earlier, you may already have NT Service\MSSQLSERVER, so you could reuse that user.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. eddy sels 45 Reputation points
    2023-07-26T12:48:48.1166667+00:00

    I copied the default profile from another computer and redid the installion.

    I still got an error and installation failed because of a missing file. Which one was however not speciefied. So I pretended my nose bleeded and started SSMS and in the local server groups 2 entries were shown. The second entry was created before the reinstallation. After changing the server to the correct name from the log file, the server started and I could attach my databases.

    So it seems to work despite the installation error(s).

    Thanks for the tip.