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 Management Server Service failed to import the updated antimalware definition.
Result code: <error code>
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=OnePoint;Data Source=Computer;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=Computer;Use Encryption for Data=False;Tag with column collation when possible=False
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is SSPI?
As per TB643195, this could be due to the installation of Client Security not being fully configured. The suggestion action is to run the Configuration wizard by launching the Client Security console for the first time.
This event occurs because of the number of characters in various entries that are in the signatures files. See ME936729 for a hotfix applicable to Microsoft Forefront Client Security.
|Private comment: Subscribers only. See example of private comment|
|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