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

KB484018: Windows Kafka could not be started due to file system errors in MicroStrategy 2019 Update 2 and up


Scott Rowley

Director, Application Security Engineering • MicroStrategy


This article explains why the Apache Kafka service cannot be started in MicroStrategy 2019 Update 2 and up on Windows. This article also provides a solution to this error.

Description 


In Strategy 2019 Update 2 and later versions, the Apache Kafka (Telemetry Server) service cannot be started on Windows, or frequently crashes. 

ka04W000001Iw1SQAS_0EM2R000000ngpt.jpeg

Entries similar to those relating to file system operation failures are recorded in the Kafka server log in the Messaging Services folder:

C:\Program Files (x86)\Strategy\Messaging Services\Kafka\kafka_2.11-1.1.0\logs\kafka\server.log

 

  • FileSystemException: The process cannot access the file because it is being used by another process
  • FileAlreadyExistsException for Replication-offset-checkpoint file
  • java.io.IOException: The requested operation cannot be performed on a file with a user-mapped section open
  • ERROR Shutdown broker because all log dirs in E:\Program Files (x86)\Strategy\Messaging Services\tmp\kafka-logs have failed (kafka.log.LogManager)

Why is this happening?

This is caused by a related defect in Apache Kafka where file system operations fail. These errors can occur after the service has been running for some time, or on startup. 
For details, see this Apache Kafka article. 
 

Solution


If you are on Strategy 2019 Update 1 or older versions, please see KB441447, and update to Strategy Update 2 or a new version. This contains a fix and resolves the issue for most impacted systems. 
If you are on Strategy 2019 Update 2 and up, including Strategy 2020, and are still experiencing this issue, please contact Strategy Technical Support.


Comment

0 comments

Details

Knowledge Article

Published:

January 31, 2020

Last Updated:

July 5, 2022