Skip to main content
Solved

MDB_ADO reader: An unknown exception occurred

  • September 27, 2018
  • 7 replies
  • 40 views
J
Forum|alt.badge.img

Hi All,

I am attempting to walk an FME script (using desktop 32 bit) over a large folder of specialised access databases called gINT files (.gpj) and move the data to various CSVs. However it will terminate after several hours with "MDB_ADO reader: An unknown exception occurred", and only write several of the CSVs for the files it has read. It works for smaller sample sets, so I don't believe it is a flaw in the script.

I have a copy of the log, unfortunately it is a bit large to attach. Any help appreciated.

Thanks

-Jack Collins

Best answer by jecollins

It turned out there was something in the reader that was stopping this reading the access files properly, this has now been fixed in the latest FME release. Thank you to the hard working team at Safe for getting that fixed up!

View original
Did this help you find an answer to your question?

7 replies

oscard
Influencer
Forum|alt.badge.img+21
  • oscardInfluencer
  • Influencer
  • September 27, 2018
Does the exception always happen reading the same gINT file? It could be a corrupt file.

 

 

J
Forum|alt.badge.img
  • jecollins
  • Author
  • September 27, 2018
oscard wrote:
Does the exception always happen reading the same gINT file? It could be a corrupt file.

 

 

The file can be opened by FME Data Inspector, so I don't believe it is corrupted. But I'll re-run the script and see if it stops on the same file.

 

 

steveatsafe
Safer
Forum|alt.badge.img+12
  • steveatsafeSafer
  • Safer
  • September 28, 2018

I wonder if you are hitting any sort of memory limit with the 32bit process? What's the memory usage look like in the FME log? I'm curious if you have looked at the Windows Task Manager while the job was running to see what sort of memory usage the FME.exe process is up to. You might have success with 64bit FME (installing into a new folder - you don't need to uninstall your existing FME), but you'll also need to have the appropriate drivers for the 64bit version of MDB_ADO.

 

As an example here's a link to the drivers you may need for FME 64bit: https://www.microsoft.com/en-us/download/details.aspx?id=54920 (32bit and 64bit here at this link)
SteveatSafe
J
Forum|alt.badge.img
  • jecollins
  • Author
  • October 2, 2018
steveatsafe wrote:

I wonder if you are hitting any sort of memory limit with the 32bit process? What's the memory usage look like in the FME log? I'm curious if you have looked at the Windows Task Manager while the job was running to see what sort of memory usage the FME.exe process is up to. You might have success with 64bit FME (installing into a new folder - you don't need to uninstall your existing FME), but you'll also need to have the appropriate drivers for the 64bit version of MDB_ADO.

 

As an example here's a link to the drivers you may need for FME 64bit: https://www.microsoft.com/en-us/download/details.aspx?id=54920 (32bit and 64bit here at this link)
It isn't hitting the memory limit, I've checked the FME log and kept an eye on the amount of C drive memory left. I can send the FME log if you want. I normally use 64bit but cannot get it to read the access databases with those drivers.

 

It is stopping at the same files, and if I run it on just the files it stops on rather than a walk it has the same error come up. I have tried a couple of different walks. I can read it in Data inspector, I have had to install Microsoft Access Runtimes to make them readable in some cases but even after fixing that Workbench won't work.

 

I have attached the log after running it on just one of the files it is failing on. holebaseuploader.txt
J
Forum|alt.badge.img
  • jecollins
  • Author
  • November 14, 2018

Hi All,

Thanks for the advise. Safe have had a look at it and it was a bug in the reader. It has been repaired and is going to be fixed in the next release.

Thanks

-Jack

J
Forum|alt.badge.img
  • jecollins
  • Author
  • Best Answer
  • February 27, 2019

It turned out there was something in the reader that was stopping this reading the access files properly, this has now been fixed in the latest FME release. Thank you to the hard working team at Safe for getting that fixed up!

neilmyoung
Contributor
Forum|alt.badge.img+3
  • neilmyoungContributor
  • Contributor
  • February 25, 2025

​@jecollins - Due to being forced to update to Windows 11, my team are having issues dealing with gINT files. I would love to use FME to export the data. Would you be willing to share your workspace or methodology, as what I worry most about is trying to replicate all the joins that would be required to export useful data and am hoping you may have already worked through a lot of the relationships between the tables to get useful output. 

Reply


Helpful Members This Week

Community Stats

31,139
Posts
118,062
Replies
38,758
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.