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.
|Source: Server Agents|
Component: Remote Insight Agent
Error: Could not read from the registry sub-key.
Cause: This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error.
0000: aa 05 00 00
|English: Request a translation of the event description in plain English.|
I think that this can be solved by following the suggestions for Event id 333 from Application Popup.
Data portion aa 05 points to Error code 0x5aa or 1450, confirming the description of the event that the system is running low on resources.
|Private comment: Subscribers only. See example of private comment|
|Links: Error code 1450, Event id 333 from Application Popup|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated