MID Server Ignite work directory not created when install path contains spaces<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue The MID Server Ignite node fails to start and the Ignite work directory is not created when the MID Server installation path contains spaces. Symptoms Ignite node does not start after MID Server restartACC checks fail because Ignite is not runningIgnite work directory (MIDTemp/ignite/work) is not created on diskMID Server install path contains spacesNo explicit error in agent log Cause The Ignite work directory path derives from java.io.tmpdir, a Java system property set in wrapper-override.conf. When the path contains spaces, the unquoted space breaks JVM property parsing. Apache Ignite requires an absolute, valid path. Reference: KB0747569 Resolution Create a new directory with no spaces (e.g. C:\SN_MID_Server\ignite\work)Update wrapper-override.conf: set tmpdir to the new pathRestart the MID Server serviceVerify Ignite work directory was createdFor a permanent fix, reinstall MID Server to a path with no spaces