EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB4969: Reports take an unusually long time to run and may eventually exceed the job time limit set in MicroStrategy Intelligence Server when running reports in MicroStrategy Developer in 3-tier mode and in MicroStrategy Web 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Reports take an unusually long time to run and may eventually exceed the job time limit set in MicroStrategy Intelligence Server. Users may see the following error messages both in MicroStrategy Developer 10.x and in MicroStrategy Web 10.x: 'Error: The job execution time limit set in MicroStrategy Intelligence Server has been exceeded for job 85: at (1:23:56:968). The Job was cancelled'

SYMPTOM:
Reports take an unusually long time to run and may eventually exceed the job time limit set in Strategy Intelligence Server. Users may see the following error messages both in Strategy Developer 10.x and in Strategy Web 10.x:

ka02R000000kbb7QAA_0EM440000002GGs.gif

'Error: The job execution time limit set in Strategy Intelligence Server has been exceeded for job 85: at (1:23:56:968). The Job was cancelled'
POSSIBLE CAUSE:
When troubleshooting, users may set up to run Open Data Base Connectivity (ODBC) tracing on the Intelligence Server machine and may forget to stop the tracing and delete the trace file. The trace file can grow to a large size quickly and it is possible that this tracing slows down the machine.
 
ACTION:
In the control panel on the Intelligence Server machine, select the Data Source (ODBC) icon and choose the tracing tab. A dialog interface similar to the one below appears:

ka02R000000kbb7QAA_0EM440000002GGg.gif

Because tracing is likely to be the cause of this issue, if users have the option to stop tracing they should select to stop it. In addition, if the log file is finished, it should be deleted from the system. If users are not using ODBC tracing, they should contact Strategy Technical Support.


Comment

0 comments

Details

Knowledge Article

Published:

June 13, 2017

Last Updated:

June 13, 2017