Hi,

for some strange reason the mssqlserverolapservice is automatically
RESTARTING every 1 minute. This has never happened before.


ALso, due to this, there are numerous .mmdmp files generated ( I guess
1 file is generated for each restart)

We have ample space on our harddisks, so I dont think that space is an
issue.

Can you suggest the reaosn why this happens and and suggest a solution
to get rid of this problem.

We run SQLServer2000 in a WINDOWS 2000 Server maching. We've been
using Sql2000 and msolap from the past 8 months.

Please respond asap

Kirri,
I ave had this happen before. The files which are created
are minidumps. The reason why AS stops and starts again
is most probably that there is an error in one of your AS
databases from which AS tries to recover by restarting.

The solution I used is to go into your "C:\Program
Files\Microsoft Analysis Services\Data" folder. Here you
can find all the database storage files. Remove one at a
time (back it up in a different folder). AS will rebuild
the database and eventually will start up normally. You
know that you have found the flawed database then.

There is no way i know to As to keep the data in this
particular database, though. You will have to reload all.

There might be other solutions, but this is the only
working one I know of. Why exactly the problem is
occurring beats me.

HTH Lutz Morrien

Here is an old post of mine, adressing the subject:

You are right, the client (we are using an asp server)
was on a different SP Level.

It is amazing that a different PTS version on the client
can mess up the server as much as it did, though.

Here is the MS bug description I used to solve the hiccup
problem. I have seen questions asked about this phenomena
several times, so it seems to be quite common.

Thanks for your help
Lutz
---
Check under
http://support.microsoft.com/default.aspx?scid=kb;en-
us;278325
---
BUG: OLAP Server Stops Responding When Data Files are
Corrupted
The information in this article applies to:
Microsoft SQL Server OLAP Services 7.0
This article was previously published under Q278325
BUG #: 11387 (plato7x)
SYMPTOMS
The OLAP server stops responding (hangs) in some
situations if one or more data files are corrupted.
Sometimes this occurs when OLAP Services is in
a "Starting" state rather than a "Started" or "Stopped"
state. Even if the service starts, the OLAP server does
not accept connections from OLAP Manager, the MDX sample
application or any other applications. The following
error message occurs in the OLAP Manager:
Cannot open connection to OLAP server 'ServerName'
This error message occurs with the MDX sample
application:
Unable to open connection. OLAP server error: The
operation requested failed due to network problems.
The OLAP Server uses two TCP ports:
2393

-and-
2394
Typing in the following netstat command:

netstat -a

shows port 2393 to be in a SYN_SENT state under these
conditions.
TCP wsweceprocdb1t:3787 localhost:2393
SYN_SENT

WORKAROUND
As a work around:
1. Stop the OLAP server.
2. Remove or rename the "..\Olap
Services\Data\DatabaseName.odb" file, and then start the
OLAP server again. You should now be able to connect from
OLAP Manager and other OLAP applications. If this method
does not work, then you might consider reprocessing the
OLAP databases after you remove the .odb files from the
Data folder.

To test which database may have a corrupted data file,
rename the data directory for the specific database that
is in the \Program Files\Microsoft Analysis Services\Data
folder. For example, in the Data folder there is a
directory named FoodMart 2000. To test if the FoodMart
2000 database has a corrupted file, rename the directory
to "testFoodMart 2000", stop and then restart the
service. The OLAP Service creates a new but empty
directory named FoodMart 2000. If the service starts
successfully you know that the FoodMart 2000 database has
a corrupted file and must be reprocessed.
STATUS
Microsoft has confirmed that this is a problem in SQL
Server OLAP Services version 7.0 and Microsoft SQL Server
2000 Analysis Services version 8.0.

What front end are u using to connect to MSAS?

-n