Cannot Connect to WMI - Access denied [0x80041003] - Sql Server

▲
0
▼

Thanks for reading and responding in a very constructive way to this question, I will try to get straight to the point to avoid to lose time at all:

PROBLEM: i can't run "SQL Server 2014 Configuration Manager" enter image description here

When i try to run it, i see this window message: enter image description here

to avoid giving an answer to inefficient solutions I've tried, I send an image for each share already done that has not solved the problem.

FAILED ATTEMPTS + IMAGE RESULTs:

  1. mofcomp sqlmgmproviderxpsp2up.mof [Access Denied][3]

  2. winmgmt /verifyrepository (+ others commands) [Access Denied][4]

  3. net stop winmgmt [is consistent, but not solve the problem][5]

  4. dcomcnfg.exe (solution found here) [Access Denied][6]

  5. Component Services WMI Properties [activated service for all user, adnim, grant mode access][7]

  6. REPOSITORY - dir deleting, moving, silly shaking... nothing

  7. WBEMTEST [Connect > Connect > "Access Denied"][9]

  8. wmidiag.vbs basenamespace="root\default" [excellent test, but not solution][10]

  9. Component Services WMI Properties - Services (Local) [still: Access Denied][11]

  10. this is the content of REPOSITORY dir: [Access Denied][12]

  11. Computer Management > WMI Control Properties [Access Denied again...][13]

these are the results of the "wmidiag.vbs" tests:

WMIDiag v2.2 started on mercoledì 12 aprile 2017 at 16:44.

Copyright (c) Microsoft Corporation. All rights reserved - July 2007.

There are no missing WMI system files: .............................................................................. OK. There are no missing WMI repository files: .......................................................................... OK. WMI repository state: ............................................................................................... N/A. AFTER running WMIDiag: The WMI repository has a size of: ................................................................................... 0 MB. - Disk free space on 'C:': .......................................................................................... 137266 MB. - INDEX.BTR, 65536 bytes, 12/04/2017 13:02:31 - MAPPING1.MAP, 92 bytes, 12/04/2017 12:58:28 - MAPPING2.MAP, 492 bytes, 12/04/2017 14:09:40 - OBJECTS.DATA, 106496 bytes, 12/04/2017 13:02:31

WARNING: Windows Firewall: .......................................................................................... DISABLED.

DCOM Status: ........................................................................................................ OK. WARNING: WMI registry setup: ........................................................................................ SERVICE SETUP ISSUES! => If the WMI service is RUNNING and if registry settings are not correct, you should check which registry key is subject to modifications (below in this report). You can eventually repair the registry: - manually with REGEDIT.EXE. - by importing the missing registry keys from a working system (same Windows version, same SP level). - You can also repair the WMI Service registry setup by re-creating the WMI service setup with the following command: i.e. 'SC.EXE CREATE WINMGMT BINPATH= C:\WINDOWS\SYSTEM32\WBEM\WINMGMT.EXE START= AUTO' Note: The SC.EXE command is available in the Windows Resource Kit. If the command fails because the WMI service name already exists, you can delete the existing definition with the following command: i.e. 'SC.EXE DELETE WINMGMT' If the SC.EXE command does not work, you can delete with REGEDIT.EXE the registry hive at: 'HKLM\SYSTEM\CurrentControlSet\Services\Winmgmt' and re-execute the 'SC.EXE CREATE' command above. Note: It could be required to reboot the system to refresh the Service Control Manager configuration. - Once the WMI service is re-created: - Make sure there is no other registry keys missing or wrongly configured. You can manually add the missing keys with REGEDIT. - After re-creating the registry, and fixing ALL missing entries, you must configure the WMI service to run as a STANDALONE service host or as a SHARED service host (SvcHost) You can achieve this by running the following commands: - to configure the service to run as a SHARED service host (recommended): i.e. 'WINMGMT.EXE /SharedHost' - if you have issue to get the WMI service running as a SHARED service host, it can be configured to run as a STANDALONEservice host: i.e. 'WINMGMT.EXE /StandaloneHost' => Reboot the system.

INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)! - Security Center (WSCSVC, StartMode='Disabled') - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled') => If the WMI service is stopped, the listed service(s) will have to be stopped as well. Note: If the service is marked with (*), it means that the service/application uses WMI but there is no hard dependency on WMI. However, if the WMI service is stopped, this can prevent the service/application to work as expected.

RPCSS service: ...................................................................................................... OK (Already started). WINMGMT service: .................................................................................................... OK (Already started).

WMI service DCOM setup: ............................................................................................. OK. WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 2 WARNING(S)! - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32) - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32) => WMI System components are not properly registered as COM objects, which could make WMI to fail depending on the operation requested. => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE ' command.

WMI ProgID registrations: ........................................................................................... OK. WMI provider DCOM registrations: .................................................................................... OK. WMI provider CIM registrations: ..................................................................................... OK. WMI provider CLSIDs: ................................................................................................ OK. WMI providers EXE/DLL availability: ................................................................................. OK.

INFO: User Account Control (UAC): ................................................................................... ENABLED. => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context. i.e. You can start your scripts or WMIC commands from an elevated command prompt by right clicking on the 'Command Prompt' icon in the Start Menu and selecting 'Run as Administrator'. i.e. You can also execute the WMI scripts or WMIC commands as a task in the Task Scheduler within the right security context.

INFO: Local Account Filtering: ...................................................................................... ENABLED. => WMI tasks remotely accessing WMI information on this computer and requiring Administrative privileges MUST use a DOMAIN account part of the Local Administrators group of this computer to ensure that administrative privileges are granted. If a Local User account is used for remote accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.

DCOM security for 'Windows Management Instrumentation' (Access Permissions): ........................................ MODIFIED. ERROR: Actual trustee 'NT AUTHORITY\SELF' DOES NOT match corresponding expected trustee rights (Actual->Default) - ACTUAL ACE: ACEType: &h0 ACCESS_ALLOWED_ACE_TYPE ACEFlags: &h0 ACEMask: &h3 DCOM_RIGHT_EXECUTE DCOM_RIGHT_ACCESS_LOCAL - EXPECTED ACE: ACEType: &h0 ACCESS_ALLOWED_ACE_TYPE ACEFlags: &h0 ACEMask: &h7 DCOM_RIGHT_EXECUTE DCOM_RIGHT_ACCESS_LOCAL DCOM_RIGHT_ACCESS_REMOTE

=> The actual ACE has the right(s) '&h4 DCOM_RIGHT_ACCESS_REMOTE' removed! This will cause some operations to fail! It is possible to fix this issue by editing the security descriptor and adding the removed right. For DCOM objects, this can be done with 'DCOMCNFG.EXE'.

DCOM security warning(s) detected: .................................................................................. 0. DCOM security error(s) detected: .................................................................................... 1. WMI security warning(s) detected: ................................................................................... 0. WMI security error(s) detected: ..................................................................................... 0.

ERROR: Overall DCOM security status: ................................................................................ ERROR! Overall WMI security status: ........................................................................................ OK. - Started at 'ROOT/DEFAULT' ------------------------------------------------------------------------------------------------------ WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE. WMI TIMER instruction(s): ........................................................................................... NONE. ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)! - ROOT/DEFAULT, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.

ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)! - ROOT/DEFAULT, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/subscription, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/DEFAULT, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/CIMV2, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/CIMV2/Security, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/CIMV2/Applications, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/nap, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/WMI, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/directory, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/directory/LDAP, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/SecurityCenter, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/Microsoft, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/Microsoft/HomeNet, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action. - Root/aspnet, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.

WMI GET operations: ................................................................................................. OK. WMI MOF representations: ............................................................................................ OK. WMI QUALIFIER access operations: .................................................................................... OK. WMI ENUMERATION operations: ......................................................................................... OK. WMI EXECQUERY operations: ........................................................................................... OK. WMI GET VALUE operations: ........................................................................................... OK. WMI WRITE operations: ............................................................................................... NOT TESTED. WMI PUT operations: ................................................................................................. NOT TESTED. WMI DELETE operations: .............................................................................................. NOT TESTED. WMI static instances retrieved: ..................................................................................... 0. WMI dynamic instances retrieved: .................................................................................... 0. WMI instance request cancellations (to limit performance impact): ................................................... 0.

17 error(s) 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action => This error is typically due to insufficient or restricted permissions in the examined system. => ENSURE you are a Full Administrator of the examined system, if the WMI provider or the WMI system security do not enforce any restrictions.

Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)! ERROR: Unexpected registry key value: - Current: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h3 - Expected: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h2 From the command line, the registry configuration can be corrected with the following command: i.e. 'REG.EXE Add "HKLM\SYSTEM\CurrentControlSet\Services\winmgmt" /v "Start" /t "REG_DWORD" /d "2" /f'

------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------

ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS********\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_********_2017.04.12_16.44.43.LOG' for details.

WMIDiag v2.2 ended on mercoledì 12 aprile 2017 at 16:44 (W:35 E:34 S:1).

I'm Admin - i have a grant permission (i have 12 screenshoot) but the problem persist...

I may find it one person can solve this problem without stupid "formatting and Windows re-install" solution? Thank you so much for your cooperation

sql-server
windows-7
wmi
asked on Stack Overflow Apr 12, 2017 by M.C.

0 Answers

Nobody has answered this question yet.

User contributions licensed under CC BY-SA 3.0