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

KB423967: When running a report in Web using Integrated Authentication, the error “Error in Process method of Component: QueryEngineServer” shows.


Monica Gallegos Salazar

Principal Product Specialist • MicroStrategy


This is a document that explains a certain issue when using Integrated Authentication to authenticate to the Database; the error “Error in Process method of Component: QueryEngineServer” will show in MicroStrategy Web.

SUMMARY
This issue has been classified as a defect by Strategy.  The impact is limited to the Strategy 10.4 HF1 and 10.5 product when running a report in Web using Integrated Authentication all the way to the Database. A solution/code fix for this issue is available in current releases.
SYMPTOM
When a report is run in Web, the following error is encountered:


“Error in Process method of Component: QueryEngineServer … ErrorCode= -21474677259”

In the Web log, the following error can be seen:

"Your request could not be processed due to a server error. Please try again. If the problem persists, contact your Administrator. (Error in Process method of Component: QueryEngineServer, Project SAP BI, Job 7888, Error code= - 2147467259.)"

The report runs correctly in Developer, using the same type of authentication.
This issue is specific to environments where the Database being used as a Warehouse requires authentication via Integrated Authentication (Kerberos).
STEPS TO REPRODUCE

  1. Login to Strategy Web using Integrated authentication.
  2. Run any report that has to run against the Warehouse.
  3. Notice the error mentioned above shows.

CAUSE
This is a known issue in Strategy Web 10.4 HF1 and 10.5.
ACTION
This issue has been fixed in Strategy Web 10.4 HF2 and 10.6. To take advantage of the fix for this issue, upgrade to one of those versions.   KB423967


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

December 31, 2018