KB484250: Troubleshooting metadata creation issues

If you encounter the following errors or issues when creating a metadata, review the troubleshooting techniques described in this article. 

• Locale and time formatting issues
• Missing demanded settings in DSN

Issue 1: Locale and time formatting issues [Linux only]

If your system's locale does not support a certain time format when creating the metadata, you may encounter a creation failure with the following error:
Configuration creation failed. See error log for reason of failure. Correct the error and rerun the configuration wizard again. 

Troubleshoot

1. Check the

   DSSErrors.log 

   for Server in the installation folder

   /MicroStrategy/log.

    There are no other specific errors other than: ERROR: VERROR;table "dsscsdspropt" does not exist.
2. Check the

   DSSErrors.log

   in the installation folder

   /MicroStrategy/log/Instances/DUMMY_SERVER

   :
   
• Prior to Strategy 2020 Update 2, there is no error log.
• Starting in Strategy 2020 Update 2, you can find a special error log like:

  [SERVER:DUMMY_SERVER][PID:15519][THR:139738750351104][COM Shared][UID:0][SID:0][OID:0] Failed to parse date time: 2014-03-03

  . 

Solution

Change the system language for the machine.

1. Open the terminal and run the command

   locale

   to check the current system locale. 
2. Change the system locale to English-US or another supported locale by running the command: 

   ocalectl set-locale LANG=en_US.UTF-8

   .
   The two known languages that have this issue are English-New Zealand and English Australia.
   
3. Reboot the system to apply the changes.

Issue 2: Missing demanded setting in DSN [PostgreSQL only]

When creating a metadata in a PostgreSQL database version 9.1 or later, with a server older than Strategy 2020, your may receive the following error: 
Configuration creation failed. See error log for reason of failure. Correct the error and rerun the configuration wizard again. 

Troubleshoot

Check the

DSSErrors.log

/MicroStrategy/log

Solution   

In the ODBC Data Source Administrator, set the InitailizationString parameter to SET STANDARD_CONFORMING_STRINGS TO OFF. For detailed instructions, see KB441192.
If you are still encountering issues, contact Technical Support for assistance and provide the following: 

• Database type
• Production version

• DSSErrors.log(s)

• MACfgWiz.xml

Related Articles

KB483356: Troubleshooting Metadata Upgrade Issues