One of our customers is experiencing a problem with EDB's Service that we've never encountered before.

"ElevateDB Error #1100 A connection to the server at '192.168.0.2' could not be established (The stream signature was not received)"

We've verified that the Windows Firewall is turned off (I've even made inbound and outbound exceptions anyway, to no avail) and there isn't any anti-virus software running.

I am able to see EDBSRVR listening on port 12010. It's NOT restricted.

We've spent some time researching this error phrase on the ElevateDB support forums, but couldn't find any recent occurrences. Any guidance you can provide would be greatly appreciated.  We have many customers running this version of EDB in a client/server configuration and no others have reported this problem.

Here are the details about their setup:

-Windows Server 2012 64-bit
- 12GB of RAM
-Intel Xenon CPU @ 3.10 GHz

******************

Our program was installed to these directories:
C:\FMP_DATA

which contains

\CONFIG
\DATA
\TEMP

as well as some supporting files, including "edbsrvr.exe" and "edbsrvr.ini". CONFIG contains the configuration files for EDB, and the DATA folder has the database/catalog files.

The program itself gets installed to C:\Program Files (x86) folder

We're using ElevateDB 2.17, Build 1. To remove application as a potential cause, I've been using ElevateDB Manager (also 2.17.1) to try and connect to the database. When I use the Local option and set the correct CONFIG directory, we are able to see and browse the database. If I change the connection option to be "Remote" and use the self-lookup IP address (127.0.0.1) and port (12010) we're able to connect. However, when trying to use the server's IP address (192.168.0.2) or its name (ADROIT-SERVER) we receive the attached error.

Thanks in advance for the assistance!

Brian Kennedy wrote:

> when trying to use the server's IP address (192.168.0.2)

Are you 100% sure that is the right server address? If so, then check what you have for the server address in the config.
https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=starting_configuring_server

I'd expect that it would be blank, and thus bind to all IPs. And if it is, then check again that is the right IP!

Beyond that, I'd check you can telnet to that port too.

--

Matthew Jones

Brian


Probably teaching granny to suck eggs here but has the machine been physically powered off, left off for at least 10 minutes before powering back on?

Looking at the only other post I can find that mentions it the problem was

<<There's an issue with both 2.03 B21 and 2.04 B2 whereby a disconnect due to
inactivity will cause the session on the server to be closed completely,
instead of just disconnected.  After that point, things can go a little
haywire, so the results can vary.  I'll be getting a 2.03 B22 out by
(hopefully) this weekend that will correct this.>>

I know from personal experience that sometimes a reboot isn't enough to get rid of the problem.

Roy Lambert

Thank you all for your input. I believe we've found the problem. The server which hosts our data has a static IP address of 192.168.0.2 but was also being assigned an IP address by DHCP. If they use the DHCP address, the connection works without issue. I've advised them to review their network configuration for this server. Again, thank you for your feedback!

Brian

>Thank you all for your input. I believe we've found the problem. The server which hosts our data has a static IP address of 192.168.0.2 but was also being assigned an IP address by DHCP. If they use the DHCP address, the connection works without issue. I've advised them to review their network configuration for this server. Again, thank you for your feedback!

Didn't even know that was possible if you didn't have two network cards which is a bit unusual

Roy