This indicates that an expected programming interface (or method/procedure) could not be detected in the loaded module (typically a dependent dll that is used by an application). One example when this may happen is for example when one installs an application on Windows NT and the application is trying to use functions that are only available to Windows 2000. See M175030 as example.
Sometimes, these procedure only became available with a certain service pack so the (re)installation of the latests service pack may help.
Symbolic name: ERROR_PROC_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.