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

KB483934: After performing a fresh install of MicroStrategy 2020 with a PostgreSQL warehouse on Windows, the Performance Troubleshooting Dossier returns an error when changing the filter selections


Jing (Sally) Cheng

Senior Principal Consultant • MicroStrategy


This article explains why an error may appear when viewing the new Platform Analytics Performance Troubleshooting Dossier after performing a fresh install of 2020 with a PostgreSQL warehouse on a Windows machine. This article also provides a solution.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Description

In Strategy 2020, Platform Analytics offers a new out-of-the-box dossier called the Performance Troubleshooting Dossier. This dossier can be used to analyze the breakdown of job step performance and SQL/CSI pass performance for each job. Additionally, Strategy 2020 also uses PostgreSQL as the Platform Analytics Repository.
You may notice that after you perform a fresh install on Windows with Strategy 2020 using a PostgreSQL warehouse that the Performance Troubleshooting Dossier encounters an error. More specifically, after changing the filter selection for Object Category on a Windows machine, executing the Performance Troubleshooting Dossier causes the following error to appear:
"Document execution fails. Error initializing data model from document instance, job 35, Error Code=.2147209146, Error Message=Internal System Error : Exception detected in %1 :: %2. %3)"

ka0PW0000001JcTYAU_0EM2R000000nHHm.jpeg

Why is this happening?

This error appears because the data has UTF-8 errors saved in the Platform Analytics cube.
When you publish an MTDI cube, the In Memory Engine will transform the source data from VarChar to UTF-8 to process it. Later, the data will be transformed back to VarChart to be viewed on the Client side. The error is appearing here because there is still data with UTF-8 errors in the Platform Analytics cube, so they cannot be processed by the Client.

Solution

To bypass this error, you need to add a registry to set the "Ignoring the UTF8 Errors" to ON

On Windows

  • Open the Registry Editor in the Intelligence Server.
  • Under 
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Strategy\Diagnostics
    , add a new DWORD (32-bit) Value.
ka0PW0000001JcTYAU_0EM2R000000nHIV.jpeg
  • Name the new DWORD Value IgnoreUTF8Error.
  • Give IgnoreUTF8Error the value 1. So it would be IgnoreUTF8Error=1.
ka0PW0000001JcTYAU_0EM2R000000nHIa.jpeg
  • Restart the Intelligence Server.

Alternatively, you can change the character set encoding to have Strategy use the right protocol to communicate with Driver in Strategy Developer.
Change the database instance settings for the Platform Analytics project (or the project you are seeing this behavior in). Set Character set encoding for Windows drivers to be Non UTF-8 for the database.
 

  • Open Developer.
  • Right-click on Platform Analytics > Project Configuration.
  • Go to Database instance > SQL Data warehouse > Platform Analytics Project > Modify.
  • From the list, select Platform Analytics Connection > Modify.
  • Go to the Advanced tab.
  • Under Table prefix, locate Character set encoding for Windows drivers.
  • Select Non UTF-8.
ka0PW0000001JcTYAU_0EM2R000000fPPQ.jpeg
  • Click OK.

Comment

0 comments

Details

Knowledge Article

Published:

December 23, 2019

Last Updated:

March 21, 2024