Hi Mark

The strange thing here is it seems if I open IbExpert and connect to a 1.5 FB database the Ibexpert never goes down.
If I open that App and connect to a 2.5 FB database the apps goes down after 5 minutes with the event showed in the log.

I think something could be wrong with IbExpert and FB 2.5
The Manager says that it can manage 2.5 FB dbs (You can select that version when a DB is registered with IbExpert)

Yesterday I was working trying to add a new index to a table and I run the "shutdown" command from ibexpert. I always do that with my 1.5 DB.
The DB has been corrupted after trying to shutdown it and I could never access to it (I had to made a restore of that db)
I think something is wrong with the ibexpert and FB 2.5.
It's a problem for me, cos IbExpert is a very good db manager for FB.

Perhaps someone can tell me other good managers for FB.

I will try to figure out what could be the issue sending an email to IbExpert support.

Regards
Diego

--- In firebird-support@yahoogroups.com, Mark Rotteveel <mark@...> wrote:
>
> On Tue, 13 Sep 2011 12:40:44 -0000, "diegodelafuente"
> <diegodelafuente@...> wrote:
> > My IbExpert manager is closing very often without any error message.
> > Checking the FB log I can see these alerts (see below)
> > I can see this explanation regarding the alerts:
> > INET/inet_error: read errno = 10054 or 10038 or 10093
> >
> > Error showings
> > Multiple entries in firebird.log or interbase.log with errors 10054,
> > 10038, 10093, etc.
> > Reason
> > These errors are caused by network problems - check your hubs, network
> > adapters, etc. It is not an Firebird/InterBase error itself, but it may
> > impact Firebird/InterBase.
> > Recovery process
> > We offer FBScanner tool to solve "10054 errors" problem (among other
> > issues). See details here.
> > Recovery chances:
> > Not applicable.
> >
> > The strange thing here is that my FB database could be one in production
> > or my local DB (for development). In this case the log is from my local
> DB.
> >
> > I'm using FB 2.5, windows XP all in a virtual machine (using Virtual
> Box)
>
> 10054 is a connection reset by peer and is a symptom of the problem you
> are experiencing with IB expert, not a cause (if IB expert crashes or
> something else, the socket is not closed correctly, which results in 10054.
>
> http://msdn.microsoft.com/en-us/library/ms740668%28VS.85%29.aspx :
> An existing connection was forcibly closed by the remote host. This
> normally results if the peer application on the remote host is suddenly
> stopped, the host is rebooted, the host or remote network interface is
> disabled, or the remote host uses a hard close (see setsockopt for more
> information on the SO_LINGER option on the remote socket). This error may
> also result if a connection was broken due to keep-alive activity detecting
> a failure while one or more operations are in progress. Operations that
> were in progress fail with WSAENETRESET. Subsequent operations fail with
> WSAECONNRESET.
>
> Mark
>