Question Re: Communication function sconn::receive code 4 in Technology Q&A

Communication function sconn::receive code 4

Former Member — Fri, 01 Aug 2014 19:11:33 GMT

I have opened the new question as Jeff asked me to ...

I indeed would love to download the EBF ... but since the absorption into SAP, which we were not told about (go figure why?), we can no longer download those EBFs ...

Ironically, no one can even tell us how to PAY for a support contract.

Here's the link back to the original question:

http://sqlanywhere-forum.sap.com/questions/10636/communication-function-sconnreceive-code-4

FYI, this issue is exactly the same for both SQL Anywhere 12 and 16 from the 'bad' machine. Finally, I did try with the ip address, without host name - same exact result.

TCP using Winsock version 2.2
IPv6 support enabled
Starting database "abi16UC" (C:\\gemsql\\abi16UC.db) at Thu Jul 31 2014 10:50
Transaction log: abi9-12.log
Starting checkpoint of "abi16UC" (abi16UC.db) at Thu Jul 31 2014 10:50
Finished checkpoint of "abi16UC" (abi16UC.db) at Thu Jul 31 2014 10:50
Cache size adjusted to 2668K
Database "abi16UC" (abi16UC.db) started at Thu Jul 31 2014 10:50
Database server started at Thu Jul 31 2014 10:50
Trying to start SharedMemory link ...
SharedMemory link started successfully
Trying to start TCPIP link ...
Starting on port 2638
Starting UDP listener on IP address 192.168.58.41:2638
Starting UDP listener on IP address (::1):2638
Starting UDP listener on IP address 127.0.0.1:2638
Looking for server with name abi16uc
Sending broadcast to find server
Using broadcast address of: 192.168.58.255
Looking for server with name abi16uc
Sending broadcast to find server
Using broadcast address of: ff02::1
Looking for server with name abi16uc
Sending broadcast to find server
Using broadcast address of: 127.255.255.255
Server not found (no reply received)
TCPIP link started successfully
Now accepting requests
Starting TCPIP listener on IP address (::):2638
Starting TCPIP listener on IP address 0.0.0.0:2638
Cache size adjusted to 709244K
TCP/IP: Received connection request from 192.168.58.41:54508.
Connection from 192.168.58.41:54508 assigned connection ID 1
Connection ID 1: Client disconnected



[Sybase][ODBC Driver][SQL Anywhere]Connection error: Timeout occurred while waiting for connection response
SQLCODE=-832
SQLSTATE=08001
Connection parameters: User= Password=*** Host=ABI-2012-04 B.absolutebrilliance.local:2638 Server=abi16uc LINKS=TCPIP ENC=NONE



C:\\Users\\administrator>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::547e:eba7:4a20:75b8%11
IPv4 Address. . . . . . . . . . . : 192.168.58.41
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.58.1

Tunnel adapter isatap.{6C2EF952-2F54-4F69-8170-2336EE12C9B3}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Re: Communication function sconn::receive code 4

Vlad — Sat, 02 Aug 2014 03:21:10 GMT

Hi Joel,
Are you able to access any of link that are listed on the Breck's page: http://sqlanywhere.blogspot.de/search/label/latest%20EBFs I can download EBFs either from the sybase.com or from SAP's https://service.sap.com/swdc

Re: Communication function sconn::receive code 4

Former Member — Mon, 04 Aug 2014 12:50:47 GMT

Yes, I can access the page, but that sends me back to the 'sybase.com' login page which reports:

"You have selected a download which requires a Technical Support Agreement"

And NO ONE CAN TELL US HOW TO GET A TECH SUPPORT AGREEMENT!

Re: Communication function sconn::receive code 4

Breck_Carter — Mon, 04 Aug 2014 15:40:13 GMT

Those EBF pages on my blog are no longer of any use whatsoever.

Re: Communication function sconn::receive code 4

Vlad — Mon, 04 Aug 2014 16:10:46 GMT

Strange, Breck, I am able to access these downloads, and links such as http://origin2.sybase.com/swx/17962/EBFXXXXX.tgz work fine for me. But it seems that I can see patches, because my account has been migrated to SAP Service Marketplace.

Re: Communication function sconn::receive code 4

Vlad — Mon, 04 Aug 2014 16:15:45 GMT

Joel, could you please take a look at the page: http://service.sap.com/sybase/support It tells that you can somehow migrate to the SAP infrastructure and get the appropriate user for patches.

Re: Communication function sconn::receive code 4

Former Member — Tue, 05 Aug 2014 00:23:32 GMT

"No Soap Radio" ...

When trying to register (upper right hand corner), the page asks for a CUSTOMER NUMBER ... and no one in SAP can tell us what our customer number is...

And when clicking the 'report an incident' link, it prompts for a userid and password (I'm guessing the one that would be assigned as part of registration).

So we're still stuck.

Re: Communication function sconn::receive code 4

jeff_albion — Tue, 05 Aug 2014 10:30:58 GMT

Could you also add the "LOG=" information, where you're currently seeing the Communication function sconn::receive code 4 message?

Have you tried disabling the IPV6 interface temporarily maybe to see if it is interfering with the IPv4 connection?

Do you have any Layered Service Providers installed on the machine? (You can try using ListDLLs to see if there are any external DLLs not provided by SAP being loaded with the SQL Anywhere processes). If there are any installed, try removing them. (See: http://support.microsoft.com/kb/299357 - i.e. netsh int ip reset).

If that doesn't remove the Layered Service Providers, you may also want to try 'LSP-Fix' to remove them.

Applying an EBF (once you can obtain it with an SAP Support agreement) would also resolve any known issues. With a support agreement you can also then open a technical support case with support so that we can diagnose this particular case with you remotely online, in real-time using SAPRouter.

Re: Communication function sconn::receive code 4

jeff_albion — Tue, 05 Aug 2014 10:44:08 GMT

Hi Joel,

Did you originally have a support agreement with Sybase? All of the Sybase support agreements have now been migrated to SAP and someone in your organzation would (should) have been given this information as part of that migration process.

If you didn't already have a support agreement, you can purchase a support agreement now with SAP when you purchase SQL Anywhere, or you will want to contact Sales through the SAP Store.