|
| Re: Establishing a onnection via IB 2007 Client to IB 6020: Server terminates server abnormally |
 |
12 Jan 2007 07:07:56 -0800 |
Michael Danninger wrote:
> I installed the IB 2007 developer edition on my development machine.
> When i connect to a database on a Windows Server 2003 running IB 6020
> Server the IB Server crashes. Serverlog:
> C:\Programme\borland\interbase\bin\ibserver.exe: terminated
> abnormally (-1). (No further hints)
>
> I removed the IB 2007 installation from my development machine and
> reinstalled IB 6020 Client, and everything works fine again.
Although R&D is supposed to be making gds32.dll backward compatible
since the introduction of multi-instancing it is unlikely that they
tested as far back as version 6. Your only option is to use the version
of gds32.dll that matches the server you are trying to connect to.
--
|
| Post Reply
|
| Establishing a onnection via IB 2007 Client to IB 6020: Server terminates server abnormally |
 |
Fri, 12 Jan 2007 09:49:32 +010 |
I installed the IB 2007 developer edition on my development machine. When i
connect to a database on a Windows Server 2003 running IB 6020 Server the IB
Server crashes.
Serverlog: C:\Programme\borland\interbase\bin\ibserver.exe: terminated
abnormally (-1). (No further hints)
I removed the IB 2007 installation from my development machine and
reinstalled IB 6020 Client, and everything works fine again.
|
| Post Reply
|
| Some further details |
 |
Fri, 12 Jan 2007 09:58:56 +010 |
ODS of the db is 10.0, database dialect 3.
Thanks, Michael
|
| Post Reply
|
| Re: Establishing a onnection via IB 2007 Client to IB 6020: Server terminates server abnormally |
 |
13 Jan 2007 07:43:19 -0800 |
Michael Danninger wrote:
> Using a matching gds32.dll will be no problem, but i think the IB
> 2007 client should raise an error message when it is not possible to
> connect to IB Server prior to IB 7 instead of killing the server.
In an ideal world that is true. In the real world doing that kind of
regression testing on outdated versions is a waste of resources that
could be put to better use. IB 6.0x is no longer being developed or
supported and most people have moved on to something else due to the
problems that IB 6.0x has running on current versions of Windows.
--
|
| Post Reply
|
| Re: Establishing a onnection via IB 2007 Client to IB 6020: Server terminates server abnormally |
 |
Sat, 13 Jan 2007 09:49:15 +010 |
"Bill Todd" <no@no.com> schrieb im Newsbeitrag
news:45a7a44c$1@newsgroups.borland.com...
> Michael Danninger wrote:
>
>> I installed the IB 2007 developer edition on my development machine.
>> When i connect to a database on a Windows Server 2003 running IB 6020
>> Server the IB Server crashes. Serverlog:
>> C:\Programme\borland\interbase\bin\ibserver.exe: terminated
>> abnormally (-1). (No further hints)
>>
>> I removed the IB 2007 installation from my development machine and
>> reinstalled IB 6020 Client, and everything works fine again.
>
> Although R&D is supposed to be making gds32.dll backward compatible
> since the introduction of multi-instancing it is unlikely that they
> tested as far back as version 6. Your only option is to use the version
> of gds32.dll that matches the server you are trying to connect to.
>
> --
> Bill Todd (TeamB)
Using a matching gds32.dll will be no problem, but i think the IB 2007
client should raise an error message when it is not possible to connect to
IB Server prior to IB 7 instead of killing the server.
Thanks, Michael
|
| Post Reply
|
|
|
|
|
|
|
|
|
|