Information store terminates unexpectedly.   

Hi,

Last week our small business 2000 server was very slow. The only option was 
to restart the server. After a reboot, the information store won’t start. 
After a long search, I fixed it by renaming the exchsrvr\mailroot\vsi 1 
folder to exchsrvr\mailroot\vsi_tmp. The exchange 2000 server inserts a new 
vsi 1 folder and was able to start. Since that point the information store 
terminates unexpectedly, restarts automatically (I configure that in 
services) for a few times ands run smoothly for a couple of ours. First I 
thought it was a memory problem and try to resolve error 9582 (the exchange 
server is fragmenting in surge a ………..) by changing the 
HeapDecommitFreeBlockThreshold key, applying hotfix KB  883527, applying post 
sp3 and the latest windows 2000 service pack. By doing all this I get only a 
warning and not a error that the memory is running to low. After I “resolved” 
the error 9582, I checked the private and public group by doing a eseutil 
/mh. That’s give me a dirty shutdown. I repaired this by doing eseutil /d 
after I did eseutil /p. After that, i checked the integrity with eseutil and 
everything looks fine. By doing a isinteg on both groups and 176 fixed where 
done everything looks ok. But unfortunately it isn’t. The information store 
is terminates unexpectedly at a random time. I think I did almost everything, 
do anybody else have a possible solution?

date: Wed, 12 Apr 2006 03:00:02 -0700   author:   H Werkman

Re: Information store terminates unexpectedly.   

I am not sure about your steps to repair the DB.
If your DB was in dirty shutdown then eseutil /d will fail.
When you are in dirty shutdown you have 2 options:
1. You have the reuqired log files - Just mount the DB and log replay will 
take place or do it manually eseutil /R Exx
2. You don't have the reuqired log files - Then you need to do a restore (if 
you have a backup) or an eseutil /P (if you don't).


Anyway you IS is terminating. What can you do?

1. Install the required symbol files and set Dr Watson as the default 
debugger drwtsn32 -i
Then you can wait for a crash and take a look at the drwtsn log to see where 
the fault is ocurring.
Try and cross refernce this against something on support.microsoft.com to 
see if there is some fix that may solve this problem.
You can also get a crash dump and take a look at it with winddg. This may 
show you where the fault is occuring but it is not user friendly at all.

2. You could call PSS and get them to help you solve the problem. I 
recommend this solution

/Simon



"H Werkman"  wrote in message 
news:881E721C-AFB1-492B-8E61-D69AA777A569@microsoft.com...
> Hi,
>
> Last week our small business 2000 server was very slow. The only option 
> was
> to restart the server. After a reboot, the information store won't start.
> After a long search, I fixed it by renaming the exchsrvr\mailroot\vsi 1
> folder to exchsrvr\mailroot\vsi_tmp. The exchange 2000 server inserts a 
> new
> vsi 1 folder and was able to start. Since that point the information store
> terminates unexpectedly, restarts automatically (I configure that in
> services) for a few times ands run smoothly for a couple of ours. First I
> thought it was a memory problem and try to resolve error 9582 (the 
> exchange
> server is fragmenting in surge a .....) by changing the
> HeapDecommitFreeBlockThreshold key, applying hotfix KB  883527, applying 
> post
> sp3 and the latest windows 2000 service pack. By doing all this I get only 
> a
> warning and not a error that the memory is running to low. After I 
> "resolved"
> the error 9582, I checked the private and public group by doing a eseutil
> /mh. That's give me a dirty shutdown. I repaired this by doing eseutil /d
> after I did eseutil /p. After that, i checked the integrity with eseutil 
> and
> everything looks fine. By doing a isinteg on both groups and 176 fixed 
> where
> done everything looks ok. But unfortunately it isn't. The information 
> store
> is terminates unexpectedly at a random time. I think I did almost 
> everything,
> do anybody else have a possible solution?
>

date: Wed, 12 Apr 2006 15:29:16 +0200   author:   Simon Walsh