Windows System32 Wbem Wmiaprpl.dll
Charlotta Menchaca
I am consistently having every game crash after a couple minutes and the only error I see in the event viewer is labelled as Event 1008 Perflib: "The Open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed with error code The device is not ready.. Performance data for this service will not be available."
I've tried most, if not all, the quick fixes I've seen related to this error code. Some of these include, running a system scan through the command prompt (no errors detected), booting computer in safe mode, factory resetting my pc, turning off game mode and hardware accelerated GPU scheduling, rolling back Windows updates and graphics drivers (updated once found no fix), and uninstalling and reinstalling the games. All with no change. Please note, I had the same issue a month ago and it magically went away for a while.
it seems that Your WmiApRpl. dll file could be missing due to accidental deletion, uninstalled as a shared file of another program (shared with Windows), or deleted by a malware infection. Furthermore, WmiApRpl. dll file corruption could be caused from a power outage when loading Windows, system crash while loading WmiApRpl.
Currently we went through a process of upgrading our DCs to 2016 after doing this and going through process of installing ATP sensor on the servers we are having the service crash or stay in a starting state.
The Open Procedure for service "WmiApRpl" in DLL "C:\Windows\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Azure Advanced Threat Protection Sensor service, but this action failed with the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
The Open Procedure for service ".NETFramework" in DLL "C:\Windows\system32\mscoree.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
I actually get the same errors as @jomalin but with one exception on these servers and it is mixture as some are 2012 R2 and others are 2016. I also never have installed WinPcap. I wasn't planning on installing npcap either as it doesn't look like it requires it unless i have a physical server and require NIC teaming. In my case all the servers (4) are running on VMware so the only requirement is the change on the NIC adapter being used. As for npcap it seems that my installs work fine until the update process goes out and looks for updates and that is where all hell breaks loose. the ATP sensor process stops and then never comes back on. NpCap then gets installed which it seems is coming from the sensor but I have not been able to trace where that install is coming from. What makes it even more weird is that it is only affecting 4 out of the more than 10 DCs we have in our environment. Should I install Winncap to see if all works fine then. I do have a support ticket opened with support but we are just stumped as to why npcap is just being installed on these and not the rest.
One thing to note so i did a complete new install of the sensor. There was no Npcap or winpcap or wireshark installed on the system. It worked fine initially. about an hour later looks to be the updater service kicks in and right around the same time npcap 0.9982 gets installed and these errors begin to happen. Now i have also experimented with me manually installing npcap but same exact issues happened. The sensor doesn't like it.
The updater service kicks in every 30 sec or so, and only does something if it finds a new version at the back end, which happens mostly once a week unless we need to patch something quickly, so unless you are using an old package, the updater should not really do anything post running for the first time until we really release a new version. (newest today is 2.106)
Thanks for the assist. I guess to help others. In my case a 3rd party app was pushing out Nmap and along with it came Npcap. I hadn't noticed because it wasn't by the typical methods of installs we utilize. As well as there was no trace of Nmap itself. Once I ran ProcMon once again with some slight modifications to the filter as suggested by @EliOfek I was able to find the culprit and fix my issue. The problem is now gone and I have documentation for historical sake.
The Open Procedure for service ".NETFramework" in DLL "C:\windows\system32\mscoree.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Open Procedure for service "WmiApRpl" in DLL "C:\windows\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Make sure that my license support Sitecore xConnect. Please contact your Sitecore regional officer to ask about if your license is eligible for xConnect. Normally, they would need to regenerate a new one. If this license was used on Sitecore 8, then you need to ask for a new one for Sitecore 9.
I have a VB.NET application that uses an MSDE database. I'm creating an install program that will install my app and a named instance of MSDE. I'm trying to make the process as easy and foolproof as possible for very nontechnical end-users. My development machine is WinXP Pro.
I'm having trouble with uninstalling MSDE. As most everyone knows, if _anything_ goes awry with an app, during installation or later, a very common resolution step to consider is an uninstall/reinstall. My problem seems to be with MSDE, so I skipped my app and just worked with MSDE. I installed it with the setup.exe provided by MS:
The install ran through to completion, and the log reported success. I then uninstalled the named instance using Add/Remove Programs from the Control Panel. That process ran without error. But the re-install failed. In the log file, the first occurrence of 'Return value 3' is about 80% down in the file:
I can get around the problem by going through the steps in the Microsoft KB article on manually removing .... But my end-users can't/won't. First, I'm pretty sure that msizap.exe (required by that procedure) can't be redistributed. Second, all I have to do is mention the word 'Registry' -- with or without the necessary standard dire warning -- and my users will say something like 'Sorry. I'm not interested in your app, just tell me how to get it off of my computer.' The answer to that request, of course, again involves the same 'Registry' and you begin to see how unproductive the conversation will get.
I may be able to code an uninstall routine that will execute many of the 'manually remove' steps by deleting directories and registry entries, but I still can't redistribute msizap.exe. And I'm thinking there's gotta be a better way.
I'm not really trying to 'access MSDE,' I'm trying to install it. All I'm doing to install it is run Microsoft's setup.exe. I've taken a look at the Event log. Other than Information entries, I found 2 Errors and a Warning (see below). I'm not sure how to interpret/resolve these, since I'm simply(!) running the Microsoft-provided setup.exe.
The open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\System32\wbem\wmiaprpl.dll" has taken longer than the established wait time to complete. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted.For more information, see Help and Support Center at
The description for Event ID ( 19011 ) in Source ( MSSQL$ENP356 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: (SpnRegister) : Error 1355.
I think my problem is more with the uninstall process than with the install process. Admittedly, there may be something I should be doing on the install end that would ensure success for the uninstall. If there is, I'd love to know what that is. My install runs successfully the first time I run it. And with the current release of MSDE, MS seems to be requiring us to install MSDE by using their Setup.exe program: (from the ReadmeMSDE200A.htm file that comes with MSDE)
"MSDE 2000 Release A does not include the merge modules that are sometimes used to embed earlier versions of MSDE 2000 in application setup utilities. To distribute the MSDE 2000 Release A files with applications, you must write an application setup wrapper utility that:
If I wanted to go the merge module route as you suggest, I'd have to use orca to dissect the 17 msi files (SqlRun01.msi - SqlRun17.msi) that come with MSDE. As far as I have been able to tell, there's no documentation re what these files contain or options for changing them. And I've found no documentation about how to change the UNinstall process.
4a15465005