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.
Non-fatal Error in module: SMS_CLIENT_CONFIG_MANAGER
Object: Client Configuration Request
Object name: GRO000S1
Error code: 53
Installation or configuration of the Systems Management Server client software cannot be completed on the NT machine named LT0622. The most likely causes are (a) the client machine is not running, (b) the client machine is not connected to the network, (c) SMS service account does not have Administrator privileges on the client machine (indicated by WIN32 error code 5), or (d) the machine is running an operating system other than Windows NT.
Verify that the machine is running and on the same network as the SMS logon server. If the error code is 5, verify that either (a) the SMS service account belongs to the Administrators group on the client machine, or (b) a local account on the client machine exists with the same name and password as the SMS service account, or (c) an account exists in the domain in which the client machine belongs, with the same name and password as the SMS service account.
MachineName = GN_SRV1
SiteCode = GRO
Component = SMS_CLIENT_CONFIG_MANAGER
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What are the Windows error codes?
What is SMS ?
Why are some errors fatal?
Woodrow Wayne Collins
Error code: 53 = Request Source: Unable to obtain a SQL connection. See ME122177 for Systems Management Server event log codes.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated