This evening, our TSM server crashed (again). I've seen this very error
several times, with version 5.2.2.0.

When this happened I restored the database from the latest backup and
everything was okay, for a while at least.

I upgraded to 5.2.3.0 recently, and it's the first time it happened with
5.2.3.0

Version information: TSM for Windows, Version 5, Release 2, Level 3.0
on Windows 2000 Server SP4 with all the latest patches from Windows
Update.

Error message in console.log:

ANR9999D pkthread.c(835): ThreadId<50> Run-time assertion failed: "bitOff >=
0", Thread 50, File dballoc.c, Line 388.
Callchain: 104EAD79  outTextf()+1529
<- 10006649  pkLogicAbort()+39 <-

Error message in Windows Event Log:

TSM Server Diagnostic: ANR9999D: ADSM Exception Information: file =
pkthread.c, line = 2253,Code = e0000001, Address = 77E9BBF3~


When I try to restart the server, I get this error message in console.log:


Tivoli Storage Manager for Windows
Version 5, Release 2, Level 3.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990,2003. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 1024 megabytes.
ANR0201I Database assigned capacity is 4096 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR9999D dballoc.c(1363): ThreadId<0> Zero bit count mismatch for SMP page
addr 153600; Zero Bits = 1, HeaderZeroBits = 2.
Callchain: 104EAD79
outTextf()+1529 <- 101A53B6  tsmInitializeServer()+19DB86 <- 00480001  Unknown
 <-
ANR0361E Database initialization failed: error initializing database page
allocator.

I cannot look into the activity log until I restore the database, but I
think it was running a scheduled backup from a Windows client when the
error occured.

Any ideas what I should do now, other than restore the database?

Thanks in advance,
   Rainer Schöpf