SQL Server 2022 Installation Errors in Developer version

William Chen 0 Reputation points
2023-07-10T19:58:31.21+00:00

I tried to install SQL Server 2022 Developer version, but I received error message and not able installation.

My computer is Windows 11, AMD CPU 64.

Screenshot 2023-07-10 153337

I found some error message in my log file

C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230710_153011


(01) 2023-07-10 15:30:34 Slp: The following is an exception stack listing the exceptions in outermost to innermost order

(01) 2023-07-10 15:30:34 Slp: Inner exceptions are being indented

(01) 2023-07-10 15:30:34 Slp:

(01) 2023-07-10 15:30:34 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException

(01) 2023-07-10 15:30:34 Slp: Message:

(01) 2023-07-10 15:30:34 Slp: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.


I tried uninstalled and clean all in registration key, but still not able to install SQL Server 2022. Please help.

Windows for business | Windows Client for IT Pros | User experience | Other
SQL Server | Other
{count} votes

4 answers

Sort by: Most helpful
  1. Erland Sommarskog 121.7K Reputation points MVP Volunteer Moderator
    2023-07-10T21:27:33.5+00:00

    The message about the MOF compiler is a difficult one. I have seen it in more than one post with installation failures, but I don't think it has ever been resolved.

    On the other hand, the screenshot says "Wait for the Database Engine recovery handle failed". This message means that SQL Server did not start, when Setup wanted to run configuration. In this case, we can expect there to be a file C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\LOG\ERRORLOG. If you have this file, and you find a message about 256 misaligned reads, you are subject to a known issue where Windows 11 reports a disk-sector size that SQL Server cannot cope with.

    Microsoft has published an article with workarounds for this problem.

    0 comments No comments

  2. William Chen 0 Reputation points
    2023-07-10T21:40:15.4966667+00:00

    Hi Erland,

    I open the ERRORLOG file, and see following,


    2023-07-10 15:32:39.85 spid42s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft

    ....

    I attach this ERRORLOG file for you to review all detail. ERRORLOG.txt

    Please help to solve this problem which takes me so much time to install it.

    Thanks.


  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Erland Sommarskog 121.7K Reputation points MVP Volunteer Moderator
    2023-07-12T20:29:04.2466667+00:00

    Thankfully, we are rid of the error message about 256 misaligned reads.

    Instead we have an error where the path for the model database relates to the machine where the Setup media was created (I assume). I also note that there are no trace flags listed in the startup, which you normally see when Setup runs SQL Server. Really how to fix this, I don't know. If would happen on my own machine, I could spend some time on experimenting, but doing this remotely without direct access is not appealing.

    But maybe this works: when you run the Setup, specify an instance name rather than going with the default. Each new instance is its own installation, so I would expect this to work.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.