title: SSAS Cube processing failed. returning trace information takes forever
body: <p>I'm using a small c# program to process SSAS databases using the C# API. The problem is that one of the cubes hangs under processing, and <code>Database.Process()</code> is a blocking call, meaning that the process hangs until killed through Process Explorer.</p>
  
  <p>If I do the processing manually, through SQL Server Management Studio, I get the following error: <code>Process failed. Trace information is still being transferred. If you do not want to wait for all of the information to arrive press Stop.</code> but the behavior is otherwise the same.  After 4 hours, still no trace information. If I press stop it tells me the connection was lost. But if the reason is the connection was lost, how come <code>Database.Process()</code> doesn't throw an exception?</p>
  
  <p>I have two questions:</p>
  
  <ol>
  <li>How do I start debugging this?</li>
  <li>Is there some way to programmatically (or otherwise) set a SSAS database to fail-fast without sending a seemingly infinite amount of trace information?</li>
  </ol>
  
  <p>I am using SQL Server 2008R2 if it makes any difference.</p>