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

KB486107: Storage Location cannot be configured with Azure Blob in Workstation as 'The storage location could not be connected' error


Shuyu Meng

Senior Cloud Support Engineer I • MicroStrategy


This article narrates the error "The storage location could not be connected. The API requires MicroStrategy Storage Service. Please contact your administrator" when trying to configure MicroStrategy Storage Service within Workstation.

Symptom 

When configuring the connection of Storage Location with Azure Blob in Workstation, the error message "The storage location could not be connected. The API requires Strategy Storage Service. Please contact your administrator" is shown below:

ka0PW0000000rh3YAA_0EM4W000005aImh.png

 
This issue happens on all client machines, and this Azure Blob Storage could be connected using Microsoft Azure Storage Explorer. 
In the Library log, found the following error message. 


"@timestamp":"2023-05-16T04:18:35.675Z","@version":"1","message":"Unexpected Library database error. Possible reason is that your database configuration (username, password, sslkeys...) is not correct or database server is down.","logger_name":"com.Strategy.rest.filters.DatabaseVersionCheckFilter","thread_name":"https-jsse-nio-8443-exec-49","level":"ERROR","level_value":40000,"stack_trace":"org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is java.sql.SQLTransientConnectionException: springHikariCPApplication - Connection is not available, request timed out after 10000ms.\ 

Cause 

It’s related to the SSL Mode specified in the configOverride.properties file. For more information, please refer to the PostgreSQL official website: https://www.postgresql.org/docs/current/libpq-ssl.html. 
 

Workaround 

Modify "datasource.sslMode=verify-full" to "datasource.sslMode=require" in configOverride.properties file, then restart the Web Application. 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 30, 2023

Last Updated:

February 26, 2024