Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
noobTalendDev
Contributor
Contributor

tServiceNowConnection/tServiceNowInput Not working : nodename nor servname provided, or not known

I looked at the other posts that were relevant to 'tServiceNowConnection' but none were helpful. I am trying to connect to our service now, however I am getting this error:

URL: "https://<

internalName>

.service-now.com/"

[FATAL] 15:06:31 iam_svn_talend.endpoint_0_1.Endpoint- tServiceNowInput_1 <internalName>.service-now.com: nodename nor servname provided, or not known

java.net.UnknownHostException:

<internalName>

.service-now.com: nodename nor servname provided, or not known

at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:1.8.0_202]

at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929) ~[?:1.8.0_202]

at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324) ~[?:1.8.0_202]

at java.net.InetAddress.getAllByName0(InetAddress.java:1277) ~[?:1.8.0_202]

at java.net.InetAddress.getAllByName(InetAddress.java:1193) ~[?:1.8.0_202]

at java.net.InetAddress.getAllByName(InetAddress.java:1127) ~[?:1.8.0_202]

at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:102) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:357) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:218) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:194) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:85) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) ~[httpclient-4.3.1-6.0.0.jar:4.3.1]

at iam_svn_talend.endpoint_0_1.Endpoint.tServiceNowInput_1Process(Endpoint.java:2941) [classes/:?]

at iam_svn_talend.endpoint_0_1.Endpoint.runJobInTOS(Endpoint.java:5061) [classes/:?]

at iam_svn_talend.endpoint_0_1.Endpoint.main(Endpoint.java:4843) [classes/:?]

Labels (3)
5 Replies
gjeremy1617088143

HI,

"https://<internalName>.service-now.com/" is a generic url you have to put your specific value instead of <internalName>.

send me love and kudos

Anonymous
Not applicable

Hello,

Are you getting this issue on MAC OS X? If so, you need to update Your /private/etc/hosts File.

Please give us more information about your situation which will be helpful for us to address your issue.

Best regards

Sabrina

 

noobTalendDev
Contributor
Contributor
Author

Yes I am getting this on my Mac OS! I am on 11.6 Big Sur, what other info would be helpful?

 

I am trying to use these components to connect and fetch data from SC_Tasks table in Service Now. I put our internal service now URL in the profile but it doesn't work it throws this message. <InternalName> in the URL is just me saying that hey this is where we put our url

noobTalendDev
Contributor
Contributor
Author

<InternName> has our specific URL, I just put that on the error

Anonymous
Not applicable

Hello,

Please check that you have a consistent internet connection (e.g. by pinging an appropriate server continuously as you run the tests), and that your DNS server is consistently reporting results (e.g. not randomly dropping requests or timing out).

You could also try changing the live server address to a straight IP address (e.g. change local host to 127.0.0.1 in /etc/hosts), so that it doesn't have to perform an address lookup.

Best regards

Sabrina