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: Windows Server Update Services|
Connection to database failed. Reason=Cannot open database "SUSDB" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.. Connection string: Net=dbnmpntwData Source=\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\queryInitial Catalog=SUSDBConnection Timeout=60Application Name=WSUS SQL ConnectionTrusted_Connection=YesPooling='true' Max Pool Size = 100
For more information see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|English: Request a translation of the event description in plain English.|
Edge case to be sure but this is an SBS2003 that has been mostly decommissioned except for one SQL application that we can't migrate at this time. As such pretty much everything on the server has been disabled or uninstalled. Update Services is installed but disabled. SQL ##SSEE is still running however. Event 421 is preceded by 2 of the SQL ##SSEE Failure Audit 18456 events I also included.
In our case it's just log noise we don't need and won't fix WSUS on this machine. May uninstall it. But on a live server if it came up someone might want to know what to do.
|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