Subject | RE: [firebird-support] Unsupported on-disk structure |
---|---|
Author | Helen Borrie |
Post date | 2007-12-01T11:49Z |
At 10:06 PM 1/12/2007, you wrote:
OTOH, if you were using Windows local connection at all times, the service port would not be involved. You would not get IPServer conflicts, since InterBase uses the old IPServer implementation, while Fb 2 and above use the new implementation in XNET. But you obviously have some miscegenation there that you will need to resolve, to ensure that your local client library is the firebird one and that it's the Firebird server it's connecting to...
Helen
>Yes, the problem was that a InterBase server was running on my system andYou can configure Firebird to run alongside a running IB server...but if you didn't configure it, it wouldn't work, since both IB and Firebird use the same service port by default...I guess it's up to you to check your system out, so you can avoid having such problems another time.
>that the FireBird service hadn't been started by the installer. The
>InterBase server was originally installed as part of Borland Developer
>Studio, and have apparentlt always been runing while I have been using
>FireBird, so it didn't occur to me that the problem were caused by
>InterBase....
>
>How can it be working at all when both servers are running at the same time?
OTOH, if you were using Windows local connection at all times, the service port would not be involved. You would not get IPServer conflicts, since InterBase uses the old IPServer implementation, while Fb 2 and above use the new implementation in XNET. But you obviously have some miscegenation there that you will need to resolve, to ensure that your local client library is the firebird one and that it's the Firebird server it's connecting to...
>OK. ;-)
>And no I don't plan to use a FireBird beta at my customers. :-)
Helen