|Subject||Re: Internal gds software consistency check (cannot start thread)|
> Memory usage is the least likely. Terminal server is a possibleI am connecting to the Host name when using IBConsole, however when
> source: are you connecting to the IP (or host) address of the host
> machine, even if connecting locally?
running other apps I am using the IP address, Is there any problem
related with this?
> 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 IBin a lot
> of ways. The immediate problem is likely to be use of the wrongclient
> library. If you have an old IB version of gds32.dll in IBConsole'sproblems
> application path, or in the system32 directory, then connection
> are likely. Add to that IBConsole's own ambiguous hard-coded SQLfor
> querying the system tables and, overall, you have several likelysources of
> Check carefully which client IBConsole is loading. It *must* be
> version of fbclient.dll that is generated by the instclient.exeutility (as
> gds32.dll) and it must be in whatever location your version ofIBConsole
> 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'twork with
> it without a careful recompile).aware admin
> Best advice is to abandon IBConsole and pick up a Firebird 1.5-
> program like IBExpert Personal, Firebird Workbench or IB_SQL. Dosome
> reality checks using isql (with the appropriate host connectionstring to
> deal with Terminal Server situation) to satisfy yourself that yourWill do, thanks!
> databases are not corrupt.