The first thing that Support recommended for that message was to run an
audit on the affected storage pool.  In my case, that wasn't the
solution.  Neither was running an auditdb on the disk volumes, which had
been drained first.  I finally went with Level 2 looking over my shoulder
and deleting objects.  That took three major scans to identify the offenders.


At 03:27 PM 6/1/2004 +0200, you wrote:

hi all, if someone can help me .... this shows up every time i start the
server

ANR9999D asutil.c(299): ThreadId<0> Pool id 6 not found.
Callchain of previous message: 0x10016138 outDiagf <- 0x
10110CEC asGetPoolAttr <- 0x101FACD4 AfUpdatePool <- 0x101FB268 AfGetPool <-
0x105C06A4 AfMigrationRestart <- 0x1
05BBFB0 AfInit <- 0x105B60BC bfInit <- 0x103D819C admStartServer <-
0x100027B4 main <-


i guess audit db will fix things ?

anyone has experience with this kinda message ?

thanks in advance.

goran

Fred Johanson
ITSM Administrator
University of Chicago
773-702-8464