Select to view content in your preferred language

ExcelToSQLite64 ArcGIS Pro 3.3 and 3.4

510
3
12-03-2024 08:09 AM
Labels (1)
StevenLowman
Occasional Contributor

ExcelToSQLite64 starts any time I try to add a table to Pro, it is under ArcGIS Pro in the Task Manager when I go to add a table.  It started around October 9, 2024 and I first had issues with trying to opening or exporting to excel files.  I have worked with Esri and tried all their attempts to fix it, none have worked and some actually corrupted some of the Office files to where I had errors opening word after installing their fix.  This happens with .csv, .dbf, .txt, and excel files that I have tested so far, basically any table file. I can kill the 

ExcelToSQLite64 file in task manager but at that point Pro is still locked up.  This happens only on one computer and the rest of the computers in our org seem to still be fine at this point. There is a standard setup so not sure of any differences in computers.   C:\Program Files\ArcGIS\Pro\bin\ExcelToSQLite64.exe seems to be an issue with my system.  Support has put this in as a bug!

0 Kudos
3 Replies
Robert_LeClair
Esri Esteemed Contributor

For others reading this item, the bug item Steven mentioned is listed below and currently under review:  

  • BUG-000150929: This is a reoccurring issue. ArcGIS Pro loads indefinitely when accessing Excel files or Excel-related tools.
0 Kudos
StevenLowman
Occasional Contributor

IT re-imaged my box, a total wipe of the C drive, and re-installed all the software and now it is working.  Ghost in the system are gone.  Not sure the cause but it was a drastic step to fix it.  

0 Kudos
phess_luckstone
Regular Contributor

Hey,

Just FYI, I have been having the same issue and I put in a ticket to ESRI, they are apparently aware of this issue and have some workarounds.

They suggest installing Microsoft Access Database Engine, if that's not on the machine running pro, pro will sometimes fire those services off.

The second thing they suggested was if this was happening on a server environment and you are running scheduled python scripts or models to use the servers python environment instead of pro's.

The Microsoft Access Database Engine is what solved my issue, but hope this helps you or anyone else facing this issue!

0 Kudos