WMI: Access is Denied after Win2K to XP Upgrade

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

MOW - 06 Apr 2006 01:20 GMT

I have just upgraded a laptop from Windows 2000 Service Pack 4 to Windows XP
Service Pack 2 and since doing so I cannot get access to WMI data. I've also
noted the following symptoms:

- Can't see any Network Connections in the Network Connections folder.
- Receive an error 0x800A0046 when running Windows Updates.
- Receive the message WMI: Access is denied when looking at service
dependencies.
- Receive the message "Can't collect information" when using MSinfo.
- Receive the message "WMI: Access is Denied" when looking at the properties
of WMI Control under Computer Management.

So far I've:
- Done everything in Knowledge Base articles 254631 and 823775
- I've run the command "rundll32.exe setupapi,InstallHinfSection WBEM 132
%windir%\inf\wbemoc.inf" to rebuild the WMI database.
- I've reregistered all the WMI components.
- I've deleted the repository folder (and saw that it was recreated).
- I've checked that the SERVICE account has the "Impersonate a client after
authenitcation" permission.
- I've checked that all necessary services are running with the correct
credentials.
- I've checked the DCOM default impersonate and authenication levels.
- I've removed the machine from the domain.
- I've checked and compared the registry permissions to a working machine
using AccessEnum for SysInternals.
- I've run an inplace upgrade (repair) install, starting from Windows and
starting from booting from the CD.

I'm pretty sure this is simply a permissions problem, but can't for the life
of me find where the problem is. Is there anything else to try before a
clean install?

Thanks

Reply to this Message

Wesley Vogel - 06 Apr 2006 02:33 GMT

Start the Windows Management Instrumentation (WMI) service, the Network
Connections service and DCOM Server Process Launcher. Also set them all to
Automatic.

You can get online w/o the Network Connections service running, but the
Network Connections folder won't work right.

[[Note the following things will fail if this service is not running:
• The builtin defrag will fail to work, and if running defrag from the
command line one gets this error:
Windows cannot connect to the Disk Defragmenter engine

• System Information (MsInfo32) will fail to work and give this error:
Can't Collect Information
A network error occurred in connecting to Windows Management
Instrumentation. Ensure that your network connection is
functioning properly.

• If Windows Firewall is enabled, then it will fail to start and all
incomming traffic will be blocked. More Info MS KB 892199
http://support.microsoft.com/kb/892199

• Disk Management will fail and give this error:
The RPC server is unavailable

• The install of new applications will fail and give this error:
The InstallShield Engine (iKernel.exe) could not be launched.
The RPC server is unavailable. ]]
from...
DCOM Server Process Launcher
http://smallvoid.com/tweak/winnt/service/def.html

[[Note if this service is stopped, it will at least have the following
effects:
Actions that requires WMI will give errors like:
Interface: Class not registered

Win32: The service cannot be started, either because it is disabled or
because it has no enabled devices associated with it

* Unable to see Service Dependencies using Services.msc
* Unable to select Properties for the Computer Management (Local) using
CompMgmt.msc
* Unable to see System Information using MsInfo32
* (WinXP) Will experience long delays with System restore (Or not work at
all) ]]
from...
Windows Management Instrumentation (WMI)
http://smallvoid.com/tweak/winnt/service/wxyz.html#WINMGMT

[[CAUSE
The error message occurs if the Windows Management Instrumentation (WMI)
service is not started. This can occur if the service is disabled, if a
dependent service is not started, or if a problem is preventing the WMI
service from starting. The System Information utility will be able to
collect information after the WMI service is started. ]]
from...
Msinfo32.exe Generates a "Can't Collect Information" Error Message
http://support.microsoft.com/?kbid=323209

Signature

Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

> I have just upgraded a laptop from Windows 2000 Service Pack 4 to Windows
> XP Service Pack 2 and since doing so I cannot get access to WMI data.
[quoted text clipped - 30 lines]
>
> Thanks

Reply to this Message

MOW - 06 Apr 2006 04:45 GMT

The WMI, Network Connections and DCOM Server Process Launcher services are
all set to auto and are running. I'm also not experiencing any of the
symptons that you listed. Defrag, Disk Management, Windows Firewall and
Software installations are all working. The error message for WMI actions is
"Access is Denied" not "Class not registered".

Any other ideas.

Thanks.

> Start the Windows Management Instrumentation (WMI) service, the Network
> Connections service and DCOM Server Process Launcher. Also set them all to
[quoted text clipped - 90 lines]
> >
> > Thanks

Reply to this Message

Wesley Vogel - 06 Apr 2006 20:08 GMT

Repairing and re-registering the WMI
http://windowsxp.mvps.org/repairwmi.htm

Signature

Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

> The WMI, Network Connections and DCOM Server Process Launcher services are
> all set to auto and are running. I'm also not experiencing any of the
[quoted text clipped - 106 lines]
>>>
>>> Thanks

Reply to this Message

MOW - 07 Apr 2006 00:29 GMT

Thanks Wesley,

I had already found that article and followed each of the steps in it. None
made any difference.

Here is the WMI report:

.1161
----------------------------------------------------------------------------------------------------
.1162 -------------------------------------- WMI REPORT: BEGIN
-------------------------------------------
.1163
----------------------------------------------------------------------------------------------------
.1164
.1165
----------------------------------------------------------------------------------------------------
.1166 Windows XP - Service pack 2 - 32-bit - User 'MADISONTECH\ROGERJ' on
computer 'ROGERLAPTOP'.
.1167
----------------------------------------------------------------------------------------------------
.1168 There are no missing WMI system files:
..................................................... OK.
.1169 There are no missing WMI repository files:
................................................. OK.
.1170 BEFORE running WMIDiag:
.1171 The WMI repository has a size of:
.......................................................... 8 MB.
.1172 - Disk free space on 'C:':
................................................................. 4193 MB.
.1173 - INDEX.BTR, 1466368 bytes, 7/04/2006
8:50:18 AM
.1174 - INDEX.MAP, 772 bytes, 7/04/2006
8:51:18 AM
.1175 - MAPPING.VER, 4 bytes, 7/04/2006
8:51:18 AM
.1176 - MAPPING1.MAP, 3976 bytes, 7/04/2006
8:51:18 AM
.1177 - MAPPING2.MAP, 3976 bytes, 7/04/2006
8:50:18 AM
.1178 - OBJECTS.DATA, 6422528 bytes, 7/04/2006
8:50:18 AM
.1179 - OBJECTS.MAP, 3212 bytes, 7/04/2006
8:51:18 AM
.1180 AFTER running WMIDiag:
.1181 The WMI repository has a size of:
.......................................................... 8 MB.
.1182 - Disk free space on 'C:':
................................................................. 4193 MB.
.1183 - INDEX.BTR, 1466368 bytes, 7/04/2006
8:50:18 AM
.1184 - INDEX.MAP, 772 bytes, 7/04/2006
8:51:18 AM
.1185 - MAPPING.VER, 4 bytes, 7/04/2006
8:51:18 AM
.1186 - MAPPING1.MAP, 3976 bytes, 7/04/2006
8:51:18 AM
.1187 - MAPPING2.MAP, 3976 bytes, 7/04/2006
8:50:18 AM
.1188 - OBJECTS.DATA, 6422528 bytes, 7/04/2006
8:50:18 AM
.1189 - OBJECTS.MAP, 3212 bytes, 7/04/2006
8:51:18 AM
.1190
----------------------------------------------------------------------------------------------------
.1191 INFO: Windows Firewall status:
............................................................. ACTIVE.
.1192 => Windows Firewall application exception for 'UNSECAPP.EXE' is
missing.
.1193 - This will prevent any script and MMC application asynchronous
callbacks to this machine.
.1194 - You can adjust the configuration by executing the following
command:
.1195 - e.g. 'NETSH.EXE FIREWALL SET ALLOWEDPROGRAM
%SYSTEMROOT%\SYSTEM32\WBEM\UNSECAPP.EXE WMICALLBACKS ENABLE'
.1196
.1197
----------------------------------------------------------------------------------------------------
.1198 WMI registry setup:
........................................................................ OK.
.1199 INFO: WMI service has dependents:
.......................................................... 2 SERVICE(S)!
.1200 - Security Center (WSCSVC, StartMode='Automatic')
.1201 - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS,
StartMode='Automatic')
.1202 => If the WMI service is stopped, the listed service(s) will have to
be stopped as well.
.1203 Note: If the service is marked with (*), it means that the
service/application uses WMI but
.1204 there is no hard dependency on WMI. However, if the WMI
service is stopped,
.1205 this can prevent the service/application to work as expected.
.1206
.1207 RPCSS service:
.............................................................................
OK (Already started).
.1208 WINMGMT service:
...........................................................................
OK (Already started).
.1209
----------------------------------------------------------------------------------------------------
.1210 WMI service DCOM setup:
.................................................................... OK.
.1211 WMI components DCOM registrations:
......................................................... OK.
.1212 WMI ProgID registrations:
.................................................................. OK.
.1213 WMI provider DCOM registrations:
........................................................... OK.
.1214 WMI provider CIM registrations:
............................................................ OK.
.1215 WMI provider CLSIDs:
....................................................................... OK.
.1216 WMI providers EXE/DLL availability:
........................................................ OK.
.1217 - Started at 'Root'
--------------------------------------------------------------------------------
.1218 09:23:36 (1) !! ERROR: WMI ADAP status:
.................................................................... NOT
AVAILABLE
.1219 You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to
resynchronize
.1220 the performance counters with the WMI performance classes with the
following commands:
.1221 e.g. 'WINMGMT.EXE /CLEARADAP'
.1222 e.g. 'WINMGMT.EXE /RESYNCPERF'
.1223 The ADAP process logs informative events in the Windows NT event
log.
.1224 More information can be found on MSDN at:
.1225
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_
adap_event_log_events.asp
.1226 09:23:36 (1) !! ERROR: WMI CONNECTION errors occured for the following
namespaces: ......................... 5 ERROR(S)!
.1227 - Root, 0x80070005 - Access is denied..
.1228 - Root, 0x80070005 - Access is denied..
.1229 - Root/Default, 0x80070005 - Access is denied..
.1230 - Root/CIMv2, 0x80070005 - Access is denied..
.1231 - Root/WMI, 0x80070005 - Access is denied..
.1232
.1233 WMI GET static operations:
................................................................. OK.
.1234 WMI MOF representations:
................................................................... OK.
.1235 WMI QUALIFIER access operations:
........................................................... OK.
.1236 WMI ENUMERATION operations:
................................................................ OK.
.1237 WMI EXECQUERY operations:
.................................................................. OK.
.1238 WMI PUT operations:
........................................................................ OK.
.1239 WMI DELETE operations:
..................................................................... OK.
.1240 WMI GET VALUE operations:
.................................................................. OK.
.1241 WMI static instances retrieved:
............................................................ 0.
.1242 WMI dynamic instances retrieved:
........................................................... 0.
.1243 WMI instances request cancellations (to limit performance impact):
......................... 0.
.1244
.1245 5 error(s) 0x80070005 - (WBEM_UNKNOWN) This error code is external to
WMI.
.1246 => This error is not a WMI error. It is typically due to:
.1247 - The user running WMIDiag has not enough privileges or rights to
issue requests
.1248 against software components exposing information through WMI.
.1249 => Ensure that no third party applications installing additional
WMI providers have
.1250 specific security requirements (e.g. group membership,
privileges, etc ...)
.1251 - The 'Impersonate Client after authentication' Local Policy is
disabled or the
.1252 'SERVICE' account has been removed from that Local Policy.
.1253 => You must add the 'SERVICE' account to the 'Impersonate Client
after authentication'
.1254 Local Policy with the 'Local Security Policy' MMC snap-in.
.1255 By default, this Local Policy includes the 'SERVICE' account.
.1256
.1257 => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More
information can be found
.1258 with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the
last four hex digits (0x0005)
.1259 converted in decimal (5).
.1260 - NET HELPMSG 5
.1261
.1262
----------------------------------------------------------------------------------------------------
.1263 WMI Registry key setup:
.................................................................... OK.
.1264
----------------------------------------------------------------------------------------------------
.1265
----------------------------------------------------------------------------------------------------
.1266
----------------------------------------------------------------------------------------------------
.1267 --------------------------------------- WMI REPORT: END
--------------------------------------------
.1268
----------------------------------------------------------------------------------------------------

> Repairing and re-registering the WMI
> http://windowsxp.mvps.org/repairwmi.htm
[quoted text clipped - 109 lines]
> >>>
> >>> Thanks

Reply to this Message