Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: FireDAC and Access Violations


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 2 - Last Post: Jul 7, 2014 6:03 AM Last Post By: Frank Staal
Frank Staal

Posts: 115
Registered: 12/9/99
FireDAC and Access Violations  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 3, 2014 7:04 AM
I am using a FireDAC connection to an Advantage database and when I am debugging it sometimes throws an AV in a different thread... the only things I see in the callstack is a couple of calls to ntdll.RtlInitializeExceptionChain and the file: "C:\Program Files (x86)\Advantage 10.10\acesdk\Redistribute\axcws32.dll". Any idea why? How to debug? Etc.? I do notice it happens only when I close the connection to the FDConnection and after some seconds. And then only once. After the exception has been raised the program runs okay...
Dmitry Arefiev

Posts: 1,406
Registered: 12/7/03
Re: FireDAC and Access Violations  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 4, 2014 7:44 PM   in response to: Frank Staal in response to: Frank Staal
I am using a FireDAC connection to an Advantage database and when I am debugging it sometimes throws an AV in a different thread...

Please provide environment report:
http://docwiki.embarcadero.com/RADStudio/XE6/en/DBMS_Environment_Reports_(FireDAC)

Also:
1) Is this AV "visible" only in debugger ? Or does your application show message box with AV information ?
2) Is this AV specific to your ACE version ? Did you try to upgrade your ACE ?
3) Is this AV reproducable with simple test application ?

--
With best regards,
Dmitry Arefiev / FireDAC Architect
Frank Staal

Posts: 115
Registered: 12/9/99
Re: FireDAC and Access Violations  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 7, 2014 6:03 AM   in response to: Dmitry Arefiev in response to: Dmitry Arefiev
Hi Dmitry,

the environment report is as follows. I've only anonymised the data connections as it would reveal customer info and such.

================================
Connection definition parameters
================================
Name=Unnamed
ServerTypes=Remote
TableType=CDX
Database=K:\Data
Protocol=TCPIP
DriverID=ADS
================================
FireDAC info
================================
Tool = RAD Studio XE6
FireDAC = 10.0.1 (Build 69712)
Platform = Windows 32 bit
Defines = FireDAC_NOLOCALE_META;FireDAC_MONITOR
================================
Client info
================================
Loading driver ADS ...
Client version = 1010000000
Client DLL name = h:\Bin\Win32\Debug\ace32.dll
================================
Session info
================================
Current catalog = \\FileServer\Data
Current schema =
Server version = 10.10.0.0
Server collation =
Connection path = \\FileServer\Data

Also:
1) Is this AV "visible" only in debugger ? Or does your application show message box with AV information ?
The application doesn't show an error dialog

2) Is this AV specific to your ACE version ? Did you try to upgrade your ACE ?
I only have one Advantage server (10.10) so I cannot answer if it is specific to mine. When I started the FireDAC test and migration I downloaded the latest ACE Engine for version 10.10. This was just a few weeks ago, so I am pretty sure this is the last one around, as they are preparing 12.0 for release and sort of declared version 10 deprecated.

3) Is this AV reproducable with simple test application ?

All I've done is put on a form a dbgrid > datasource > query > connection >wait cursor. Opened a simple query ('select * from aTable'), saw the grid fill up, set connected to false on the connection. If you want you can have my simple test app, but you'd have to change stuff like database path and such.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02