KB42658: "An internal error has occurred in the Analytical Engine" error message appears when executing a report with an attribute in page by in MicroStrategy Desktop 9.2.1m against Microsoft SQL Server 2008 R2 data Warehouse

SYMPTOM:
"An internal error has occurred in the Analytical Engine" error message appears when executing a report with an attribute in page by in Strategy Desktop 9.4.1 against Microsoft SQL Server 2008 R2 data Warehouse, as shown below:

An internal error has occurred in the Analytical Engine.
STEPS TO REPRODUCE: 
The following steps demonstrate how to reproduce this issue in tutorial project:

• Create a table "TestTable" with a date column "TestColumn1" with date value in Microsoft SQL Server 2008 R2 database with scripts as shown below:
  

  
  Create Table TestTable (TestColumn1 Date);
  Insert into TestTable Values ('2008-08-22');
  
  

  
  
• Create a database instance in tutorial project to connect with this database. Set "Database connection type" as "Microsoft SQL Server 2008 with Native Client Driver" as shown below:
  

• Import TestTable into project in Warehouse Catalog. Show sample data of TestTable and get error message as shown below:
  

• 
  Error processing table structure Type mismatch
  
  

  
  
• Create an attribute "Attribute1" mapping to TestColumn1 with Date form format. Create a report with Attribute1. The report can be executed successfully if Attribute1 is in Rows or Columns. Move Attribute1 to page by and report execution will fail with error message as shown below:
  

  
CAUSE:
This is a known issue with Strategy Desktop 9.4.1 against Microsoft SQL Server 2008 R2 data warehouse.
WORKAROUND:

• Show sample data in Architect. This will not get any error.
• Change the data type of the column from date to datetime in data warehouse. This can avoid the Analytical Engine error when attribute is put in page by field. In the example above, if changing the data type of TestColumn1 as datetime in warehouse and keeping the form format as date in attribute editor, the report with Attribute1 in page by can be executed successfully as shown below: