kiran kumar kodari
asked on
Access violation at address 4BE34602 in module 'IDAPI32.DLL'. Write of address E5067008
hi everyone,
here we have an Delphi application, it's functionality is to receive data from Ethernet and to store received data in database(Interbase DB) . to store or retrieve data in Interbase DB(Local DB) we are using BDE components. and here we are posting that data to Azure cloud using ADO components. when ever we deployed our application into client system it is working well for sometimes 3hr and sometimes 4hr and sometimes even 24 hr also it is working well but after that we are getting the above exception and exe getting hanged and forcibly stopped. I have searched about above exception all over the internet but didn't get an idea what to do. but crazy thing is this application has ran continuously for 4 days continuously whenever we tested it in my system. I think it is something to do with BDE Components.
forgive me if you are not able to understand my English.
Any suggestions or solutions are helpful.
here we have an Delphi application, it's functionality is to receive data from Ethernet and to store received data in database(Interbase DB) . to store or retrieve data in Interbase DB(Local DB) we are using BDE components. and here we are posting that data to Azure cloud using ADO components. when ever we deployed our application into client system it is working well for sometimes 3hr and sometimes 4hr and sometimes even 24 hr also it is working well but after that we are getting the above exception and exe getting hanged and forcibly stopped. I have searched about above exception all over the internet but didn't get an idea what to do. but crazy thing is this application has ran continuously for 4 days continuously whenever we tested it in my system. I think it is something to do with BDE Components.
forgive me if you are not able to understand my English.
Any suggestions or solutions are helpful.
i doubt it's the BDE causing this problem
after some time it throws an error ...
this is in 99% of the cases a memory leak
you could also add a error stack logger
try madshi.net (free) or eurekalog (paying)
install madshi's madExcept on the machine with Delphi
activate it in your project
> set the madExcept options, like sending a mail with the stack trace via mail when an unhandled AV occurs
http://help.madshi.net/HowToUseMadExcept.htm
this should give you a full stack trace of where the error actually happens
after some time it throws an error ...
this is in 99% of the cases a memory leak
you could also add a error stack logger
try madshi.net (free) or eurekalog (paying)
install madshi's madExcept on the machine with Delphi
activate it in your project
> set the madExcept options, like sending a mail with the stack trace via mail when an unhandled AV occurs
http://help.madshi.net/HowToUseMadExcept.htm
this should give you a full stack trace of where the error actually happens
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
It is normal for something to go wrong with it
Use other components
Try http://devart.com
Or firedac