Dear Himanshu Dwivedi,
The message you're seeing — "The description for Event ID 2050 from source Microsoft-Windows-SystemDataArchiver cannot be found..." — typically indicates that the event source is present, but the corresponding message resource DLL is either missing, not properly registered, or not accessible by the logging tool.
Here are a few key points to consider:
Windows Component Behavior This event is generated by the SystemDataArchiver, a Windows component tied to SRUM (System Resource Usage Monitor). If the event originated locally but the message cannot be rendered, it may suggest that the required resource files are not available or are not being interpreted correctly by the log viewer.
Third-Party Tool Limitation Kiwi Syslog Server may not have access to the localized message resources needed to display the full event description. This is common when third-party tools collect logs from Windows Event Viewer but do not include the necessary DLLs to interpret certain proprietary event messages.
Confirm that the SystemDataArchiver component is properly installed and not disabled or corrupted. You can do this by checking sfc /scannow
and reviewing component health.
Ensure that the log forwarder is configured to include event message text, not just event metadata.
If the event is being forwarded from another machine, verify that the original system has the necessary message resources and that the forwarding method preserves them.
Consider reviewing the event directly in Windows Event Viewer on the source machine to confirm whether the full message is visible there.
I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
B`est regards,
Domic Vo