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. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The VB Application identified by the event source logged this <event description>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a “runtime”?
- Description: "Application MSCSCfg: Thread ID: 1164 , Logged: PCOPipeline: Loader error: -2147024770 Automation error The specified module could not be found" - See ME897072.
ME184747 provides information on event logging in Visual Basic.
Description: "Application Global Sync Service: Thread ID: 804, Logged: Send Mail: Object variable or With block variable not set." - no info.
Description: Application name Thread ID: 1316 Function: ProcessFiles. Error : Path Not Found - no info
The description is very generic and is related to various errors that can occur in a Visual Basic program. Usually this event appeared when the exception-handling routines in VB programs are poorly implemented.
|Private comment: Subscribers only. See example of private comment|
|Links: ME184747, ME897072|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated