SQL Server Service Manager Fails with "The system cannot find the file specified" Error Message

Question

SQL Server Service Manager Fails with "The system cannot find the file specified" Error Message

Anh Nhật 5

It's said the system cannot find the file specified when I tried to instal sql server

Screenshot 2023-05-22 133154

Ronen Ariely 15,206 Reputation points

2023-05-21T16:59:12.5433333+00:00

Please re-read the message which you get which is not just for fun, and provide the information from the installation log file. The path to the location of the log file is present in the message you got
Anh Nhật 5 Reputation points

2023-05-21T17:11:49.3466667+00:00

i have read but really don't know what to do to fix this. Can you help me
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-05-21T20:29:47.6266667+00:00

The path in the screenshot is to a folder. There are quite a few files in this folder. Summary.txt and Details.txt are typically the most interesting. Feel free to upload them here.
LiHongMSFT-4306 31,566 Reputation points

2023-05-22T03:13:36.16+00:00

Hi @Anh Nhật

Could you please post the log files.

There is a summary.txt file and many subfolders created every time the Installation wizard is started. In those subfolders, we can find a Detail.txt file.

View and Read SQL Server Setup Log Files - SQL Server | Microsoft Learn
Anh Nhật 5 Reputation points

2023-05-22T03:48:20.7+00:00

Summary_meo_20230523_004113.txt

Detail.txt

I ran the setup again and this time it said "The system cannot find the path specific" C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230523_004113

Here is the summary and detail

2 answers

Your answer

Ronen Ariely 15,206 Reputation points

2023-05-21T16:59:12.5433333+00:00

Please re-read the message which you get which is not just for fun, and provide the information from the installation log file. The path to the location of the log file is present in the message you got
Anh Nhật 5 Reputation points

2023-05-21T17:11:49.3466667+00:00

i have read but really don't know what to do to fix this. Can you help me
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-05-21T20:29:47.6266667+00:00

The path in the screenshot is to a folder. There are quite a few files in this folder. Summary.txt and Details.txt are typically the most interesting. Feel free to upload them here.
LiHongMSFT-4306 31,566 Reputation points

2023-05-22T03:13:36.16+00:00

Hi @Anh Nhật

Could you please post the log files.

There is a summary.txt file and many subfolders created every time the Installation wizard is started. In those subfolders, we can find a Detail.txt file.

View and Read SQL Server Setup Log Files - SQL Server | Microsoft Learn
Anh Nhật 5 Reputation points

2023-05-22T03:48:20.7+00:00

Summary_meo_20230523_004113.txt

Detail.txt

I ran the setup again and this time it said "The system cannot find the path specific" C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230523_004113

Here is the summary and detail

Answer 1

LiHongMSFT-4306 31,566

Hi @Anh Nhật

Found this in Detail.txt

Sco: File 'C:\SQL2022\Express_ENU\x64\setup\x64\sql_engine_core_inst.msi' does not exist

Please refer to this similar thread: Please help erorr unable to install sql sever 2022 Express Edision.

Best regards,

Cosmog Hong

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Anh Nhật 5 Reputation points

2023-05-22T08:10:05.8133333+00:00

Is there any way i can change MEO\nhata to MEO\nhatanh?
Anh Nhật 5 Reputation points

2023-05-22T08:11:08.27+00:00

Is there any way i can change MEO\nhata to Meo\nhatanh?
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-05-22T10:43:10.28+00:00

That's what the Add and Remove buttons are for. But you need to know what you are doing. You should only do this if you run Setup from an account you normally don't use. If you want to add this other user, add it, but not remove the current user.

By the way, the name you select here has nothing to do with any Setup problems you may still have. (I don't have the time to look at the log files right now.)
Anh Nhật 5 Reputation points

2023-05-22T11:13:40.4866667+00:00

Weird, my user name is nhatanh but when i get to this step it's just nhata. Will this cause an error after I finish the setup?
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-05-22T21:04:29.17+00:00

Strange. I don't know why that would happen. But as I said, just add nhatant, don't remove the other name.

I now looked at your detail.txt, and I found

File 'C:\Program Files (x86)\Microsoft SQL Server\160\Shared\sqlmgmprovider.mof' not found!

I have not yet fully understand why this file would be missing. But another person I helped admitted having installed and uninstalled and then removed some files manually, Could that fit your situation?

If you have another machine, for instance a VM, on which you can install SQL Server on, maybe you could test copying the file from that computer?
Anh Nhật 5 Reputation points

2023-05-23T09:43:08.82+00:00

Still cannot instal SQL Server @Erland Sommarskog Can you help me check it again?

TITLE: Microsoft SQL Server 2022 Setup

The following error has occurred:

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.

For help, click: https://go.microsoft.com/fwlink?LinkID=2209051&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0xA60E3551%25400xD3BEBD98%25401211%25401

Summary_meo_20230523_163625.txt

Detail.txt
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-05-23T21:03:15.1533333+00:00

If you look in details.txt, you find that just above the exception is the message in my post above.

As I said, I don't fully understand this error and how to deal with it. I've reached out to some people in hope to get some assistance, but I don't know how that will turn out.

Can you tell us more about the steps you've taken previously. After the first installation failure, did you uninstall and start over, or what did you do?
Anh Nhật 5 Reputation points

2023-05-24T07:49:55.76+00:00

After installing error the first time I uninstalled completely, also in Registry Editor, then I reinstalled using Download media but I still get this error.
Anh Nhật 5 Reputation points

2023-05-24T07:52:34.2633333+00:00

I tried installing the older version which is SQL Server 2019 instead of the 2022 version but still getting the same error. Is there any other way I can install SQL Server? @Erland Sommarskog

Answer 2

Hi,

in the log, there is this error:

01) 2023-05-23 00:41:57 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.

(01) 2023-05-23 00:41:57 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.

(01) 2023-05-23 00:41:57 Slp: The configuration failure category of current exception is ConfigurationFailure

(01) 2023-05-23 00:41:57 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.

(01) 2023-05-23 00:41:57 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: 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.

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Repair(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)

(01) 2023-05-23 00:41:57 Slp: The following is an exception stack listing the exceptions in outermost to innermost order

(01) 2023-05-23 00:41:57 Slp: Inner exceptions are being indented

(01) 2023-05-23 00:41:57 Slp:

(01) 2023-05-23 00:41:57 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException

(01) 2023-05-23 00:41:57 Slp: Message:

(01) 2023-05-23 00:41:57 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.

(01) 2023-05-23 00:41:57 Slp: HResult : 0x84bb0001

(01) 2023-05-23 00:41:57 Slp: FacilityCode : 1211 (4bb)

(01) 2023-05-23 00:41:57 Slp: ErrorCode : 1 (0001)

(01) 2023-05-23 00:41:57 Slp: Data:

(01) 2023-05-23 00:41:57 Slp: SQL.Setup.FailureCategory = ConfigurationFailure

(01) 2023-05-23 00:41:57 Slp: WatsonConfigActionData = REPAIR@CONFIGNONRC@COMMONFILES

(01) 2023-05-23 00:41:57 Slp: WatsonExceptionFeatureIdsActionData = System.String[]

(01) 2023-05-23 00:41:57 Slp: Stack:

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()

(01) 2023-05-23 00:41:57 Slp: at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)

I would check: https://mikerodionov.com/unable-to-install-sql-server-2019-sql-install-error-the-mof-compiler-could-not-connect-with-the-wmi-server/

Regards,

Stefan

Anh Nhật 5 Reputation points

2023-05-24T13:34:38.7+00:00

I reinstalled my windows version and i no longer get the old error instead this error. Is there any way to fix this error?

Error details:

§ Error installing SQL Server Database Engine Services Instance Features

Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.

Error code: 1639

Log file: C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230524_195824\sql_engine_core_inst_Cpu64_1.log

Visithttps://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639 to get help on troubleshooting.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-05-24T21:02:48.69+00:00

It's really frustrating to hear that you had to reinstall Windows and still got the problem. But tell me, did you get this specific error the first time after the reinstall?

This is one more of these error, I have not been able to understand much of. (I count myself an SQL Server expert, but I am not an expert in MSI installs.) Anyway, we would need to see summary.txt, details.txt and also sql_engine_core_inst_Cpu64_1.log.

By the way, this is your home machine, right? Or is this in a corporate network?

Share via

SQL Server Service Manager Fails with "The system cannot find the file specified" Error Message

2 answers

Your answer