cancel
Showing results for 
Search instead for 
Did you mean: 

Connection error

0 Kudos
2,268

When i try to connect to a sql anywhere 16 server, i get the error "No valid host names or addresses given". I searched for this message but nothing found.

The application is hosted in a win10 that uses oledb (dboledb16.dll) to connect.

I have other clients with the same configuration working fine.

Accepted Solutions (1)

Accepted Solutions (1)

The issue has been solved with the W10 update 1903. Thanks

Answers (2)

Answers (2)

jack_schueler
Product and Topic Expert
Product and Topic Expert

I looked up the cause for the "Ignoring IPv4 address 192.168.69.14:9574" message.

When calling the operating system's socket() function with the argument "AF_INET" (The Internet Protocol version 4 (IPv4) address family) an INVALID_SOCKET error was returned. This is interpreted by the SQL Anywhere software to mean that IPV4 is not supported on the system.

So the software resorts to IPv6.

What does a command prompt "ping 192.168.69.14" report?

What does the Windows ipconfig tool report?

0 Kudos

C:>ping 192.168.69.14

Pinging 192.168.69.14 with 32 bytes of data: Reply from 192.168.69.14: bytes=32 time=16ms TTL=123 Reply from 192.168.69.14: bytes=32 time=16ms TTL=123 Reply from 192.168.69.14: bytes=32 time=16ms TTL=123 Reply from 192.168.69.14: bytes=32 time=16ms TTL=123

Ping statistics for 192.168.69.14: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 16ms, Average = 16ms

C:>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PCQH1002 Primary Dns Suffix . . . . . . . : domain.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : domain.local Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller Physical Address. . . . . . . . . : 4C-52-62-21-35-D0 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.70.104(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 29 de maio de 2019 16:26:12 Lease Expires . . . . . . . . . . : 8 de junho de 2019 14:51:59 Default Gateway . . . . . . . . . : 192.168.70.254 DHCP Server . . . . . . . . . . . : 192.168.70.10 DNS Servers . . . . . . . . . . . : 192.168.70.10 NetBIOS over Tcpip. . . . . . . . : Enabled

jack_schueler
Product and Topic Expert
Product and Topic Expert
0 Kudos

Forward your email address to Jack(dot)Schueler(at)sap.com and I will send you a Windows socket test application that should tell me what's happening on the system with the failing connection.

0 Kudos

I have already sent the email

This is what I found in one of the release notes:

If an IPv6 address was used in the HOST or LINKS parameters of a connection string, on a machine that did not support IPv6, the client would have displayed the message "No IP address found for <ipv6 address="">". Thishas been fixed. The error message will now read "No valid host names or addresses given". If the LOG= parameter is also used, the message "Ignoring IPv6 address <ipv6 address="">" is written to the log for each IPv6 address found.

VolkerBarth
Contributor
0 Kudos

This seems to be from the 12.0.1 readme, particularly "(Build #3530 - Engineering Case #691879)", so I added the link...