Subject | Re: [firebird-support] Firebird crashing |
---|---|
Author | Helen Borrie |
Post date | 2003-09-04T02:32:10Z |
At 01:54 AM 4/09/2003 +0000, you wrote:
client machine (in your %system% dir). If they don't have matching version
info and/or their version info doesn't match that of fbserver.exe, then the
problem is that your client is using the wrong version of gds32.dll.
Provide more info about your environment, like what you are using to
connect from Delphi to the server, including versions of everything. If it
IBX or the BDE or dbx using the native IB driver then, on the client
machine, you should probably hide the shipped gds32.dll and rename
fbclient.dll to gds32.dll.
This might not solve it either. We don't know anything about your data
access interface. Depending on what you are using and how it's linking to
the client dll, it might be necessary to recompile it.
Be sure to let us know what happens so that we have a record of any issues
with your specific development environment.
heLen
>Hello,Take a look at the property sheets for gds32.dll and fbclient.dll on the
>Firebird has been crashing while my application is trying to get
>data. It will connect correctly but after some steps it will stop
>responding. The error that I get in Delphi is the following:
>
>Project ctswin.exe raised exception class EAccessViolation with
>message 'Access violation at address 011E26E in odule 'fbclient.dll'.
>Read of address 0145D000'. Process stopped. Use Setp or Run to
>continue.
>
>The error signature that Windows gives is the following:
>szAppName : fbserver.exe szAppVer : 1.5.0.3233 szModName :
>fbserver.exe
>szModVer : 1.5.0.3233 offset : 00020269
>
>Any idea of what could be causing this? Thank you.
client machine (in your %system% dir). If they don't have matching version
info and/or their version info doesn't match that of fbserver.exe, then the
problem is that your client is using the wrong version of gds32.dll.
Provide more info about your environment, like what you are using to
connect from Delphi to the server, including versions of everything. If it
IBX or the BDE or dbx using the native IB driver then, on the client
machine, you should probably hide the shipped gds32.dll and rename
fbclient.dll to gds32.dll.
This might not solve it either. We don't know anything about your data
access interface. Depending on what you are using and how it's linking to
the client dll, it might be necessary to recompile it.
Be sure to let us know what happens so that we have a record of any issues
with your specific development environment.
heLen