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. |
The issue has been solved with the W10 update 1903. Thanks |
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? 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
(31 May '19, 13:27)
SamuelCosta
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.
(31 May '19, 16:27)
JBSchueler
Replies hidden
I have already sent the email
(03 Jun '19, 11:06)
SamuelCosta
|
This is what I found in one of the release notes:
This seems to be from the 12.0.1 readme, particularly "(Build #3530 - Engineering Case #691879)", so I added the link...
(31 May '19, 03:44)
Volker Barth
|
What connection string are you using?
the oledb connection string is: Provider=SAOLEDB.16;ENG=SA16;DBN=SGDataBase;Links=tcpip(host=192.168.69.14:9574)
the same cs works in other pcs
I'd recommend to add the LOG=... connection parameter to debug connection issues.
Here is the log
The PC have the IPv6 disabled and IPv4 enabled