Connection to the SSAS Cubes

I have some users connecting to the cubes using excel, is there any way i can track which users aere connected to the cubes without using the Profiler/running a trace.

You can do an XMLA discover command to discover the current sessions/connections

<Discover xmlns="urnchemas-microsoft-com:xml-analysis">

<RequestType>DISCOVER_SESSIONS</RequestType>

<Restrictions>

<RestrictionList />

</Restrictions>

<Properties>

<PropertyList />

</Properties>

</Discover>

<Discover xmlns="urnchemas-microsoft-com:xml-analysis">

<RequestType>DISCOVER_CONNECTIONS</RequestType>

<Restrictions>

<RestrictionList />

</Restrictions>

<Properties>

<PropertyList />

</Properties>

</Discover>

But I think that the easiest way to run these commands is to use the Analysis Services Stored Procedure Project www.codeplex.com/asstoredprocedures where you can do the equivalent and get the results in an easy to read table form by doing

CALL ASSP.DiscoverSessions();

or

CALL ASSP.DiscoverConnections();

There was also an AMO Activity sample (or something like that) in the Analysis Services product samples that could show this sort of information.

Connection to Lan fails and locks server

Morning,
We have two nodes in a sql cluster. The "Lan" connection on one of the
servers fails at different times and I can't track down the problem and I am
not sure where to start.
I have changed NIC's Cables, Switches and still no luck..
Any suggestions where to start would be appreciated.
Thanks
Firmware? BIOS? Drivers? Called the vendors?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"James" <James@.discussions.microsoft.com> wrote in message
news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I
> am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks
|||Actually we had a DELL rep come out and set this up because we did not want
to mess with the SAN LUN's. He couldn't figure it out either. I will take a
look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
I noticed earlier that Network DTC was not installed on both servers so I
installed that see if maybe that will make a difference.
"Rodney R. Fournier [MVP]" wrote:

> Firmware? BIOS? Drivers? Called the vendors?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "James" <James@.discussions.microsoft.com> wrote in message
> news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
>
>
|||"James" <James@.discussions.microsoft.com> wrote in message
news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> Actually we had a DELL rep come out and set this up because we did not
want
> to mess with the SAN LUN's. He couldn't figure it out either. I will
take a
> look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
>
To ask the obvious... SP3a installed?
[vbcol=seagreen]
> I noticed earlier that Network DTC was not installed on both servers so I
> installed that see if maybe that will make a difference.
> "Rodney R. Fournier [MVP]" wrote:
the[vbcol=seagreen]
and I[vbcol=seagreen]
|||SP3 A is installed. Server failed again after 3 day. Network cards pass all
test? I will post some logs see if anyone has seen it before.
"Greg D. Moore (Strider)" wrote:

> "James" <James@.discussions.microsoft.com> wrote in message
> news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> want
> take a
> To ask the obvious... SP3a installed?
>
> the
> and I
>
>
|||Ok Here is the Cluster Log as soon as it fails I cannot figure this out. We
have had this problem for 3 weeks now, the amount of time it takes to fail
varies. Any help would be appreciated.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Reporting connectivity
to leader for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
completed successfully for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
worker thread finished.
000003c0.00000804::2004/12/30-14:53:46.531 INFO [GUM] s_GumUpdateNode:
dispatching seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:46.531 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is unreachable (node: Server1, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 is unreachable (node: Server2, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is down.
000003c0.00000804::2004/12/30-14:53:46.547 INFO [GUM] s_GumUpdateNode:
completed update seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:50.405 INFO [NM] Received request to get
online address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Found address
10.40.0.91 for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Received request to get
ping address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Received request to
ping targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging targets for
interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging host 10.40.0.1
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Ping of host 10.40.0.1
failed.
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Pinging host 10.40.0.182
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Ping of host
10.40.0.182 failed.
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Pinging host 10.40.0.2
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Ping of host 10.40.0.2
failed.
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Pinging host 10.40.0.7
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Ping of host 10.40.0.7
failed.
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Pinging host 10.40.0.39
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Ping of host 10.40.0.39
failed.
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Finished pinging
targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
dispatching seq 8885type 2 context 15
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is up (node: Server1, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 failed (node: Server2, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is up.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
completed update seq 8885type 2 context 15
"James" wrote:

> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks