This is a message from our DBA, who it appears is receiving the error. Maybe it will help:
"Update of the SCITSCDDB server issues we are having. I had to restart the server around 6:30 this morning. I had asked Jayme Zupkow (Microsoft) yesterday if there was any information since all our searches were bringing back numerous scenarios. Here is what she said: This is going to take some time to analyze and if we can not resolve it we will open an incident. Additional information about this error: Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003 RTM all write registry information to the disk (%windir%\system32\config) every 5 seconds. The timer to begin flushing the registry starts after 10 minutes of boot time. When you changed a registry and try saving, due to resource related issues, the registry keys would not stay set. Starting with Windows Server 2003 Service Pack 1 we added a new Event ID, Event ID 333's. The Event ID 333's are written to the system event log if the O.S. is not able to flush and write to the registry hive. The only way to recover the error message is to restart the server. The solution is to find out what's leading to this condition." -----Original Message----- From: Candee Vaglica [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2008 13:03 PM To: NT System Admin Issues Subject: Re: Event error 333 Interesting. Let us know what it turns out to be. On Tue, Mar 4, 2008 at 11:22 AM, David W. McSpadden <[EMAIL PROTECTED]> wrote: > I sent that on to the MS support team that is working with me. > > > ----- Original Message ----- > From: "Candee Vaglica" <[EMAIL PROTECTED]> > To: "NT System Admin Issues" <[email protected]> > Sent: Tuesday, March 04, 2008 10:57 AM > Subject: Re: Event error 333 > > > > Have you checked eventid.net? > > Looks like there's some good info regarding that error there. > > http://www.eventid.net/display.asp?eventid=333&eventno=5757&source=Appli cation%20Popup&phase=1 > > > > > > On Tue, Mar 4, 2008 at 9:25 AM, David W. McSpadden <[EMAIL PROTECTED]> > > wrote: > >> > >> I keep getting this error on my Production server. Microsoft support > >> runs a > >> checkreg tool and fixes the registry but hasn't determined the source of > >> the > >> corruption. Have any of you seen this error and or the cause of it?? > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > > > ______________________________________________________________________ > > This email has been scanned by the MessageLabs Email Security System. > > For more information please visit http://www.messagelabs.com/email > > ______________________________________________________________________ > > > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
