java.io.IOException

The filename, directory name, or volume label syntax is incorrect

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web15552

  • via Pentaho BI Platform Tracking by Matt Tucker, 9 months ago
    The filename, directory name, or volume label syntax is incorrect
  • via Atlassian JIRA by Joe Wai Tye [Atlassian], 1 year ago
    The filename, directory name, or volume label syntax is incorrect
  • via Atlassian JIRA by Michael Orthey, 1 year ago
    The filename, directory name, or volume label syntax is incorrect
  • Stack trace

    • java.io.IOException: The filename, directory name, or volume label syntax is incorrect at java.io.WinNTFileSystem.canonicalize0(Native Method) at java.io.Win32FileSystem.canonicalize(Unknown Source) at java.io.File.getCanonicalPath(Unknown Source) at com.tecnomen.test.system.PropertyLoader.loadSystemProperties(PropertyLoader.java:101) at com.tecnomen.test.system.PropertyLoader.loadSystemProperties(PropertyLoader.java:62) at com.tecnomen.test.TestProperties.getInstance(TestProperties.java:89) at com.tecnomen.test.BaseTestCase.<init>(BaseTestCase.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader.getTest(JUnit3TestLoader.java:108) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader.loadTests(JUnit3TestLoader.java:59) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:444) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    2 times, 5 months ago
    16 more bugmates