How to resolve Data Virtualization Studio connection failure with error 'Cause: host.docker.internal: Name or service not known'?

How to resolve Data Virtualization Studio connection failure with error 'Cause: host.docker.internal: Name or service not known'?

book

Article ID: KB0137871

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization All supported versions

Description

Data Virtualization(DV) Studio connection fails with error - An internal error has occurred. Cause: Connection Failed. 

image.png

Studio.log file shows the following error trace - 

ERROR [jetty thread pool-44] 2025-07-17 21:43:11.241 +0000 Util - User Exception Occurred
com.compositesw.common.UserException: An internal error has occurred.
Cause: An internal error has occurred.
Cause: host.docker.internal: Name or service not known [Log ID: 56b310f5-c32c-4693-bea3-c5cf873aa958]  [Log ID: b9946e5a-34a3-4b45-8e28-4f3650d3828e]
        at com.compositesw.common.UserException$Builder.build(UserException.java:169) ~[cscommon-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.Util.createWebapiException(Util.java:91) ~[cswebapi-server-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.Util.createWebapiException(Util.java:77) ~[cswebapi-server-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.WSessionImpl.startSession(WSessionImpl.java:602) ~[cswebapi-server-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.WSystemImpl.getSession(WSystemImpl.java:256) ~[cswebapi-server-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.WMetaDataImpl.system_getSession(WMetaDataImpl.java:1120) ~[cswebapi-server-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.WMetaDataSvc_Tie.invoke_system_getSession(WMetaDataSvc_Tie.java:7393) ~[cswebapi-080801001.jar:?]
        at com.compositesw.cdms.webapi.service.WMetaDataSvc_Tie.processingHook(WMetaDataSvc_Tie.java:22104) ~[cswebapi-080801001.jar:?]
        at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:350) ~[webservices-rt-2.1.jar:2.1]
        at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:465) ~[webservices-rt-2.1.jar:?]
        at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:119) ~[webservices-rt-2.1.jar:?]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) ~[servlet-api-3.1-cis-trunk.jar:3.1.0]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) ~[servlet-api-3.1-cis-trunk.jar:3.1.0]
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:811) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at com.compositesw.server.services.SecurityHeadersFilter.doFilter(SecurityHeadersFilter.java:106) ~[csserver-080801001.jar:?]
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1651) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:142) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:576) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:222) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1126) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:514) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:184) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1060) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:140) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:212) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:96) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.Server.handle(Server.java:498) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:258) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) ~[jetty-all-9.2.30.v20200428.jar:9.2.30.v20200428]
        at java.lang.Thread.run(Thread.java:842) ~[?:?]
Caused by: com.compositesw.common.SafeException: An internal error has occurred.
Cause: host.docker.internal: Name or service not known [Log ID: 56b310f5-c32c-4693-bea3-c5cf873aa958]
        at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
        at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:933) ~[?:?]
        at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1543) ~[?:?]
        at java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:852) ~[?:?]
        at java.net.InetAddress.getAllByName0(InetAddress.java:1532) ~[?:?]
        at java.net.InetAddress.getAllByName(InetAddress.java:1384) ~[?:?]
        at java.net.InetAddress.getAllByName(InetAddress.java:1305) ~[?:?]
        at java.net.InetAddress.getByName(InetAddress.java:1255) ~[?:?]
        at com.compositesw.cdms.webapi.service.WSessionImpl.startSession(WSessionImpl.java:569) ~[cswebapi-server-080801001.jar:?]
        ... 32 more

This article provides details to resolve the Studio connection issue due to error 'host.docker.internal: Name or service not known'. 

Environment

DV Server installed on Windows or Linux machine

Resolution

Follow below steps - 

1. Open Notepad as Administrator on the Windows Studio machine. 

2. Open: C:\Windows\System32\drivers\etc\hosts

3. Add a line like:

127.0.0.1 host.docker.internal
or your local IP if needed.

4. Re-open Studio and connect to DV Server. 

If the issue still persists or fails with a different error, reach out to DV Support team via Support ticket for further assistance. 

Issue/Introduction

How to resolve Data Virtualization Studio connection failure with error 'Cause: host.docker.internal: Name or service not known'?

Powered by Wolken Software