org.jinterop.dcom.common.JIException

Message not found for errorCode: 0x8001FFFF

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 web313

  • Message not found for errorCode: 0x8001FFFF<br/>
  • via Jenkins JIRA by Robert Moore, 11 months ago
    Message not found for errorCode: 0x8001FFFF
  • via oschina.net by Unknown author, 1 year ago
    Message not found for errorCode: 0x8001FFFF
  • Stack trace

    • org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x8001FFFF at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:876) at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:825) at org.jinterop.dcom.core.JIComServer.addRef_ReleaseRef(JIComServer.java:909) at org.jinterop.dcom.core.JISession.releaseRef(JISession.java:730) at org.jinterop.dcom.core.JIComServer.createInstance(JIComServer.java:746) at org.jvnet.hudson.wmi.WMI.connect(WMI.java:61) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:152) at hudson.slaves.DelegatingComputerLauncher.launch(DelegatingComputerLauncher.java:56) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:199) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:736) Caused by: java.net.SocketException: Network is unreachable at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:519) at java.nio.channels.SocketChannel.open(SocketChannel.java:157) at org.jinterop.dcom.transport.JIComTransport.attach(JIComTransport.java:98) at rpc.Stub.attach(Stub.java:104) at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:860) ... 13 more

    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