MSRS Java Client

We tried to develop a MSRS Java Client to communicate with the MSRS server
via web services. Because of integrated windows authentication, we
encountered an access denial error. Has anyone encountered this problem and
know how to embed windows security in the Java client. By the way, I used
Apache Axis to create client stub classes from a WSDL file. I obtained the
WSDL file from the MSRS server directly.
Thanks,
JamesJames, I am trying to do exactly what you are describing and have run into
the same problem. Did you ever discover a solution?
Thanks!
"James" wrote:
> We tried to develop a MSRS Java Client to communicate with the MSRS server
> via web services. Because of integrated windows authentication, we
> encountered an access denial error. Has anyone encountered this problem and
> know how to embed windows security in the Java client. By the way, I used
> Apache Axis to create client stub classes from a WSDL file. I obtained the
> WSDL file from the MSRS server directly.
> Thanks,
> James|||Josh, James, I'm having this problem as well. Was there a solution?
"Josh Hensley" wrote:
> James, I am trying to do exactly what you are describing and have run into
> the same problem. Did you ever discover a solution?
> Thanks!
> "James" wrote:
> > We tried to develop a MSRS Java Client to communicate with the MSRS server
> > via web services. Because of integrated windows authentication, we
> > encountered an access denial error. Has anyone encountered this problem and
> > know how to embed windows security in the Java client. By the way, I used
> > Apache Axis to create client stub classes from a WSDL file. I obtained the
> > WSDL file from the MSRS server directly.
> >
> > Thanks,
> >
> > James|||Hey LT,
I did find a solution, but forgot to come back and mention it here.
The problem comes from the fact that we need to call the Render method
without specifying some optional parameters (like historyID). When you call
a Web Service API method from Java and leave out an optional parameter, the
SOAP message that is generated by AXIS can either exclude the tag for that
missing parameter or include the tag with a special attribute saying it's not
being used (xsi:nil="true"). The default for behavior for AXIS is to send
the tag with the special attribute but apparently Microsoft Reporting
Services doesn't want the tag sent at all. So you have to modify AXIS to
satisfy Reporting Services and stop sending tags for arguments that aren't
specified.
A much more detailed explanation is in this article written by a fella from
France. (You will have to register on their site to read the article)
http://www.sqlreportingservices.net/Tools/1996.aspx
Good luck!
"LT" wrote:
> Josh, James, I'm having this problem as well. Was there a solution?
> "Josh Hensley" wrote:
> > James, I am trying to do exactly what you are describing and have run into
> > the same problem. Did you ever discover a solution?
> >
> > Thanks!
> >
> > "James" wrote:
> >
> > > We tried to develop a MSRS Java Client to communicate with the MSRS server
> > > via web services. Because of integrated windows authentication, we
> > > encountered an access denial error. Has anyone encountered this problem and
> > > know how to embed windows security in the Java client. By the way, I used
> > > Apache Axis to create client stub classes from a WSDL file. I obtained the
> > > WSDL file from the MSRS server directly.
> > >
> > > Thanks,
> > >
> > > Jamessql

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
H
Little things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegro ups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSMQ & Integration Services

I have a SSIS package in SQL Server 2005 that attempts to publish some data into a MSMQ Private queue located on another machine.

While I was creating the package the connection string was pointing to the local server something like: localhost\private$\csin

Now I'm trying to get to the remote machine but I'm not sure what type of connection string I need to enter:

I tried: mw59\private$\csin where mw59 is the name of the remote machine I need to publish to but that result into a "Invalid Queue Path Name."

I tried: formatname:DIRECT=OS:mw59\private$\csin but that results in "The specified format name does not support the requested operation...."

Any idea?

Thanks,

Thierry

I haven't tried MSMQ in SSIS yet but I know that in SQL 2000 DTS the standard MSMQ task could not access remote private queues. I got around this with a couple of fairly simple/generic VBS tasks.

One task reads a text file into the message body and sends the message to a remote private queue. The second taks reads messages from the queue and merges them into a single text file. The next step in this tasks uses the text file source connection to read the data from the text file into a SQL table.

Dick Campbell

|||

The next Web update of Books Online, scheduled to coincide with Service Pack 1, contains an already-written new topic titled "Sending to a Remote Private Message Queue with the Script Task." Sadly, as we all know, it is not a pretty sight when one attempts to copy and paste the HTML of a BOL topic. Here is my best effort after converting it to plain text:

Sending to a Remote Private Message Queue with the Script Task

Microsoft Windows Message Queuing makes it easy for developers to communicate with application programs quickly and reliably by sending and receiving messages. A message queue may be located on the local computer or a remote computer, and may be public or private. The Integration Services MSMQ Connection Manager and Message Queue Task do not support sending to a private queue on a remote computer. However, by using the Script task, it is easy to send a message to a remote private queue.

Description

The following example uses an existing MSMQ connection manager, together with objects and methods from the System.Messaging namespace, to send the text contained in a package variable to a remote private message queue. The call to the AcquireConnection method of the MSMQ connection manager returns a MessageQueueTask object whose Send method accomplishes this task.

To configure this Script Task example

Create an MSMQ Connection Manager with the default name. Set its path to a valid remote private queue, in the following format:

FORMATNAME:DIRECT=OS:<computername>\private$\<queuename>

Create an Integration Services variable named MessageText of type String to pass the message text into the script. Enter a default message as the value of the variable.

Add a Script Task to the design surface and edit it. On the Script tab of the Script Task Editor, add the MessageText variable to the ReadOnlyVariables property to make the variable available inside the script.

Click Design Script to open the Visual Studio for Applications script editor.

Add a reference in the script project to the System.Messaging namespace.

Replace the contents of the script window with the code in the following section.

Imports System
Imports Microsoft.SqlServer.Dts.Runtime
Imports System.Messaging

Public Class ScriptMain

Public Sub Main()

Dim remotePrivateQueue As MessageQueue
Dim messageText As String

remotePrivateQueue = _
DirectCast(Dts.Connections("Message Queue Connection Manager").AcquireConnection(Dts.Transaction), _
MessageQueue)
messageText = DirectCast(Dts.Variables("MessageText").Value, String)
remotePrivateQueue.Send(messageText)

Dts.TaskResult = Dts.Results.Success

End Sub

End Class

-Doug

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 Ordinal 801 error

Afternoon,

I am trying to install Analysis Services on Win2k, and I am getting an error I don't know what to do with...

msmdsrv.exe - Ordinal not found
The ordinal 801 could not be located in the dynamic link library msjet40.dll.

I have tried:
uninstalling and re-installing Analysis Services
updating MDAC
deleting msjet40.dll and then updating MDAC

I'm at a loss... Can any suggest anything?

Thanks in advance!!Howdy

You may have to remove entries from the Registry to clean it up.

Cheers

SG

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

msdtssrvr.exe - sql 2005 sp2

Installed sp2 for sql 2005

cannot start msdtssrvr.exe

event viewer returns:

The SQL Server Integration Services service failed to start due to the following error:

The system cannot find the file specified.

I tried to locate the msdtssrvr.exe in C:\Program Files\Microsoft SQL Server\90\DTS\Binn\

I cannot locate the file .

Ron

You need to install SSIS from the installation media. The SSIS service is not installed by default, though I'm surprised you have a service listed for SSIS in the first place.

MSDTC Service

Hi,
I could not find MSDTC service from Control Panel --> Services for SQL
Server 2000 on Win 2000 and Win 2003. There are only MSSQLSERVER and
SQLSERVERAGENT 2 services. I need to change the startup account password. I
have changed password for SQL Server and SQL Server Agent account via SEM.
But there is not place to change password for MSDTC startup from SEM. MSDTC
is in Control Pannel -->Services for SQL 7.0. How can I find it for SQL 2000
on Win 2000 and Win 2003?
Thanks,
Julia
The name of the service is 'Distributed Transaction Coordinator". There is
only one instance per computer and does not appear in EM. Like all
services, it can be managed using the Services MMC.
The service runs under NT AUTHORITY\NetworkService by default. This is a
minimally privileged account so one usually doesn't need to change it.
Hope this helps.
Dan Guzman
SQL Server MVP
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:37C72C27-59EA-40BD-B3F9-DC209E642CF7@.microsoft.com...
> Hi,
> I could not find MSDTC service from Control Panel --> Services for SQL
> Server 2000 on Win 2000 and Win 2003. There are only MSSQLSERVER and
> SQLSERVERAGENT 2 services. I need to change the startup account password.
> I
> have changed password for SQL Server and SQL Server Agent account via SEM.
> But there is not place to change password for MSDTC startup from SEM.
> MSDTC
> is in Control Pannel -->Services for SQL 7.0. How can I find it for SQL
> 2000
> on Win 2000 and Win 2003?
> Thanks,
> Julia
>

MSDTC Service

Hi,
I could not find MSDTC service from Control Panel --> Services for SQL
Server 2000 on Win 2000 and Win 2003. There are only MSSQLSERVER and
SQLSERVERAGENT 2 services. I need to change the startup account password. I
have changed password for SQL Server and SQL Server Agent account via SEM.
But there is not place to change password for MSDTC startup from SEM. MSDTC
is in Control Pannel -->Services for SQL 7.0. How can I find it for SQL 2000
on Win 2000 and Win 2003?
Thanks,
JuliaThe name of the service is 'Distributed Transaction Coordinator". There is
only one instance per computer and does not appear in EM. Like all
services, it can be managed using the Services MMC.
The service runs under NT AUTHORITY\NetworkService by default. This is a
minimally privileged account so one usually doesn't need to change it.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:37C72C27-59EA-40BD-B3F9-DC209E642CF7@.microsoft.com...
> Hi,
> I could not find MSDTC service from Control Panel --> Services for SQL
> Server 2000 on Win 2000 and Win 2003. There are only MSSQLSERVER and
> SQLSERVERAGENT 2 services. I need to change the startup account password.
> I
> have changed password for SQL Server and SQL Server Agent account via SEM.
> But there is not place to change password for MSDTC startup from SEM.
> MSDTC
> is in Control Pannel -->Services for SQL 7.0. How can I find it for SQL
> 2000
> on Win 2000 and Win 2003?
> Thanks,
> Julia
>