Lỗi sql server service the remote call failed năm 2024

Question

Previously I installed SQL Server 2008 R2 Express version and since I needed the full text search I uninstalled SQL Server 2008 R2 Express and then installed SQL Server 2008 R2 Express with advanced services.

P.s my RPC background service is running.

I executed the following command and it returned an error:

 C:\Users\venkat>mofcomp.exe "C:\Program Files (x86)\Microsoft SQL    Server\100\Shared\sqlmgmproviderxpsp2up.mof"
 Microsoft (R) MOF Compiler Version 6.1.7600.16385
 Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
 Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof
 MOF file has been successfully parsed
 Storing data in the repository...

Error:

An error occurred while processing item 1 defined on lines 4 - 7 in file C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof: Error Number: 0x80041003, Facility: WMI Description: Access denied Compiler returned error 0x80041003

marc_s

8,9226 gold badges44 silver badges51 bronze badges

asked Mar 25, 2015 at 8:00

1

In my case there were two instances of the "SQL server Configuration Manager" in SysWOW64. Only the latest version worked. The other version produced the RPC error message.

C:\Windows\SysWOW64\mmc.exe /32 C:\WINDOWS\SysWOW64\SQLServerManager10.msc FAILED
C:\Windows\SysWOW64\mmc.exe /32 C:\WINDOWS\SysWOW64\SQLServerManager11.msc WORKED

answered May 10, 2016 at 14:46

The problem is solved by running the command prompt as administrator and typing the same commands for me. Hope it helps

answered Jan 7, 2017 at 9:48

This error appears to happen when .mof files (Managed Object Format (MOF)) don’t get installed and registered correctly during set-up. To resolve this issue, Execute the following mofcomp command in command prompt to re-register the *.mof files:

I am generally write down according to bit size. which OS you are using according to that you can execute the command

There are some situations When you open SQL server configuration manager you get an error saying “Remote procedure call failed (0x800706be)”

There may be 2 possible root causes to trigger this error;

Issue 1. Shared Files for All Instances of SQL Server

Issue 2. Not pointing the correct Configuration Manager Path in an Multi DB instance enviornment

Below, will try to address all those two possible issues

Issue 1 Solution:

Common files used by all instances on a single computer are installed in the folder <drive>:\Program Files\Microsoft SQL Server\nnn\. <drive> is the drive letter where components are installed. The default is usually drive C. <nnn> identifies the version. The following table identifies versions for the paths.

<nnn> Version 140 SQL Server 2017 130 SQL Server 2016 120 SQL Server 2014 110 SQL Server 2012 100 SQL Server 2008

We will do step by step:

1. Checking the WMI Repository

If using Window Server 2008 and above, run command from command prompt to verify WMI repository: winmgmt /verifyrepository

If you get any error, please contact your OS team for WMI rebuild.

Recompile the MOF file

cd C:\program files (x86)\Microsoft SQL server\140\shared

c:\program files (x86)\Microsoft SQL server\140\shared>mofcomp.exe sqlmgmproviderxpsp2up.mof

Re-register the SQL Server provider DLL

regsvr32 “C:\program files (x86)\Microsoft SQL server\140\shared\sqlmgmprovider.dll”

Issue 2 Solution:

Step 1: Open the SQL server configuration manager location through Windows Start->type SQL server configuration manager ->right click->Open file location

you may notice that the shortcut is pointing to SQLServerManager10.msc or any other

Spep 2: go to the path what the msc is located

Step 3: you will see their is a higher version of the same is present in my case SQLServerManager11.msc, so I changed the shortcut path to the latest version i.e. I changed target of the SQL configuration manager shortcut to as below;

C:\Windows\SysWOW64\mmc.exe /32

C:\windows\SysWOW64\SQLServerManager11.msc

Step 4:After saving the above change, open the SQL Server Configuration manager from the windows start menu. and now you should see all the SQL server Services in it.

mẹo hay