Problem by stopping and starting MSSQLSERVEROLAPService
-
Hi,
I experienced a serious problem with Analysis Services 2000 SP4. Because the service was not responding any more I tried to restart the service. The service stops without problems, but when trying to start again it lasts a very long, unusual time (15 minutes) and nothing happens. The service is in the status "starting" and you cannot stop or start it. After a long while the service was up again.
What is happening there? Which opportunities do I have to check for informations what is going on with the SQLServerOLAPProcess or generally a windows process?
The system is Windows 2003 Enterprise Edition. 2 Xeon Processors 32 bits, 8 Gigabytes of RAM.
Best regards, Stefan
Kindest Regards,SK
-
Check the permission for the account starting the service. check for registry, folder and other windows permissions.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
Hi,
thanks for the reply. But the permissions could not be the problem, because I did this with the same credentials and the same settings thousands of times. And nothing changed.
Finally it works. But it lasts very long.
Best regards,
Stefan
Kindest Regards,SK
-
Have you got some very large dimensions in some/one of your AS databases? AS2K loads all dims in to memory and if you've got a lot of large ones, this could take some time. Have you reviewed what the memory usage is of the msmdsrv.exe process after it des finally start up?
Steve.
-
Hi Steve,
I have some very large Dimensions (400.000 Elements). After processing them I regularly do a restart of the OLAP Server, because of the memory leak. But I do this via script in a SQL Server Agent Job daily. This worked pretty well for a long time.
And can not be the problem. I could always restart the process and the dimensions did not grow much in the last time.
Best regards,
Stefan
Kindest Regards,SK
-
What service pack level do you have on your AS (not SQL)?
Are there any entries in any event logs related to AS? Part of the problem with AS2K (benefit of AS2k5!?!) is the lack of monitoring available. THere are some performance counters but i ca't think of any that could help diagnose this. You may want to look at them though. You may also want to use Process Monitor to view the msmdsrv.exe process when you start the service to see what it does (ie churn @ 100% cpu or maybe do nothing).
Steve.
-
Hi Steve,
as I told I have SP4 on the Analysis Services. I know that they have different installation routines under SQL 2000. 😉
The problem with the AS is that they need to much RAM. It's a 32bit Machine with 8G Ram. PAE and 3G switches are enabled. There are about 400 users using the OLAP service daily. When there is much traffic the OLAP Server eats much RAM until a certain point in time. Then the enty Memory is full is written to the event log. Then the only possiblility to get it to work again is to restart the service. This works in normal case.
But that it does not start and keeps on "starting" for such a long time is a new "feature".
Stefan
Kindest Regards,SK
-
Switch to AS2K5
or maybe go 64bit?I thought with a 32bit machine the process itself could access a max of 3gb? This means that the other 5gb, while avail to the OS and/or MSSQL, means nothing to AS. You could try to load the dims to the large/virt dim manager (thres a threshold somewhere to manage when this kicks in) but I have a feeling this was documented as *not* best practice for AS2K.
Have you checked the old (AS2K) Perf Guide to look for hints on how to optimize this?
Steve.
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply