Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.

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.

asked 30 May '19, 04:27

SamuelCosta's gravatar image

SamuelCosta
71338
accept rate: 20%

What connection string are you using?

(31 May '19, 03:39) Volker Barth
Replies hidden

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

(31 May '19, 04:19) SamuelCosta

I'd recommend to add the LOG=... connection parameter to debug connection issues.

(31 May '19, 06:01) Volker Barth

Here is the log

Fri May 31 2019 14:44:57
14:44:57 Attempting to connect using:
UID=ClickView;PWD=********;DBN=SGQuiaios;ServerName=SA16;CON=SQL_DBC_791800;LOG=C:\temp\connlog.log;LINKS='tcpip(host=192.168.69.14:9574)'
14:44:57 Attempting to connect to a running server...
14:44:57 Attempting TCPIP connection (no sasrv.ini cached address)
14:44:57 Ignoring IPv4 address 192.168.69.14:9574
14:44:57 No valid host names or addresses given
14:44:57 Removing failed address from sasrv.ini cache
14:44:57 Cannot connect to server

The PC have the IPv6 disabled and IPv4 enabled

(31 May '19, 09:56) SamuelCosta

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

permanent link

answered 26 Jun '19, 10:49

SamuelCosta's gravatar image

SamuelCosta
71338
accept rate: 20%

Comment Text Removed

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?

permanent link

answered 31 May '19, 10:24

JBSchueler's gravatar image

JBSchueler
3.3k41564
accept rate: 19%

edited 31 May '19, 10:26

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:

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.

permanent link

answered 31 May '19, 02:24

Dev's gravatar image

Dev
81114
accept rate: 20%

edited 31 May '19, 03:43

Volker%20Barth's gravatar image

Volker Barth
40.2k361550822

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
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×159
×95

question asked: 30 May '19, 04:27

question was seen: 1,610 times

last updated: 26 Jun '19, 11:20