I just had a few of those on my NT 3.1.1.3 server myself.  IBM support
suggested that it may be a database corruption problem and suggested a full
DB backup to quickly verify the integrity of the DB.  That worked fine, but
I still got another one of these errors a few weeks later.  This time, I
think I found the answer.  We have Tivoli agents running on the server, and
just before it crashed, there were many orphaned processes from Tivoli in
memory.  I would suggest you look in task manager and see what processes are
running and start turning things off to see if it solves your problem.

James Louie
Nabisco

> On Monday, August 31, 1998 3:24 AM, Mohamed Adan
> [mailto:mohamed.adan AT HYDROTEXACO DOT NO] wrote:
>
> For about 4 days now, we have had something odd on ADSM
> server. I get an
> application error on the screen and the ADSM Server stops. I
> thought that
> this had to do with reclaimation, as the crashes occurred while
> reclaimation was in process. But I have stopped reclaimation
> and when the
> last crash occured, there was no reclaimation process going
> on. Here's the
> error message in the log file:
>
> ANR9999D pkthread.c(2600): ADSM Exception Information:
>                        Code = c0000005, Address =
> 10255333Attempt to write
> data
>                        at address 0
>
> 30-08-1998 22:53:27   ANR9999D asalloc.c(1195): Missing
> allocation storage
>
>                        pool.
>
>
> Is there someone who has had the same experienece?
>
> Thanks in advance.
>
> Regards
>
>
> Mohamed Adan
> Hydro Texaco AS
> Drammensvei. 134
> 0212 Oslo
> Norway
>