mssearch.exe has high CPU usage

Hello-
Normally our mssearch.exe CPU is less than 5% even at peak times, and
falls to 0 at night. But for the last few days mssearch.exe CPU usage
remains close to 25% even when all the catalogs are idle and search
queries are very infrequent.
This happened a few months ago, and was fixed only by restarting
mssearch.exe. This time I'd like to discover what is causing the
problem. How can I figure out what mssearch.exe is doing?
SQL Server 2000 sp4 on Windows 2003 Server sp1, 4-processor, in an
active-active cluster, 3.5GB memory. 6 tables all with "Update Index in
background" option, each in their own catalog. The largest is 417MB
from 350k rows, the rest are much smaller.
Thanks for your help!
-Steve
www.vin.com
You can trace any SQL related activities of the MS Search service by running
SQL Profiler.
Perhaps - provided you're using task manager - what you see is the MS Search
service indexing your file system.
ML
http://milambda.blogspot.com/
|||Those are good suggestions, so thanks, but nothing was showing up on
profiler or perfmon that I could see, and nothing in the regular
filesystem was being indexed.
Here's how I resolved this, and it turns out that another issue I'd
been having was related to this one. There was a sql process (a
normally quick FT query) that was hanging for a couple of days and was
not responding to the KILL request. In the wee hours I restarted
mssearch.exe, the CPU dropped down to it's typical nearly nothing, and
the unkillable process finally dies. So I suppose mssearch was running
rampant and had locked up a sql process. Glad that's over but wish I
knew what caused mssearch to bork.
Cheers,
Steve
ML wrote:
> You can trace any SQL related activities of the MS Search service by running
> SQL Profiler.
> Perhaps - provided you're using task manager - what you see is the MS Search
> service indexing your file system.

mssearch.exe CPU utilization increased with SP4

Hi,
after installing SP4 I am having trouble with mssearch.exe using excess
CPU. Typically all is fine for some hours, then the utilization jumps
up to 60% and more. mssearch.exe can then only be stopped via killing
the process. After a restart all is fine again.
Any known problems with SP4 and the Fulltext engine?
TIA, Regards
DC
None that I am aware of - however have you checked the gatherer logs to
determine what is happening at this point? You can enable logging for more
details about exactly what is happening in this timeframe.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"DC" <dc@.upsize.de> wrote in message
news:1136211283.315556.324940@.f14g2000cwb.googlegr oups.com...
> Hi,
> after installing SP4 I am having trouble with mssearch.exe using excess
> CPU. Typically all is fine for some hours, then the utilization jumps
> up to 60% and more. mssearch.exe can then only be stopped via killing
> the process. After a restart all is fine again.
> Any known problems with SP4 and the Fulltext engine?
> TIA, Regards
> DC
>
|||Hi,
thanks for the hint, Hilary. I have rebuild all Fulltext Catalogs from
scratch and that seems to have solved my problem.
Regards
DC

Mssearch.exe consuming High CPU over extended time period

Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you

No solution to your particular problem, except looking at a prioir post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

This may help understand the problem.

Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.

Mssearch.exe consuming High CPU over extended time period

Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you

No solution to your particular problem, except looking at a prioir post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

This may help understand the problem.

Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?
|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.

mssdmn consuming cpu and memory

I have a sql 2000 SP4 server with two processors that has started to consume
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
ThanksThis is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ureader.com...
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks

mssdmn consuming cpu and memory

I have a sql 2000 SP4 server with two processors that has started to consume
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
Thanks
This is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ureader.com. ..
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
sql

mssdmn consuming cpu and memory

I have a sql 2000 SP4 server with two processors that has started to consume
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
ThanksThis is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ur
eader.com...
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks

msmdsrv.exe takes more than 95% cpu

Hi,
The process msmdsrv.exe (ver 8.00.2039) takes more than 95% cpu. The PC is
very very slow. What can I do? I have SP4 for Analysis Services installed.
I thought SP4 could correct the problem but it did not.
When I looked at the Analysis Services in MMC, the PC icon had a small red
square, which indicates the Analysis Services was not running. I did not
connect to it, since the PC was nearly halted.
Please help me!
Thanks.
Actually msmdsrv *IS* Analysis Services. It is the service.
So it is running -- regardless of what the icon is saying. This just means
that the service APIs cannot detect that it is in a running state. Typically
msmdsrv going into a high CPU loop when the lazy aggregator is running (i.e.
someone kicked off a changing dimension incremental process and the flex
aggs are being reprocessed), or a full processing is being done for a
specific cube, etc.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chrissi" <anubisofthydeath@.hotmail.com> wrote in message
news:uuLYlX6cFHA.2420@.TK2MSFTNGP12.phx.gbl...
> Hi,
> The process msmdsrv.exe (ver 8.00.2039) takes more than 95% cpu. The PC
> is very very slow. What can I do? I have SP4 for Analysis Services
> installed. I thought SP4 could correct the problem but it did not.
> When I looked at the Analysis Services in MMC, the PC icon had a small red
> square, which indicates the Analysis Services was not running. I did not
> connect to it, since the PC was nearly halted.
> Please help me!
> Thanks.
>
|||Do you have a solution to this problem? My OS is windows 2000 server. I
have another PC with Analysis Services. The msmdsrv.exe does not take cpu.
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23qC1fGfdFHA.2696@.TK2MSFTNGP09.phx.gbl...
> Actually msmdsrv *IS* Analysis Services. It is the service.
> So it is running -- regardless of what the icon is saying. This just means
> that the service APIs cannot detect that it is in a running state.
> Typically msmdsrv going into a high CPU loop when the lazy aggregator is
> running (i.e. someone kicked off a changing dimension incremental process
> and the flex aggs are being reprocessed), or a full processing is being
> done for a specific cube, etc.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI SystemsTeam
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Chrissi" <anubisofthydeath@.hotmail.com> wrote in message
> news:uuLYlX6cFHA.2420@.TK2MSFTNGP12.phx.gbl...
>
|||I had the same problem albiet under Windows XP. I resolved it by:
1: Go to Control Panel/Admin Tools/Services. Find the
MSSQLServerOLAPService, choose properties and check the 'Allow service to
interact with desktop' checkbox.
2: Allow the msmdsrv.exe file through your firewall (file typically found in
the \program files\Microsoft Analyst Service\bin\ folder.
I'm not sure if 2: is required but it seemed to help.
This resolved the problem - I'm not technically competent enough to know why
but it worked!
Good luck.
"§Chrissi§" wrote:

> Do you have a solution to this problem? My OS is windows 2000 server. I
> have another PC with Analysis Services. The msmdsrv.exe does not take cpu.
> "Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
> news:%23qC1fGfdFHA.2696@.TK2MSFTNGP09.phx.gbl...
>
>

msmdsrv.exe takes more than 95% cpu

Hi,
The process msmdsrv.exe (ver 8.00.2039) takes more than 95% cpu. The PC is
very very slow. What can I do? I have SP4 for Analysis Services installed.
I thought SP4 could correct the problem but it did not.
When I looked at the Analysis Services in MMC, the PC icon had a small red
square, which indicates the Analysis Services was not running. I did not
connect to it, since the PC was nearly halted.
Please help me!
Thanks.Actually msmdsrv *IS* Analysis Services. It is the service.
So it is running -- regardless of what the icon is saying. This just means
that the service APIs cannot detect that it is in a running state. Typically
msmdsrv going into a high CPU loop when the lazy aggregator is running (i.e.
someone kicked off a changing dimension incremental process and the flex
aggs are being reprocessed), or a full processing is being done for a
specific cube, etc.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chrissi" <anubisofthydeath@.hotmail.com> wrote in message
news:uuLYlX6cFHA.2420@.TK2MSFTNGP12.phx.gbl...
> Hi,
> The process msmdsrv.exe (ver 8.00.2039) takes more than 95% cpu. The PC
> is very very slow. What can I do? I have SP4 for Analysis Services
> installed. I thought SP4 could correct the problem but it did not.
> When I looked at the Analysis Services in MMC, the PC icon had a small red
> square, which indicates the Analysis Services was not running. I did not
> connect to it, since the PC was nearly halted.
> Please help me!
> Thanks.
>|||Do you have a solution to this problem? My OS is Windows 2000 server. I
have another PC with Analysis Services. The msmdsrv.exe does not take cpu.
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23qC1fGfdFHA.2696@.TK2MSFTNGP09.phx.gbl...
> Actually msmdsrv *IS* Analysis Services. It is the service.
> So it is running -- regardless of what the icon is saying. This just means
> that the service APIs cannot detect that it is in a running state.
> Typically msmdsrv going into a high CPU loop when the lazy aggregator is
> running (i.e. someone kicked off a changing dimension incremental process
> and the flex aggs are being reprocessed), or a full processing is being
> done for a specific cube, etc.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI SystemsTeam
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Chrissi" <anubisofthydeath@.hotmail.com> wrote in message
> news:uuLYlX6cFHA.2420@.TK2MSFTNGP12.phx.gbl...
>|||I had the same problem albiet under Windows XP. I resolved it by:
1: Go to Control Panel/Admin Tools/Services. Find the
MSSQLServerOLAPService, choose properties and check the 'Allow service to
interact with desktop' checkbox.
2: Allow the msmdsrv.exe file through your firewall (file typically found in
the \program files\Microsoft Analyst Service\bin\ folder.
I'm not sure if 2: is required but it seemed to help.
This resolved the problem - I'm not technically competent enough to know why
but it worked!
Good luck.
"§Chrissi§" wrote:

> Do you have a solution to this problem? My OS is Windows 2000 server. I
> have another PC with Analysis Services. The msmdsrv.exe does not take cp
u.
> "Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
> news:%23qC1fGfdFHA.2696@.TK2MSFTNGP09.phx.gbl...
>
>sql

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?
|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.
|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?
|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.
|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?
|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.
|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings

sql

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings

msmdsrv.exe is taking 99% cpu

I've tried rebooting the server, restarting services, etc, but that only seems to help for about 5-10mins.

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed. Is there a way to narrow down what (and why) might be causing that process to hog so much CPU time and making the whole server slow?

I have seen this problem before; and I remember the solution was to apply the latest service pack for Analysis services. SP4.

Which service pack are you running?
|||

So sorry I didn't include that info.

SSAS 2005 , SP1
1.8Ghz, 1.5gb ram with around 5 users connecting.
The memory usage wasn't at all bad when this happened. The msmdsrv.exe process took about 35mb of RAM, and there was 800-950mb free, but the cpu was at its peek.

|||

This happens during quering of the cube and not the processing?

I suggest that you download the Performance Guide which is pointed to at the top post in this message group.

Are you using any real time update of the cube or is it a full MOLAP in all dimensions and in the measure groups?

Regards

Thomas Ivarsson

|||

tee_user5 wrote:

When the cpu usage was that high, I profiled the cube for a 3 minute period and no queries were being performed.

The whole server is slow when this happens, not just AS.

Right now the server is operating much better and msmdsrv is using 300mb. I'm not sure why it wasn't using more ram yesterday.

Note: sqlserver is also on this server and it's not an option to move it at this time. It is now using 600mb of ram when the server is stable.

Update:
I just saw the msmdsrv process take 900mb+, leaving the available amount of memory less than 1mb. Then what happened is that msmdsrv released the memory and then cranked on the cpu. It's now at 99%.

If I look at the event logs, there is an out of memory error logged from today (it's in there for yesterday as well)
--

Event Type: Information
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 2
Date: 2/16/2007
Time: 10:12:31 AM
User: N/A
Computer: name
Description:
The system is out of memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

--
I understand that it would be advisable to add more memory - but I'm not sure how quick that can be done. Also, why did the process basically give up? It had 900mb of memory, but then it dropped it all and worked down the cpu and continues to crank on it at 99%

|||

More info:

When the server acted up, it was always from the same user. I looked at their setup, and their permissions are done through windows domain groups and the 2 groups in which the user is placed put them in 2 different roles - which each have access to 1 section of a customer region. I took the person out of one of the roles and tried access again - there was no slowness on the server. Any clue as to why something like this would happen with 2 roles hooked up?

|||

I can recreate the problem by putting a test user in 2 different Cube roles - this doesn't even involve windows groups nor any measures!

Each role is for 1 region - east and central.

When I plop on the region attribute for a display, the server starts to take a dive.
Note: only the region attribute was used. I would expect 2 different regions to show. Here is the code that the cube browser creates:

CREATE SESSION
SET [sales].[{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0] AS
'
{
{ [Customer].[Region].[All] },
AddCalculatedMembers([Customer].[Region].[Region].MEMBERS)
}
'

SELECT
NON EMPTY [{AF0CD6C2-0256-4225-AE4C-CF8C3091654D}Pivot2Axis1Set0]
DIMENSION PROPERTIES MEMBER_NAME, PARENT_UNIQUE_NAME ON COLUMNS
FROM [sales]
CELL PROPERTIES VALUE, FORMATTED_VALUE, FORE_COLOR, BACK_COLOR

I'm going to see if SP2 helps, but please throw out any ideas. This problem is detrimental to the server.

|||

It is very hard to tell anything about your problem without knowing more about the limit of RAM on your server and how complex the cube is, regarding number of dimensions and each fact table size(number of records) in the cube.

Regards

Thomas Ivarsson

|||

That info was in my 3rd post.
There is little complexity because we have only 3 regions and I could create the problem just by looking at that attribute.

SP2 seems to have fixed the issue, but I'm needing to do more involved testing to make sure it's no longer an issue.

|||Hi

I'm having a similar problem. I have a machinne with 2 fisical processors and two logical, 4GB of memory RAM and 800 GB of free disc space. I'm describing Power Eddge Dell Server. The problem apears when a user perform a query to the cube, no matter the client tool used to make the query the server uses all it's memory and processor capacity an then pased a few minutes It aborts the operation and disconect any user. At this moment they are using Officce Web Component but I'm using the SQL's browser and I have the same problem.

I've made some test using two diferent machins. One of them with SQL Server 2005 SP1 y the other one with SQL Server 2005 SP2 and the results are 100% similar.

I really apreciate if anyone can help me. Thank you very much.
|||

does it differ any if the simpliest query is executed?

select from [cube name]

|||

It does not differ depending the complexity of the query. I get the problem, sometimes, only changing then members of a dimention, already included in the query. At this moment the case is on Microsoft Support Engeneers hands. If I receive a useful response from them I will let you know about it.

Thank you very much for your help.

|||

Hi,

I'm afraid I'm facing the same issue.

We are running a 64bit W2003 Server Enterprise with SQL2005 Enterprise Edition (64bit, SP2) on it. The System has 4 CPUs and 8GB of RAM. On the system we are running a Datawarehouse and a SSAS DB.

Now for the error: When I query an OLAP Cube (no mather if with Excel, OWC or the internal Cube Browser in VS) the client application randomly stops responding and you can see that one of the 4 CPUs is peaked on 100% and the memory consumed by SSAS is constantly increasing.

The memory consumption goes up to about 7,5 GB RAM, then the memory is paged (I can see an entry in the event log) and the memory is increasing again, now starting vom 100K Memory. The whole system also is non-respondive in these cases, you can hardly work on the system. The only sol?ution i found so far is restarting the SSAS Service.

The occurace of this error is not bound to a special query or complexity ... after about 5 minutes of "normal" analysis (drilldown, filter, ...) the problem occurs.

Is there an updated information about this issue available?

Greetings Montechristo

|||

We also have this problem.

Using a Intel Xeon QuadCore 3.4 GHz CPU with 3.5 GB ram and W2003Server, SQL2005 SP2.
SSAS and SSRS on the same server.

After a while (at least once a day, with 30 something users average a day) the msmdsrv.exe climbes to ~33% usage on each core.
It also eats up almost all available memory.

Only a restart on SSAS releases it.

During the "hangup" a "SQL server profiler"-session shows no activity.

Any idas?

|||

Since there seem to be a lot of implementations that suffer from this issue, is there any official comment/workaround/solution to this problem available?

Greetings