As its description indicates, this error occurs when an application its trying to load one of the dependend modules (or libraries) but it cannot find it. This could be because the module is not on the location that the application expects it, is not on the search path or it may be missing. If the file name is indicated one can verify if the file exists and if it is in the location expected by the application. If it is missing, maybe it was removed by uninstalling another application that used that file or it may have been deleted. The solution in this case would be to reinstall the application that reports the problem. If the module name is not provided, one may try to identify it with tools that track the load of various dlls (like NtFilmon from www.sysinternals.com). The reinstall of the application that reported the problem may work as well too.
Symbolic name: ERROR_MOD_NOT_FOUND
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.