# Stardog 5.2.1 on windows - ERROR StatusLogger **URL:** \ **Category:** Support\ **Created:** [February 15, 2018, 1:54pm UTC](https://community.stardog.com/t/stardog-5-2-1-on-windows-error-statuslogger/813 "2018-02-15T13:54:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mathib](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/mathib/32/345_2.png) [@mathib](https://community.stardog.com/u/mathib)\ **Post date:** [February 15, 2018, 1:54pm UTC](https://community.stardog.com/t/stardog-5-2-1-on-windows-error-statuslogger/813/1 "2018-02-15T13:54:51Z")
Hi, I recently updated my Stardog from v5.0.4 to v5.2.1, and ever since I’ve started stardog from the console, I get the following error: ``` ERROR StatusLogger Cannot locate file java.io.FileNotFoundException: C:\ (The system cannot find the path specified) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at org.apache.logging.log4j.core.config.ConfigurationFactory.getInputFromUri(ConfigurationFactory.java:289) at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:476) at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:420) at org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:265) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:613) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122) at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46) at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383) at com.complexible.stardog.Environment.(Environment.java:23) at com.complexible.stardog.cli.admin.CLI.main(CLI.java:185) [Fatal Error] :1:1: Content is not allowed in prolog. ERROR StatusLogger Error parsing C:\ org.xml.sax.SAXParseException; systemId: file:///C:/; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.apache.logging.log4j.core.config.xml.XmlConfiguration.(XmlConfiguration.java:95) at org.apache.logging.log4j.core.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:46) at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:491) at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:420) at org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:265) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:613) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122) at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46) at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383) at com.complexible.stardog.Environment.(Environment.java:23) at com.complexible.stardog.cli.admin.CLI.main(CLI.java:185) ERROR StatusLogger No logging configuration ``` I think this only affects the logging (all logging goes via the CLI now) so far. Stardog is running smoothly as for as I found out. Platform: Windows 10 Stardog: v5.2.1 CE ---
**Author:** ![stephen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/stephen/32/27_2.png) [@stephen](https://community.stardog.com/u/stephen)\ **Post date:** [February 15, 2018, 2:25pm UTC](https://community.stardog.com/t/stardog-5-2-1-on-windows-error-statuslogger/813/2 "2018-02-15T14:25:25Z")
Hi, Thanks for bringing this to our attention. There was a small bug introduced into our .bat scripts for 5.2.1 that you’ve run into. It will be fixed in the next release. In the meantime, if you copy $STARDOG/server/dbms/log4j2.xml into your $STARDOG\_HOME, this will go away and the default logging scheme will be used. ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)\ **Post date:** [March 1, 2018, 2:25pm UTC](https://community.stardog.com/t/stardog-5-2-1-on-windows-error-statuslogger/813/3 "2018-03-01T14:25:56Z")
Closed on March 1, 2018, 2:25pm UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.