Does the exception always happen reading the same gINT file? It could be a corrupt file.
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.
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)
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
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
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!
