MSSQL$MICROSOFT##SSEE event description not found - 2008 R2 DC

Question

This is a 2008 R2 domain controller, that previously had WSUS and Deep Freeze Core / Admin installed on it.
In order to promot system stability, I have removed WSUS and Deep Freeze, and uninstalled MSSQL 2005 / 2008 components from the server.
Previous thread:
http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/7f50a802-8f72-46a6-a433-7929ca1b0735
dcdiag /c reports the domain is passing all tests.
However, I am seeing event log messages that there are event descriptions for "MSSQL$MICROSOFT##SSEE" that can't be found. I believe this is the Windows Internal Database used by domain controllers.
Service info:
HKLM\SYSTEM\CurrentControlSet\services\eventlog\Application\MSSQL$MICROSOFT##SSEE]
"CategoryCount"=dword:00000008
"CategoryMessageFile"="c:\\Windows\\SYSMSI\\SSEE\\MSSQL.2005\\MSSQL\\Binn\\Resources\\sqlevn70.rll"
"EventMessageFile"="c:\\Windows\\SYSMSI\\SSEE\\MSSQL.2005\\MSSQL\\Binn\\Resources\\sqlevn70.rll"
"TypesSupported"=dword:000000ff
This SQL event category/message file exists, so I don't know what exactly the problem is:
C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn\Resources\sqlevn70.rll
Size: 3kb
Date created: 10/14/2005 1:26 PM
File Version: 2005.090.1399.00
One event log mentions event ID 17111, and lists a log location:
C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
The logs in that directory in general look to me like the Internal Database is working, and it's just the event log that's having a problem showing logged event descriptions correctly:
2013-01-09 03:30:22.10 Server      Microsoft SQL Server 2005 - 9.00.5000.00 (X64)
 Dec 10 2010 10:38:40
 Copyright (c) 1988-2005 Microsoft Corporation
 Windows Internal Database (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)
2013-01-09 03:30:22.24 Server      (c) 2005 Microsoft Corporation.
2013-01-09 03:30:22.24 Server      All rights reserved.
2013-01-09 03:30:22.24 Server      Server process ID is 2000.
2013-01-09 03:30:22.24 Server      Authentication mode is WINDOWS-ONLY.
2013-01-09 03:30:22.24 Server      Logging SQL Server messages in file 'C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG'.
2013-01-09 03:30:22.24 Server      This instance of SQL Server last reported using a process ID of 1888 at 1/9/2013 3:27:20 AM (local) 1/9/2013 9:27:20 AM (UTC). This is an informational message only; no user action is required.
2013-01-09 03:30:22.24 Server      Registry startup parameters:
2013-01-09 03:30:22.24 Server        -d C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf
2013-01-09 03:30:22.27 Server        -e C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
2013-01-09 03:30:22.27 Server        -l C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
2013-01-09 03:30:22.53 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-01-09 03:30:22.53 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2013-01-09 03:30:24.56 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2013-01-09 03:30:25.50 Server      Database mirroring has been enabled on this instance of SQL Server.
2013-01-09 03:30:25.75 spid5s      Starting up database 'master'.
2013-01-09 03:30:26.70 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-01-09 03:30:27.18 spid5s      SQL Trace ID 1 was started by login "sa".
2013-01-09 03:30:27.25 spid5s      Starting up database 'mssqlsystemresource'.
2013-01-09 03:30:27.28 spid5s      Error: 958, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2013-01-09 03:30:27.51 spid5s      Server name is 'MYSERVER\MICROSOFT##SSEE'. This is an informational message only. No user action is required.
2013-01-09 03:30:27.57 spid8s      Starting up database 'model'.
2013-01-09 03:30:27.57 spid5s      Starting up database 'msdb'.
2013-01-09 03:30:27.57 Server      Server local connection provider is ready to accept connection on [
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query ].
2013-01-09 03:30:27.59 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2013-01-09 03:30:27.62 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-01-09 03:30:27.98 spid8s      Clearing tempdb database.
2013-01-09 03:30:29.12 spid8s      Starting up database 'tempdb'.
2013-01-09 03:30:29.46 spid5s      Recovery is complete. This is an informational message only. No user action is required.
2013-01-09 03:30:29.57 spid11s     The Service Broker protocol transport is disabled or not configured.
2013-01-09 03:30:29.59 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2013-01-09 03:30:29.80 spid11s     Service Broker manager has started.
2013-01-09 19:00:11.38 Server      Server resumed execution after being idle 55750 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2013-01-10 22:29:20.01 Server      Server resumed execution after being idle 4449 seconds: user activity awakened the server. This is an informational message only. No user action is required.
I can't find a clear answer to what "Error 958 Severity 10" is, but it looks like the Internal database succeeds at starting up regardless of that error, so apparently it is working properly.
At this point there is no non-DC software installed that is trying to use the Internal Database, so I assume it is being used by the domain controller for its own domain purposes as it should be.
Due to the weird/incorrect event log messages, should I be concerned here at all that the Internal Database may be damaged and this domain controller may be unreliable?
There are only two DCs in this network and this is one of them.

Answer 1

You are probably correct. The Wikipedia article for the internal database CAN be used by Active Directory, but it isn't necessarily actually used.
http://en.wikipedia.org/wiki/Windows_Internal_Database
"Several components of Windows Server 2008 and 2012 use Windows Internal Database for their data storage:
Active Directory Rights Management Services,
Windows System Resource Manager,
UDDI Services,
Active Directory Federation Services 2.0, and Windows SharePoint Service."
It is quite possible it is sitting idle and nothing is using it. I do not see the Internal Database installed on our other domain controller, and I'd expect it on both if the domain needs it.
So, I am now looking at the prospect of reinstalling some SQL tools just so I can access the internal database to see what, if anything, is in there.
How to look at databases in Windows Internal Database
http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/7ac072ab-62b7-436e-a468-65067e17ed77
Microsoft® SQL Server® 2008 Management Studio Express
http://www.microsoft.com/en-us/download/details.aspx?id=7593
Windows Internal Database is not listed in the Add or Remove Programs tool
http://support.microsoft.com/kb/920277/en-us