These errors for me were occurring when trying to change the “log on as” user for SQL Server via SQL Server Configuration Manager
WMI Provider Error [call to WMI Provider returned error code 0x8007481d]
To work around this problem, add the user account to the SQLServerMSSQLUser$ComputerName$InstanceName group.
To do this, follow these steps:
- Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
In the Active Directory Users and Computers snap-in, click Users. (or in the local groups in computer manager) - Double-click SQLServerMSSQLUser$ComputerName$InstanceName.
- In the Properties dialog box, click the Members tab.
- On the Members tab, click Add.
- In the Select Users, Contacts, Computers, or Groups dialog box, type the user in the DomainName\UserName format under Enter the object names to select, and then click OK.
- In the Properties dialog box, click OK.
That didn’t entirely fix me, however, I figured my windows firewall not allowing the connections, so I ensured it would, then I reinstalled WMI by doing:
(( from a .bat file ))
@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End :FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer :SkipSrv
goto End :TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End |
And then I ran the following from a dos prompt
C:\Program Files\Microsoft SQL Server\100\Shared>mofcomp "c:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
and I started to get the following:
Oh, a different (and imho better) error.
Still no dice, no how, no way, even ensuring groups above were right, etc… Oddly lost.. soooooo
I Removed and Reinstalled SQL Server, then re-service packed it.
Issue resolved.
What actually resolved it?? I have no idea, but it is resolved, which is why I’m done trying to figure it out. *grins*