Does anyone know if there are issues with OLAP (sp1) connecting SQL SERVER
2000 SP4?

We had a problem w/ are OLAP box this morning and after a reboot the service
would no longer start.

We getting the following error w/ dump files. I am unable to find anything
about EventID=2905(shown below).

The only thing I can think of is that we recently upgraded the sql server
that OLAP server is connecting to(we upgraded from sql sp3 to sql sp4)


TitleName=MSSQL
ErrorText=SQLDumper
HeaderText=SQL Server Error Reporting
ErrorSig=00051EE4
ErrorDetail=Dump
Server=watson.microsoft.com
Stage1URL=/StageOne/msmdsrv_exe/8_0_760/msmdsrv_exe/8_0_760/00051EE4.ht
Stage2URL=/dw/stagetwo.asp?szAppName=msmdsrv.exe&szAppVer=8.0.76 0&szModName=msmdsrv.exe&szModVer=8.0.760&offset=00 051EE4&
UI LCID=1033
DataFiles=D:\Microsoft Analysis Services\Data\SQLDmpr0117.mdmp
RegSubPath=Microsoft\PCHealth\ErrorReporting\DW
Flags=262528
EventLogSource=MSSQLSERVER
EventID=2905
ErrorSubPath=msmdsrv.exe\8.0.760\msmdsrv.exe\8.0.7 60\00051EE4
Caption=Microsoft SQL Server

This was fixed using the same solution given for
"MSSQLServerOLAPService cannot start" post



There have been reported problems with dimension corruption (fixed in
SP4) -- and this sounds like what you might be running into.

Stop the msmdsrv service, go into the AS data folder and rename each of the
database folder temporarily to something else, then restart the service. If
it comes up, then one-by-one stop and restart the service bring each
database on-line until you find the one with the corrputed dimension. Then
do a similar activity with each dimension until you find the corrupted
dimension. Once you find those, then do a full process of the dimension (and
underlying cubes/partitions which might be affected).

--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)



"Jeremy" wrote: