If the service is not responding, check the SSAS log:
If one session is not responding, open an MDX window in SSMS and run the following:
SELECT * FROM $system.discover_sessions
ORDER BY session_used_memory DESC
If looking for active sessions, filter by:
Question: How To differentiate between queries and SSAS processing commands? Run a simple processing and check the SESSION_LAST_COMMAND.
If looking for heavy sessions: Identify the session by its user or its memory consumption, then check its SPID and its query from SESSION_LAST_COMMAND column, then/or cancel it:
<?xml version=“1.0” encoding=“UTF-8”?>
Commands belong to 1 session
Sessions belong to one connection.
A connection is run by one user and host.
To discover which connections, sessions, or commands are running, run these on an MDX screen:
SELECT * FROM $SYSTEM.DISCOVER_CONNECTIONS
SELECT * FROM $SYSTEM.DISCOVER_SESSIONS
SELECT * FROM $SYSTEM.DISCOVER_COMMANDS