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.
There was a problem with '<computer name>', which is an alternate name for '<computer name>'. The list of aliases is now '<computer name>', and the alias 'was' removed from the list. The specific problem is '<problem description>'.
|English: Request a translation of the event description in plain English.|
Reported problem: CreateFile(\\nodename\sgguid\log) = 2 - According to ME975255, this occurs because a temporary lock locked the log file when the copy operation started. However, after the lock is released, the copy operation is complete. See the article for an update rollup information.
Reported problem: "CreateFile(\\NODE1\efaab020-73c8-4618-a8c9-8676801cdeb3$\E020001087A.log) =
2" - From a support forum post: "I got my case escalated to a MS Lead Tech and as soon as he saw VMWare he shut me down and sent me a link to their support policy. I expect this they are going to strictly enforce this now that Hyper-V is out. VMWare users beware!"
Problem description: "Continuous replication operation aborted." - no info
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated