I found out about a new "FEATURE" in SSAS 2008. The new feature is a server level lock. This lock will effectively stop clients from connecting to SSAS until the situation clears. Just what may this be? It seems that if you are doing any processing and it gets queued up behind another query that feels it is not obligated to yield. Its failure to be able to take a write lock forces all the requests for read locks to queue up behind it. And what does that do to your server? Interesting enough is that it will not only kill incoming requests but also chew up the memory on the server since it is not recycling the requests for a read lock as shown below.