UPDATED:
We were having the same issue and it was related to a bug in the ActualTech ODBC package. They have since posted an update on their website here:
http://www.actualtech.com/download.php
After installing the update, we were back in action.
Be sure to let Microsoft know about this crash by clicking the Smile button and sending a frown in the Interface.
I am an unpaid volunteer and do not work for Microsoft. 'Independent Advisors' work for contractors hired by Microsoft. 'Microsoft Agents' work for Microsoft Support.
They know about it.. Their articles I linked to actually tell you Excel will crash, this seems to be 'Expected behavior' in this case. {sigh} I don't get it, it sure doesn't seem that it should be expected, and shouldn't even be tolerated.
![]()
Jul 10, 2018 Microsoft ODBC Driver 17 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, Analytics Platform System, Azure SQL Database and Azure SQL Data Warehouse.
I am not sure this is the whole source of the problem, despite Microsoft's articles..
I just downloaded and installed v4.0 of the Actual Open Source Database drivers, and they appear to BE 64bit..
Looking at the ODBC driver:
$ lipo -info 'Actual Open Source Databases'
Architectures in the fat file: Actual Open Source Databases are: i386 ppc7400 x86_64 ppc64
I do have others installed, not all of which might be 64bit, but in your case if Actual is the only one installed and you are on the latest release it should be 64bit capable.
UPDATE: In fact, all but one of my installed ODBC drivers WERE 64bit, so I removed the onlly one that was not and the same crash happens. I don't think the 64bit issue is the entire answer to the problem this latest office update has inflicted on us.
Ok so I called into their support line and they were able to give me an installer for the 32 bit version of Excel. I'd recommend you do the same if you need the functionality now.
BTW chat was a no-go for this, I had to call.
I'd post the link here but they also removed some other things manually in order to completely remove Office 2016 before re-installing. I think its safer to have them do that.
Regarding the error the exception I was getting looks like this:
Exception: EXC_BAD_ACCESS
Exception Code: KERN_NAME_EXISTS (0x000000011b0dafcc)
Application Name: Microsoft Excel
Application Signature: XCEL
Application Version: 15.25.0.160817
Crashed Module Version: 1.0.0.0
Blame Module Name: iODBC
Blame Module TimeStamp: 0x4aaa23b5
StackHash: ffffbed8
Extra app info: Reg=en Loc=0x0409
Crashed thread: 0
It references iODBC, which I believe is the first ODBC manager Excel attempts to use prior to prompting you to use the ODBC manager that comes w/ the Actual package.
I'm not sure if iODBC is installed w/ Excel or Actual.
We have discovered that our driver has an issue with the August (64-bit) release of Excel 2016. We will be releasing a fix within the next 48 hours.
I will post here when the new version has been released.
UPDATE: we have posted a new version of the Actual ODBC Pack to our website: http://www.actualtech.com/download.php
The new versions of the ODBC drivers fix the crashing issue with 64-bit Excel 2016 (15.25).
Jonathan Monroe
Actual technologies - ODBC for macOS
http://www.actualtech.com
I see an update posted, and after I installed it Excel 2016 64bit (15.25 (160817)) is no longer crashing when I attempt to insert data from an external database.
Thanks!!
Hi, here is the information we have on this issue, I hope it helps. If you continue to experience problems after installing a compatible driver, please let us know.
Issue
When retrieving data via Data > Get External Data > From Database from an external database that uses a 32-Bit ODBC driver, the 64-Bit Excel 2016 for Mac (version 15.25 or later) crashes
Status: Workaround
This is a known compatibility issue. Please visit this article ODBC drivers that are compatible with Excel for Mac and install a driver that includes 64-bit support.
See Also
Freya
Office Newsroom
Similar to Windows, macOS utilizes named data sources (DSNs) for connecting ODBC-based client applications to Snowflake.
In this Topic:
Prerequisites¶iODBC¶
The Snowflake ODBC driver for Mac requires iODBC, which is available for download from:
To install iODBC:
Note
iODBC provides a GUI administrator tool for configuring drivers and DSNs; however, this tool has not been tested for use with Snowflake and, therefore, should not be used to create or manage DSNs. https://businessnew842.weebly.com/blog/hp-deskjet-f340-all-in-one-printer-driver-for-mac. Use ODBC Manager instead.
ODBC Manager — Optional/Recommended¶
ODBC Manager is a GUI tool for configuring drivers and creating/managing DSNs. The tool is optional because you can also create DSNs manually by editing the appropriate
odbc.ini file. ODBC Manager is available from:
To install ODBC Manager:
The installer installs ODBC Manager in the
~/Applications/Utilities directory.
Step 1: Install the ODBC Driver¶
To install the Snowflake ODBC driver for macOS:
If you choose the default directory when prompted, the installer installs the ODBC driver files in the following directories:
Step 2: Configure the ODBC Driver¶
To configure the ODBC driver for macOS, create one or more data source (DSNs), which are stored in the following files, depending on the type of DSN you create:
To create a DSN, either use ODBC Manager or edit the appropriate
odbc.ini file.
Creating a DSN Using ODBC Manager¶
To create a DSN in ODBC Manager:
If you are creating the first user or system DSN for the ODBC driver, ODBC Manager creates the
odbc.ini file in the corresponding directory for the type of DSN you are creating. If you are creating additional DSNs, ODBC Manageradds entries for each DSN to the existing odbc.ini file.
Creating a DSN by Adding an Entry in the
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |