| Subject | Re: [firebird-support] Internal gds software consistency check (cannot start thread) |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-04-05T05:59:04Z |
At 05:11 AM 5/04/2005 +0000, you wrote:
source: are you connecting to the IP (or host) address of the host
machine, even if connecting locally?
The main source of the problem is likely to be IBConsole itself. It was
written for InterBase. Firebird 1.5.x is really different from IB in a lot
of ways. The immediate problem is likely to be use of the wrong client
library. If you have an old IB version of gds32.dll in IBConsole's
application path, or in the system32 directory, then connection problems
are likely. Add to that IBConsole's own ambiguous hard-coded SQL for
querying the system tables and, overall, you have several likely sources of
inconsistency.
Check carefully which client IBConsole is loading. It *must* be the
version of fbclient.dll that is generated by the instclient.exe utility (as
gds32.dll) and it must be in whatever location your version of IBConsole
wants to load the client from. (If you are using Fb 1.5.x Classic, which,
judging by your error message, you are not, then IBConsole won't work with
it without a careful recompile).
Best advice is to abandon IBConsole and pick up a Firebird 1.5-aware admin
program like IBExpert Personal, Firebird Workbench or IB_SQL. Do some
reality checks using isql (with the appropriate host connection string to
deal with Terminal Server situation) to satisfy yourself that your
databases are not corrupt.
./hb
>Hi Guys,Memory usage is the least likely. Terminal server is a possible
>
>I am getting "Internal gds software consistency check (cannot start
>thread)" almost every time I try to connect to Firebird using
>IBConsole.
>
>I have a Win2k server with 2 databases on Firebird 1.52 (I was
>getting
>the error also on 1.51, 1.50, etc...
>
>I have a feeling it is related with memory usage or with my server
>having Terminal server installed.
source: are you connecting to the IP (or host) address of the host
machine, even if connecting locally?
The main source of the problem is likely to be IBConsole itself. It was
written for InterBase. Firebird 1.5.x is really different from IB in a lot
of ways. The immediate problem is likely to be use of the wrong client
library. If you have an old IB version of gds32.dll in IBConsole's
application path, or in the system32 directory, then connection problems
are likely. Add to that IBConsole's own ambiguous hard-coded SQL for
querying the system tables and, overall, you have several likely sources of
inconsistency.
Check carefully which client IBConsole is loading. It *must* be the
version of fbclient.dll that is generated by the instclient.exe utility (as
gds32.dll) and it must be in whatever location your version of IBConsole
wants to load the client from. (If you are using Fb 1.5.x Classic, which,
judging by your error message, you are not, then IBConsole won't work with
it without a careful recompile).
Best advice is to abandon IBConsole and pick up a Firebird 1.5-aware admin
program like IBExpert Personal, Firebird Workbench or IB_SQL. Do some
reality checks using isql (with the appropriate host connection string to
deal with Terminal Server situation) to satisfy yourself that your
databases are not corrupt.
./hb