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

KB483661: After upgrading to MicroStrategy 2019 Update 2, the Intelligence Server is slow to start when the operating system timezone is set to UTC + 10:00 / UTC + 11:00 / UTC + 12:00


Yating (Tiffanie) Zhai

Senior Cloud Support Engineer III • MicroStrategy


This article details why the Intelligence Server is slow to start after upgrading to MicroStrategy 2019 Update 2 when your Windows OS timezone is set to UTC + 10:00 / UTC + 11:00 / UTC + 12:00. This article provides a solution and a workaround.

Description 


After upgrading from Strategy 2019 Update 1 to Strategy 2019 Update 2, it takes much longer to start the Intelligence Server. 
In 2019 Update 1, it took one minute to load three projects. In 2019 Update 2, it takes eight minutes to load the same three projects from the same metadata. However, when the timezone settings are changed, the server loads quickly again.

Steps to Reproduce

  1. On a Windows machine with a timezone of UTC + 10:00 / UTC + 11:00 / UTC + 12:00 and Strategy 2019 Update 1, ensure the Intelligence Server is configured to connect to the metadata.
  2. Start the Intelligence Server. Notice it takes one minute to start.
  3. Install Strategy 2019 Update 2.
  4. Configure the Intelligence Server to connect to the same metadata and load the same projects. Notice it takes eight minutes to start the server.
  5. Change the timezone to UTC - 5:00 (EST) and start the Intelligence Server again. Notice it only takes one minute to start.

Why is this happening?


During the Intelligence Server startup, the database connection cache is expired at the moment it was created. In this instance, the server is incorrectly using the coordinated universal time to calculate the database connection cache expiration time but using the local time to check whether the database connection is expired or not. 
This issue can be reproduced if the timezone is set to UTC + 10:00 / UTC + 11:00 / UTC + 12:00.
 

Solution


This issue has been fixed in Strategy 2019 Update 3. To take advantage of the fix, upgrade to the latest version of Strategy.

Workaround


For an immediate solution, you can modify the timezone of the Intelligence Server operating system to UTC-5 (EST).
There is no need to change the timezone on the client machine since Strategy supports different timezones between the Intelligence Server and clients.


Comment

0 comments

Details

Knowledge Article

Published:

September 26, 2019

Last Updated:

September 26, 2019