Hi,

I have a problem that my OLAP services is restarting itself. I have SP3 and till now it worked OK. And now I get this kind of message in the Event viewer - system log.

The MSSQLServerOLAPService service terminated unexpectedly. It has done this 39 time(s). The following corrective action will be taken in 0 milliseconds: No action.

In the past I had this kind of error on another server but with new SP everything worked OK.

Any idea?

THX, Andrej

Hi Andrej,

Do you got the mini dump of this crash?

It should be created automatically in the Analysis server\Data\ folder as
SQLDmpr0001.mdmp if it's not there make sure that the file dbhelp.dll
(version 6.0.17.0 or higher) is available in the Analysis\bin directory.
You can grab this file for example out of the bin folder from a sp3 SQL
server.

I can have a look into this dump if you can post it for me.

Regards,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Hi,

I checked the dump and this crahs is filed at Microsoft this is sheduled to
be fixed with sp4. There is no fix available at the moment.

The crash stack seems related to lazy processing, could yo turn this of to
look if it's gone then. You can do this easily for example with the
following new sp3 key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Server
DSOCommitMode 2

From
New Functionality for Incremental Update of Changing Dimensions WGID:223
ID: 325289.KB.EN-US CREATED: 2002-06-24 MODIFIED: 2003-01-09
http://support.microsoft.com/default...b;en-us;325289

It could be necessary to stop AS service, rename datafolder, and do a full
process of the database because of the crashes.

If you still got problems after this do I advise to contact your local
Microsoft office and ask assistance from the support department. To work
with you to get a fix or an acceptable workaround.

HTH,
Bas


"This posting is provided "AS IS" with no warranties, and confers no
rights."

Hello,

I have seen similar problems with my analysis server, one problem area we had was a particular cube could crash the server if it did not have the latest PTS installed from SP3 on all the clients in addition to the server.

Regards

Paul
"Andrej Hudoklin" <andrej.hudoklin (AT) add (DOT) si> wrote

Hi,

I have a problem that my OLAP services is restarting itself. I have SP3 and till now it worked OK. And now I get this kind of message in the Event viewer - system log.

The MSSQLServerOLAPService service terminated unexpectedly. It has done this 39 time(s). The following corrective action will be taken in 0 milliseconds: No action.

In the past I had this kind of error on another server but with new SP everything worked OK.

Any idea?

THX, Andrej

Yes the problem is that a particular cube crashes the server, but about the PTS and SP3. I have Pivot table services 8.0 and SP3 for SQL server and Analysis installed, it was installed prior to this events.

What have you meant on all the clients?


"Paul Adams" <paul.adams (AT) siemens (DOT) com> wrote

Hello,

I have seen similar problems with my analysis server, one problem area we had was a particular cube could crash the server if it did not have the latest PTS installed from SP3 on all the clients in addition to the server.

Regards

Paul
"Andrej Hudoklin" <andrej.hudoklin (AT) add (DOT) si> wrote

Hi,

I have a problem that my OLAP services is restarting itself. I have SP3 and till now it worked OK. And now I get this kind of message in the Event viewer - system log.

The MSSQLServerOLAPService service terminated unexpectedly. It has done this 39 time(s). The following corrective action will be taken in 0 milliseconds: No action.

In the past I had this kind of error on another server but with new SP everything worked OK.

Any idea?

THX, Andrej

Hello,

If you have a user using an OLAP client like for example ProClarity that uses PTS, this client will need the PTS that is included with SP3 of Analysis Services. If you are developing from a workstation and you already have SP3 installed from Analysis Services then I would expect it to be OK.

The problem we found was we had developed a cube which worked fine on our development PC, but when our users started using ProClarity with an old version of PTS it would crash the server.

Regards

Paul
"Andrej Hudoklin" <andrej.hudoklin (AT) add (DOT) si> wrote


Yes the problem is that a particular cube crashes the server, but about the PTS and SP3. I have Pivot table services 8.0 and SP3 for SQL server and Analysis installed, it was installed prior to this events.

What have you meant on all the clients?


"Paul Adams" <paul.adams (AT) siemens (DOT) com> wrote

Hello,

I have seen similar problems with my analysis server, one problem area we had was a particular cube could crash the server if it did not have the latest PTS installed from SP3 on all the clients in addition to the server.

Regards

Paul
"Andrej Hudoklin" <andrej.hudoklin (AT) add (DOT) si> wrote

Hi,

I have a problem that my OLAP services is restarting itself. I have SP3 and till now it worked OK. And now I get this kind of message in the Event viewer - system log.

The MSSQLServerOLAPService service terminated unexpectedly. It has done this 39 time(s). The following corrective action will be taken in 0 milliseconds: No action.

In the past I had this kind of error on another server but with new SP everything worked OK.

Any idea?

THX, Andrej

If you have Parent-Child dimensions, please contact PSS and ask for QFE
872 - it fixed crash during lazy aggregation after incremental processing of
parent-child dimension.

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Mosha,

what exactly does this hotfix?
I've already put DSOCommit on value 2,
Does it do anything else?

Regards,
Andrej


"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote

The hotfix fixes the crash during lazy aggregation processing after
parent-child incremental processing.
You can workaround it by disabling lazy processing (like you did). If this
is satisfactory workaround for you - then you don't need to worry about the
hotfix.

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Well it worked for me in a way that service is not crashing, but in generly
this is not a solution.
The problem is if you disable lazy processing and set DSOCommit on value 2
as Non lazy indexing and if you have virtual cubes, you won't be able to
process it with other cubes, because full process isn't one of operations of
virtual cubes. So, you have to process it separetly.



"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote