MicroStrategy 7 Administrator Guide

2. Entry for [05/29/2000::14:52:00:16] shows that the report execution
has started in the Report Executor.
3. Entry for [05/29/2000::14:52:00:26] shows that the Resolution Server is
now examining the report instance.
4. Entry for [05/29/2000::14:52:00:456] shows that the report instance
has prompts that need to be resolved.
5. Entry for [05/29/2000::14:52:09:629] shows that we are answering
prompts.
6. Entry for [05/29/2000::14:52:09:629] shows that we are requesting
execution of the report instance which has prompt answers.
7. Entry for [05/29/2000::14:52:09:639] shows that the report executor is
executing the report instance.
8. Entry for [05/29/2000::14:52:09:639]shows that the report executor is
requesting for Resolution Server.
9. Entry for [05/29/2000::14:52:09:649]The prompts are marked as
closed.
10. Entry for [05/29/2000::14:52:09:659]shows that the Report Executor is
requesting for Resolution Server
11. Entry for [05/29/2000::14:52:09:690] shows that the report executor is
requesting for SQL Generation for ReportInstance - a call is made to the
SQL Engine at this point.
12. Entry for [05/29/2000::14:52:15:999]shows that the report executor is
requesting for Query Engine
13. Entry for [05/29/2000::14:52:20:826]shows that the report executor is
requesting for Analytical Engine
14. Entry for [05/29/2000::14:52:21:146] shows that the report executor
has completed executing the ReportInstance
15. Entry for [05/29/2000::14:52:21:146] shows that the Report Server has
finished Executing the report instance.
A
P
P
E
N
D
I
X
E
S
Sample log file 221