I have a customer running an application written in Delphi 2009 using EDB
2.03b21 Unicode where most everyone (4 of the 5 people in the small company)
connects remotely to the database server running as a service on an old XP
in a corner of the office.  They've had no problems to speak of until
yesterday.

I got a report that two of the people could not connect and were getting
error #1100, "A connection to the server cannot be established ('The stream
signature was not received')."  The person in the office that was connecting
locally was still working fine.  I got the same error trying to connect over
the internet from EDB Manager.

Simply logging into the machine and restarting the EDB service solved the
problem (I did not reboot the whole machine).  But today they reported the
problem again--this time the local office person was also getting the error.
Again, restarting the database service got them up and running.

Is this a network glitch?  Can I just tell them to get a faster computer or
more memory?  I think they have a pretty fast internet connection, so don't
believe that's the problem.  There is 16 GB free space on the main hard
disk.  Anything else to check?

--
David Cornelius
Cornelius Concepts

David,

> I got a report that two of the people could not connect and were getting
> error #1100, "A connection to the server cannot be established ('The
> stream signature was not received')."

I've seen this at a couple of different client sites as well, so it's not
just you.   Users that are connected can continue to use the existing
connections, but once this occurs any new connection attempt fails with an
1100 error.

The other connection issue that we see is a 1100 error indicating "Socket
error: An existing connection was forcibly closed by the remote host."   Not
sure if it's the same thing with slightly different message depending on the
circumstances, but the result is the same in that new connections can't be
made until the server engine is restarted.

Unfortunately I have been unable to figure out some way to reproduce either
of these.

But I can tell you that the cause of the issue is NOT having both local and
client/server connections accessing the same database as we are seeing this
at client sites that only use client/server connections.  Not a big help,
but at least that is one possibility that is eliminated.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Terry,

Thanks for the note.  It makes sense that it doesn't matter whether the
connection is local or remote--I've found that to be pretty transparent to
EDB.  But it makes me wonder if something gets tripped up in the database
listener service and then can't correct itself.

I may create a small program that attempts to connect periodically and
restarts the database if it detects a problem.  I was out of the office when
the call came in today and the customer application was down for about an
hour.  Hopefully, the root of the problem will be found and resolved
instead.

--
David Cornelius
Cornelius Concepts

"Terry Swiers" <millennium@1000years.com> wrote in message
news:6FE6A055-4B7B-4655-A494-6FA9389DA3C3@news.elevatesoft.com...
> David,
>
>> I got a report that two of the people could not connect and were getting
>> error #1100, "A connection to the server cannot be established ('The
>> stream signature was not received')."
>
> I've seen this at a couple of different client sites as well, so it's not
> just you.   Users that are connected can continue to use the existing
> connections, but once this occurs any new connection attempt fails with an
> 1100 error.
>
> The other connection issue that we see is a 1100 error indicating "Socket
> error: An existing connection was forcibly closed by the remote host."
> Not sure if it's the same thing with slightly different message depending
> on the circumstances, but the result is the same in that new connections
> can't be made until the server engine is restarted.
>
> Unfortunately I have been unable to figure out some way to reproduce
> either of these.
>
> But I can tell you that the cause of the issue is NOT having both local
> and client/server connections accessing the same database as we are seeing
> this at client sites that only use client/server connections.  Not a big
> help, but at least that is one possibility that is eliminated.
>
> --
>
> ---------------------------------------
>  Terry Swiers
>  Millennium Software, Inc.
>  http://www.1000years.com
>  http://www.atrex.com
>
> Now shipping Atrex 13.  For more information go to
>  http://www.atrex.com/news.asp
>
> Atrex Electronic Support Options:
>  Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
>  Email: mailto:support@atrex.com
>  Newsgroup: news://news.1000years.com/millennium.atrex
>  Fax: 1-925-829-1851
>  Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
>  ---------------------------------------
>
>

David,

> Thanks for the note.  It makes sense that it doesn't matter whether the
> connection is local or remote--I've found that to be pretty transparent to
> EDB.  But it makes me wonder if something gets tripped up in the database
> listener service and then can't correct itself.

That's what I'm thinking as well, but have not had the time to track down
the starting point of the connection process and trace into the function to
see where it's failing.


> I may create a small program that attempts to connect periodically and
> restarts the database if it detects a problem.

I had thought about doing that as well, but since there may be users
actively using the server that bouncing them out without warning might not
be the best solution.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

<< I had thought about doing that as well, but since there may be users
actively using the server that bouncing them out without warning might not
be the best solution. >>

While not a solution how about just creating a task in windows that restarts the EDB service every night/morning. This assumes there is time with nobody on but if error is infrequent it might be enough to help.
Setting it up is just a line in a batch file.

Raul

Raul,

> While not a solution how about just creating a task in windows that
> restarts the EDB service every night/morning. This assumes there is time
> with nobody on but if error is infrequent it might be enough to help.

I've got one user that claims that he is having to restart the server engine
3 or 4 times a day, the other already shuts the server down at night so a
nightly restart wouldn't be any different than what they are doing now.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Terry

<<
I've got one user that claims that he is having to restart the server engine
3 or 4 times a day, the other already shuts the server down at night so a
nightly restart wouldn't be any different than what they are doing now.
>>

Yikes - definitely not in this case.

I guess on the bright side (if there is such a thing here) it's at least reproducable on client systems.

I'm sure you've done it already but anything in the server logs?  Enabling all log events and possibly even deploying a debug version of edb server for a day might not be a bad idea  (if your customer goes for it) to see if that sheds more light on it.

Raul

I thought about that, but it's been running fine for months, then bam!  two
days in a row.  It's gotta be something tangible and identifiable.  And like
Danny Thorpe tweeted a few days ago: "Things that magically go away have a
bad habit of magically returning. Don't accept magical solutions. Understand
and fix the true problem."

--
David Cornelius
Cornelius Concepts

"Raul" wrote in message
news:E690CB7C-A8B5-4EE9-83E5-4EEE78D15697@news.elevatesoft.com...
>
> << I had thought about doing that as well, but since there may be users
> actively using the server that bouncing them out without warning might not
> be the best solution. >>
>
> While not a solution how about just creating a task in windows that
> restarts the EDB service every night/morning. This assumes there is time
> with nobody on but if error is infrequent it might be enough to help.
> Setting it up is just a line in a batch file.
>
> Raul
>

David,

> I'm sure you've done it already but anything in the server logs?

With this particular client, there are no unexpected errors in the log
table.


> Enabling all log events and possibly even deploying a debug version of edb
> server for a day might not be a bad idea  (if your customer goes for it)
> to see if that sheds more light on it.

Had the debug server running on one of the other clients running into this.
Since there is no AV associated with the event, the debug code in the server
engine isn't triggered.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Nothing unusual in the logs.  I see connects and disconnects, then a server
stop and a server start--nothing to indicate there was ever a problem.

--
David Cornelius
Cornelius Concepts

"Terry Swiers" <millennium@1000years.com> wrote in message
news:E3344399-24FB-41B1-9A4E-E1AD2A3FA4CF@news.elevatesoft.com...
> David,
>
>> I'm sure you've done it already but anything in the server logs?
>
> With this particular client, there are no unexpected errors in the log
> table.
>
>
>> Enabling all log events and possibly even deploying a debug version of
>> edb server for a day might not be a bad idea  (if your customer goes for
>> it) to see if that sheds more light on it.
>
> Had the debug server running on one of the other clients running into
> this. Since there is no AV associated with the event, the debug code in
> the server engine isn't triggered.
>
> --
>
> ---------------------------------------
>  Terry Swiers
>  Millennium Software, Inc.
>  http://www.1000years.com
>  http://www.atrex.com
>
> Now shipping Atrex 13.  For more information go to
>  http://www.atrex.com/news.asp
>
> Atrex Electronic Support Options:
>  Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
>  Email: mailto:support@atrex.com
>  Newsgroup: news://news.1000years.com/millennium.atrex
>  Fax: 1-925-829-1851
>  Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
>  ---------------------------------------
>
>