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

KB485570: Platform Analytics Error Analysis dossier displays error messages with xxx instead of the specific error codes and/or error messages


Ramses Castro Cabrera

Senior Cloud Support Engineer II • MicroStrategy


Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
Description
In Platform Analytics, it is possible to see the error messages in the Error Analysis dossier with “xxx” in the Error column instead of an specific error code or a more tailed error message.

ka0PW0000001JiYYAU_0EM4W000005kmzk.png


Why is this happening?
 
The "xxx" message is commonly displayed in different versions of MSTR Platform Analytics. This is a normal behavior. The xxx are only a way to present the information displayed. Since the space in the rows is limited, this was though to not see the whole error message and fill the Error Analysis grid row space.
Solution
 
It is possible to see the actual error message by going to DB Query Tool and use the query select * from lu_status and check the timestamp of the error.
To look at the error timestamp it is necessary to add the attribute “timestamp” to the Error Analysis dossier. It is possible that the timestamp will be displayed as 12:00 AM.

ka0PW0000001JiYYAU_0EM4W000005kmzl.png


For any difficulty when seeing the actual timestamp, please go to ODBC Data Source administrator > System DSN > PLATFORM_ANALYTICS_WH > Configure > Advanced> Select the Fetch TSWTZ as timestamp box and apply the changes.

ka0PW0000001JiYYAU_0EM4W000005kmzm.png

 
Once that this configuration is performed correctly, it will be necessary to restart the I-Server and Trigger the Initial Load of Object Telemetry and refresh the Platform Analytics Cube. If this is done correctly, the timestamp will be visible in the Error Analysis Dossier.

ka0PW0000001JiYYAU_0EM4W000005kmzn.png


Finally, we can compare these timestamps with the output of the query

SELECT * FROM platform_analytics_wh.lu_status;
in DB Query Tool. In this way we can know to which error displayed as “xxx” corresponds each timestamp.

ka0PW0000001JiYYAU_0EM4W000005kmzo.png


 


Comment

0 comments

Details

Knowledge Article

Published:

June 30, 2022

Last Updated:

March 21, 2024