Win 2000 Database Reset Errors

Hi all

The MSDE instance on our WSUS server crashed a month ago, which it
recovered (or appeared to!) fine from. However a few of the Windows
2000 clients are having issues reporting in now. Most are fine, and
all of XP/2003 are fine too.

The windowsupdate.log file reports multiple issues:
2007-03-30 10:51:41 1296 558 DtaStor WARNING: DS: Database will be
reset next time it starts up due to 0xc80001fe
2007-03-30 10:51:41 1296 558 DtaStor WARNING: DS: Database will be
reset next time it starts up due to 0xc80001fe
2007-03-30 10:51:41 1296 558 PT WARNING: Sync of Updates: 0xc80001fe
2007-03-30 10:51:41 1296 558 Agent * WARNING: Failed to synchronize,
error = 0xC80001FE
2007-03-30 10:51:41 1296 558 Agent * WARNING: Exit code = 0xC80001FE
2007-03-30 10:51:41 1296 558 Agent *********
2007-03-30 10:51:41 1296 558 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-03-30 10:51:41 1296 558 Agent *************
2007-03-30 10:51:41 1296 558 Agent WARNING: WU client failed Searching
for update with error 0xc80001fe
2007-03-30 10:51:41 1296 558 Report REPORT EVENT: {4747B101-1D4B-455D-
B601-789E76D3F669} 2007-03-30 10:51:22+0100 1 202 102
{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Content Install Reboot completed.
2007-03-30 10:51:41 1296 558 AU >>## RESUMED ## AU: Search for
updates [CallId = {26DA602B-9AA5-4C21-8248-F5CD3E3E5B2D}]
2007-03-30 10:51:41 1296 558 AU # WARNING: Search callback failed,
result = 0xC80001FE
2007-03-30 10:51:41 1296 558 AU #########
2007-03-30 10:51:41 1296 558 AU ## END ## AU: Search for updates
[CallId = {26DA602B-9AA5-4C21-8248-F5CD3E3E5B2D}]
2007-03-30 10:51:41 1296 558 AU #############
2007-03-30 10:51:41 1296 558 AU AU setting next detection timeout to
2007-03-30 14:51:41
2007-03-30 10:51:46 1296 558 Report REPORT EVENT:
{3D4A1BD9-6C21-46DC-943D-49145179800B} 2007-03-30 10:51:41+0100 1 148
101 {00000000-0000-0000-0000-000000000000} 0 c80001fe AutomaticUpdates
Failure Software Synchronization Error: Agent failed detecting with
reason: 0xc80001fe
2007-03-30 10:56:41 1296 558 DtaStor WARNING: DS: Database will be
reset next time it starts up due to 0xc80001fe
2007-03-30 10:56:41 1296 558 DtaStor WARNING: DS: Database will be
reset next time it starts up due to 0xc80001fe
2007-03-30 11:05:52 1296 558 DtaStor WARNING: Forcing re-creation of
data store
2007-03-30 11:05:52 1296 558 DtaStor FATAL: Failed to initialize
datastore, error = 0xC8000212
2007-03-30 11:05:52 1296 558 Report WARNING: Reporter failed to upload
events with hr = c8000212.

The Automatic Updates service on the affected PCs will then not stop -
it needs to be disabled, then the PC rebooted. I've tried doing this
then deleting both the SoftwareDistribution and WindowsUpdate.log
file, but this doesn't fix it. I've tried "wuauclt /
resetauthorization", deleting the affected computers from WSUS,
deleting the SusClientID and AccountDomainSID entries in the
registry.. nothing.

Does anyone have any further ideas I can try? We don't really want to
rebuild these PC's simply to get WSUS going again!

"Andrew" <> wrote in message
news: oups.com...
> Hi all
>
> The MSDE instance on our WSUS server crashed a month ago, which it
> recovered (or appeared to!) fine from. However a few of the Windows
> 2000 clients are having issues reporting in now. Most are fine, and
> all of XP/2003 are fine too.
>
> The windowsupdate.log file reports multiple issues:
> 2007-03-30 10:51:41 1296 558 DtaStor WARNING: DS: Database will be
> reset next time it starts up due to 0xc80001fe
> 2007-03-30 10:51:41 1296 558 DtaStor WARNING: DS: Database will be
> reset next time it starts up due to 0xc80001fe
> 2007-03-30 10:51:41 1296 558 PT WARNING: Sync of Updates: 0xc80001fe
> 2007-03-30 10:51:41 1296 558 Agent * WARNING: Failed to synchronize,
> error = 0xC80001FE
> 2007-03-30 10:51:41 1296 558 Agent * WARNING: Exit code = 0xC80001FE
> 2007-03-30 10:51:41 1296 558 Agent *********
> 2007-03-30 10:51:41 1296 558 Agent ** END ** Agent: Finding updates
> [CallerId = AutomaticUpdates]
> 2007-03-30 10:51:41 1296 558 Agent *************
> 2007-03-30 10:51:41 1296 558 Agent WARNING: WU client failed Searching
> for update with error 0xc80001fe
> 2007-03-30 10:51:41 1296 558 Report REPORT EVENT: {4747B101-1D4B-455D-
> B601-789E76D3F669} 2007-03-30 10:51:22+0100 1 202 102
> {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
> Content Install Reboot completed.
> 2007-03-30 10:51:41 1296 558 AU >>## RESUMED ## AU: Search for
> updates [CallId = {26DA602B-9AA5-4C21-8248-F5CD3E3E5B2D}]
> 2007-03-30 10:51:41 1296 558 AU # WARNING: Search callback failed,
> result = 0xC80001FE
> 2007-03-30 10:51:41 1296 558 AU #########
> 2007-03-30 10:51:41 1296 558 AU ## END ## AU: Search for updates
> [CallId = {26DA602B-9AA5-4C21-8248-F5CD3E3E5B2D}]
> 2007-03-30 10:51:41 1296 558 AU #############
> 2007-03-30 10:51:41 1296 558 AU AU setting next detection timeout to
> 2007-03-30 14:51:41
> 2007-03-30 10:51:46 1296 558 Report REPORT EVENT:
> {3D4A1BD9-6C21-46DC-943D-49145179800B} 2007-03-30 10:51:41+0100 1 148
> 101 {00000000-0000-0000-0000-000000000000} 0 c80001fe AutomaticUpdates
> Failure Software Synchronization Error: Agent failed detecting with
> reason: 0xc80001fe
> 2007-03-30 10:56:41 1296 558 DtaStor WARNING: DS: Database will be
> reset next time it starts up due to 0xc80001fe
> 2007-03-30 10:56:41 1296 558 DtaStor WARNING: DS: Database will be
> reset next time it starts up due to 0xc80001fe
> 2007-03-30 11:05:52 1296 558 DtaStor WARNING: Forcing re-creation of
> data store
> 2007-03-30 11:05:52 1296 558 DtaStor FATAL: Failed to initialize
> datastore, error = 0xC8000212
> 2007-03-30 11:05:52 1296 558 Report WARNING: Reporter failed to upload
> events with hr = c8000212.


Try a search?

http://perso.orange.fr/doc.jm/WU5-ERR.htm

(Live Search for
0xc80001fe microsoft codes
)

<extract>
0xC80001FE -939523586 hrLogWriteFail unable to write to the log file
0xC8000211 -939523567 hrLogDiskFull
0xC8000240

</extract>

>
> The Automatic Updates service on the affected PCs will then not stop -
> it needs to be disabled, then the PC rebooted. I've tried doing this
> then deleting both the SoftwareDistribution and WindowsUpdate.log
> file, but this doesn't fix it.


Sounds as if you have already guessed there is a problem with a log file?
Perhaps there is a permissions problem with it?
Try running FileMon to see if that is the case.

Tip: if you use ProcMon instead it will interleave both File and Registry
accesses for you including the writes to the above log file. Hence, you
can get supplemental information about the codes (such as the probable
name of the file which is full, etc.) Note: the log records can be inferred
by their lengths. E.g. use Notepad with Word Wrap off and press End
to find the length of a line you want more information about; then find when
a line of that length (or 1 byte more) was written. Etc.


> I've tried "wuauclt /
> resetauthorization", deleting the affected computers from WSUS,
> deleting the SusClientID and AccountDomainSID entries in the
> registry.. nothing.
>
> Does anyone have any further ideas I can try? We don't really want to
> rebuild these PC's simply to get WSUS going again!


Good luck

Robert Aldwinckle
---

On Apr 4, 1:45 am, "Robert Aldwinckle" <rob...@techemail.com> wrote:
> Try a search?
>
> http://perso.orange.fr/doc.jm/WU5-ERR.htm

> 0xC80001FE -939523586 hrLogWriteFail unable to write to the log file
> 0xC8000211 -939523567 hrLogDiskFull
> 0xC8000240

Yeah, found them - they're not that helpful in this case!

> > The Automatic Updates service on the affected PCs will then not stop -
> > it needs to be disabled, then the PC rebooted. I've tried doing this
> > then deleting both the SoftwareDistribution and WindowsUpdate.log
> > file, but this doesn't fix it.
>
> Sounds as if you have already guessed there is a problem with a log file?
> Perhaps there is a permissions problem with it?
> Try running FileMon to see if that is the case.

It doesn't appear to be.. I've managed to delete everything as
mentioned above, so that when the service restarts it recreates
everything, but the same error reappears :/

I think we'll just have to leave the machines be and keep an eye on
any 2k patches coming out. They'll all be replaced soon enough, I
guess.

A.