jcifs.smb.SmbException: The parameter is incorrect.

Jenkins JIRA | taril42 | 7 years ago
  1. 0

    Hudson Windows service slave launch causes SmbException

    Stack Overflow | 7 years ago | leander
    jcifs.smb.SmbException: The parameter is incorrect.
  2. 0

    [JENKINS-4564] Launch slave agent: jcifs SmbException - Jenkins JIRA

    jenkins-ci.org | 6 months ago
    jcifs.smb.SmbException: The parameter is incorrect.
  3. 0

    We've just added two new XP x64 slaves to our hudson, and we're seeing two types of jcifs SmbException when attemptint to "Launch slave agent". (JNLP works fine, but we'd prefer the master-managed service method.) The first occurs immediately after the slave is rebooted or after the "Server" service is stopped and restarted: Connecting to beast.example.com Copying slave.jar The parameter is incorrect. jcifs.smb.SmbException: The parameter is incorrect. at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:542) at jcifs.smb.SmbTransport.send(SmbTransport.java:644) at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:371) at jcifs.smb.SmbSession.send(SmbSession.java:235) at jcifs.smb.SmbTree.treeConnect(SmbTree.java:161) at jcifs.smb.SmbFile.doConnect(SmbFile.java:858) at jcifs.smb.SmbFile.connect(SmbFile.java:901) at jcifs.smb.SmbFile.connect0(SmbFile.java:827) at jcifs.smb.SmbFile.open0(SmbFile.java:917) at jcifs.smb.SmbFile.open(SmbFile.java:951) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:142) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:97) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:67) at jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2793) at hudson.os.windows.ManagedWindowsServiceLauncher.copySlaveJar(ManagedWindowsServiceLauncher.java:198) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:152) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:175) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:613) The second occurs thereafter -- very occasionally it does not have this error and works, but I'm not sure why: Connecting to beast.example.com Copying slave.jar 0xC0000205 jcifs.smb.SmbException: 0xC0000205 at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:542) at jcifs.smb.SmbTransport.send(SmbTransport.java:644) at jcifs.smb.SmbSession.send(SmbSession.java:242) at jcifs.smb.SmbTree.send(SmbTree.java:111) at jcifs.smb.SmbFile.send(SmbFile.java:729) at jcifs.smb.SmbFile.open0(SmbFile.java:934) at jcifs.smb.SmbFile.open(SmbFile.java:951) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:142) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:97) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:67) at jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2793) at hudson.os.windows.ManagedWindowsServiceLauncher.copySlaveJar(ManagedWindowsServiceLauncher.java:198) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:152) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:175) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:613) The JCIFS homepage suggests a newer version may have a fix: http://jcifs.samba.org/ "jcifs-1.3.10 released / Bugfix for SmbException: The parameter is incorrect posted by Mike, June 4, 2009 " We've also tried IRPStackSize registry key adjustments as recommended by microsoft/google when searching for the 0xC0000205 smb error; no luck here. The master is a MacOSX machine, the slaves are XP x64 machines (our XP32 machines don't seem to have this issue). We have been able to work around this by using JNLP to install the service; the service automatic startup seems to connect back to the master OK. Originally found on 1.323, but reproed (both cases) on 1.324. Feel free to holler if there's need for any additional information. Thanks in advance!

    Jenkins JIRA | 7 years ago | taril42
    jcifs.smb.SmbException: The parameter is incorrect.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    We've just added two new XP x64 slaves to our hudson, and we're seeing two types of jcifs SmbException when attemptint to "Launch slave agent". (JNLP works fine, but we'd prefer the master-managed service method.) The first occurs immediately after the slave is rebooted or after the "Server" service is stopped and restarted: Connecting to beast.example.com Copying slave.jar The parameter is incorrect. jcifs.smb.SmbException: The parameter is incorrect. at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:542) at jcifs.smb.SmbTransport.send(SmbTransport.java:644) at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:371) at jcifs.smb.SmbSession.send(SmbSession.java:235) at jcifs.smb.SmbTree.treeConnect(SmbTree.java:161) at jcifs.smb.SmbFile.doConnect(SmbFile.java:858) at jcifs.smb.SmbFile.connect(SmbFile.java:901) at jcifs.smb.SmbFile.connect0(SmbFile.java:827) at jcifs.smb.SmbFile.open0(SmbFile.java:917) at jcifs.smb.SmbFile.open(SmbFile.java:951) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:142) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:97) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:67) at jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2793) at hudson.os.windows.ManagedWindowsServiceLauncher.copySlaveJar(ManagedWindowsServiceLauncher.java:198) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:152) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:175) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:613) The second occurs thereafter -- very occasionally it does not have this error and works, but I'm not sure why: Connecting to beast.example.com Copying slave.jar 0xC0000205 jcifs.smb.SmbException: 0xC0000205 at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:542) at jcifs.smb.SmbTransport.send(SmbTransport.java:644) at jcifs.smb.SmbSession.send(SmbSession.java:242) at jcifs.smb.SmbTree.send(SmbTree.java:111) at jcifs.smb.SmbFile.send(SmbFile.java:729) at jcifs.smb.SmbFile.open0(SmbFile.java:934) at jcifs.smb.SmbFile.open(SmbFile.java:951) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:142) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:97) at jcifs.smb.SmbFileOutputStream.(SmbFileOutputStream.java:67) at jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2793) at hudson.os.windows.ManagedWindowsServiceLauncher.copySlaveJar(ManagedWindowsServiceLauncher.java:198) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:152) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:175) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:613) The JCIFS homepage suggests a newer version may have a fix: http://jcifs.samba.org/ "jcifs-1.3.10 released / Bugfix for SmbException: The parameter is incorrect posted by Mike, June 4, 2009 " We've also tried IRPStackSize registry key adjustments as recommended by microsoft/google when searching for the 0xC0000205 smb error; no luck here. The master is a MacOSX machine, the slaves are XP x64 machines (our XP32 machines don't seem to have this issue). We have been able to work around this by using JNLP to install the service; the service automatic startup seems to connect back to the master OK. Originally found on 1.323, but reproed (both cases) on 1.324. Feel free to holler if there's need for any additional information. Thanks in advance!

    Jenkins JIRA | 7 years ago | taril42
    jcifs.smb.SmbException: The parameter is incorrect.
  6. 0

    SMB deployer attempts to copy artifacts to top level of host, rather than share/subdir

    GitHub | 2 years ago | nskvortsov
    jcifs.smb.SmbException: The network name cannot be found.

    2 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. jcifs.smb.SmbException

      The parameter is incorrect.

      at jcifs.smb.SmbTransport.checkStatus()
    2. jCIFS
      SmbFile.getOutputStream
      1. jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:542)
      2. jcifs.smb.SmbTransport.send(SmbTransport.java:644)
      3. jcifs.smb.SmbSession.sessionSetup(SmbSession.java:371)
      4. jcifs.smb.SmbSession.send(SmbSession.java:235)
      5. jcifs.smb.SmbTree.treeConnect(SmbTree.java:161)
      6. jcifs.smb.SmbFile.doConnect(SmbFile.java:858)
      7. jcifs.smb.SmbFile.connect(SmbFile.java:901)
      8. jcifs.smb.SmbFile.connect0(SmbFile.java:827)
      9. jcifs.smb.SmbFile.open0(SmbFile.java:917)
      10. jcifs.smb.SmbFile.open(SmbFile.java:951)
      11. jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:142)
      12. jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:97)
      13. jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:67)
      14. jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2793)
      14 frames