Share via

Support Tip: App-V client service fails with Error 1114: A Dynamic Link Library (DLL) initialization routine failed

  • Article

imageHello everyone, John Behneman here, and today I wanted to tell you about an interesting App-V issue I ran into the other day and what we did to fix it.

What happened was that the Microsoft Application Virtualization client service failed to start and generated the following error message:

Error 1114
A Dynamic Link Library (DLL) initialization routine failed

We also found the following event in the Application event log:

Log Name: Application
Source: Microsoft-Windows-WMI
Date: <date-time>
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
Description: Event filter with query "select * from __instancecreationevent within 60 where targetinstance isa "win32_service" and targetinstance.name="msmpsvc"" could not be reactivated in namespace "//./root/cimv2" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

When we checked the sftlog.txt file we found this:

[01/29/2013 19:04:48:773 ABCD CRT] {tid=1980}
Initialization of the Application Virtualization file system security failed (status 16D13A0A-0000E016).

I began to suspect a WMI issue but running the Winmgmt /verifyrepository command in an elevated command prompt indicated that the WMI repository is consistent.

We did some more investigation and found that although the WMI repository was consistent it was missing the CIMWIN32.MOF class objects.

To resolve this, we simply ran the following command in an elevated command prompt:

mofcomp %systemroot%\system32\wbem\CIMWIN32.MOF

As a side note, if the result of the Winmgmt /verifyrepository command indicates that the repository is inconsistent, try running the following command:

Winmgmt /salvagerepository

Also note that WMI issues are not the only cause of this particular error. I’ve included a couple other links that might also help below:

John Behneman | Senior Support Escalation Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter :

clip_image001 clip_image002

System Center All Up: https://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: https://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: https://blogs.technet.com/momteam/
System Center – Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm

Windows Intune: https://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
The AD RMS blog: https://blogs.technet.com/b/rmssupp/

App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/

Comments

  • Anonymous
    September 24, 2013
    Hi, How did you determine that it was missing the CIMWIN32.MOF class object. Is there a program or logs directory that could explain this? Cheers

  • Anonymous
    June 19, 2014
    Hi, Is there a way to fix this if you are not a computer genius? :(

  • Anonymous
    August 19, 2014
    Hi John,

    Thanks for detailed explanation. However I am also wondering how you determined that mentioned object was missing. So can you please provide me further details about that part?