Woody -
Is your installation using 2003 Virtual Servers or just plain old vanilla
Win2003 Server? Our setup is running on Virtual. I don't know if it makes a
difference, since the Virtual Server is **supposed** to behave exactly like
2003 (Standard) Server. And you're right - the 60 minute window makes this a
bear to simulate. I wonder if playing with the clock on the server would
accelerate the error? Most of the rest of this response is not necessarily
toward anything in your post - just a convenient spot to jump back into this
mess I started!

Thanks everyone for all your input to this point. It sounds like I'm not the
only one that's about to run out of hair to pull out! ;-)

As has been pointed out elsewhere, our problem is ONLY occurring when a user
leaves an application with an active connection to our FB 1.5.3 databases
open for 60 minutes or more. When said user returns to the aplication
(inhouse, off the shelf, Database Workbench, etc) and attempts to do
anything, the "connection forcibly closed" error comes up. There are no
queries running, no blobs being sent or received, nothing is happening at
all. We have searched for settings on the client, server, and FB that would
indicate some kind of connection timeout and have found nothing of the sort.
The FB service has never crashed or restarted itself, there is nothing in
the Firebird log since we started it up afterour upgrade. We have not seen
this problem at all in the five years these apps have been running on other
versions of the OS and FB/IB platforms.

We have added a keep-alive routine to our in-house app and it has put a
band-aid on that problem, at least. This at least verifies that it is an
idle connection issue. On Tuesday I plan to install FB 1.5.3 on our old
server and run tests against it, as well as the other way around - FB
1.0.3on Win2003. If the 2003/1.5.3 combination theory is accurate,
neither of
those setups should fail. I'll report my findings as soon as they are
available. Now it's time to enjoy the holiday weekend!

Thanks again for all your input,
Scott

On 5/27/06, Woody <woody-tmw@...> wrote:
>
> From: "Glebas" <glebasp@...>
> > Scott,
> >
> > We have exactly the same problem on Win2003 server + FB153SS.
> >
>
> In December, I switched a major client to Win2003 server and FB 1.5.3 SS
> and
> we haven't had any of these problems on their site. We even run terminal
> services so others and myself can work over the Internet. So far, I'd have
> to say the conversion was flawless. I believe the server is at SP1 though
> and not SP2 so I don't know if that makes a difference or not.
>
> I am still running tests here between my laptop XP and my 2000 puter. So
> far, ISQL doesn't seem to exhibit the problem but when you have to wait
> over
> an hour between tests, it takes a long time to check into some of this. :)
>
> Woody (TMW)
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>


[Non-text portions of this message have been removed]