bquackenbush
New Member
- Joined
- Aug 21, 2008
- Messages
- 9
This is the strangest - and probably most frustrating - problem I've run into with Excel in 20+ years working with the software. It's stumped our corp IT guys so far too, so hoping someone either has run into this problem or can give me some ideas how to troubleshoot.
We're running Excel 2013 Professional on Windows 10 Enterprise. We have Bromium and CrowdStrike installed by corporate policy. Everything is really locked down, so unlikely that this is a virus.
I have an Excel file that has several ODBC connections to an Oracle database using the 32 bit driver (version 11.02.00.03). I created the Oracle back end and everything on the database layer is tested and operational (it's a relatively simple DB application). The ODBC connections pull correctly into data tables in Excel. I created two data relationships in Excel to link the data tables together on two common fields in order to use slicers across all the data tables. There is no VBA code...just ODBC data pulls into one workbook and a few pivots connected to those tables by using the Excel data model.
This was all working beautifully on Friday. I was saving my work throughout the day without any problems. The workbook was exactly where I wanted it Friday COB. Yesterday I came in, opened the workbook, made a small change in the DB layer to streamline the SQL and re-pulled the data into the ODBC data tables. Everything still looked great. I hit File->Save and the workbook closed. It did not save the workbook. It didn't look like a typical crash. It just closed and wrote a zero-byte file to the folder where the file is located with a random 8 character file name (i.e. "C8972400"). I reopened Excel and tried again but same result. I restarted Windows - same result. I took it up to our IT guys and sent them the file. They opened the file on two different computers (one with Excel 2013 and one with Excel 2016) and they tried to save - same result. They uninstalled CrowdStrike and Bromium, but this didn't have any effect.
So, I opened the file, created an extra worksheet with and single value typed into cell A1 of "Test" and then deleted all other worksheets. So, the file had just one worksheet with one value in cell A1. I tried to save but got same result - file closed without saving and that strange 8-character zero-byte file.
Later in the day, I was messing around with the file, alt-tabbed away from it, and noticed a few minutes later that Excel closed on its own. I thought I was losing my mind, so re-opened it and just kept an eye on it throughout the rest of the day and noticed that Excel would sporadically close. Sometimes it happened while I was refreshing a data table. Sometimes it happened while I was alt-tabbed away and Excel was running in the background.
This doesn't happen with any other Excel file I'm working with, so it's got to be something with this file or with how this file is interacting with some other software on my machine.
I have really talented front-line IT help desk people and they're stumped, so they're going to escalate it to one of our Windows engineers. But, so far we've not been able to find anything in any event log to indicate what may be happening.
Any ideas what may be going on or even where I can look to research on my own?
Thanks
We're running Excel 2013 Professional on Windows 10 Enterprise. We have Bromium and CrowdStrike installed by corporate policy. Everything is really locked down, so unlikely that this is a virus.
I have an Excel file that has several ODBC connections to an Oracle database using the 32 bit driver (version 11.02.00.03). I created the Oracle back end and everything on the database layer is tested and operational (it's a relatively simple DB application). The ODBC connections pull correctly into data tables in Excel. I created two data relationships in Excel to link the data tables together on two common fields in order to use slicers across all the data tables. There is no VBA code...just ODBC data pulls into one workbook and a few pivots connected to those tables by using the Excel data model.
This was all working beautifully on Friday. I was saving my work throughout the day without any problems. The workbook was exactly where I wanted it Friday COB. Yesterday I came in, opened the workbook, made a small change in the DB layer to streamline the SQL and re-pulled the data into the ODBC data tables. Everything still looked great. I hit File->Save and the workbook closed. It did not save the workbook. It didn't look like a typical crash. It just closed and wrote a zero-byte file to the folder where the file is located with a random 8 character file name (i.e. "C8972400"). I reopened Excel and tried again but same result. I restarted Windows - same result. I took it up to our IT guys and sent them the file. They opened the file on two different computers (one with Excel 2013 and one with Excel 2016) and they tried to save - same result. They uninstalled CrowdStrike and Bromium, but this didn't have any effect.
So, I opened the file, created an extra worksheet with and single value typed into cell A1 of "Test" and then deleted all other worksheets. So, the file had just one worksheet with one value in cell A1. I tried to save but got same result - file closed without saving and that strange 8-character zero-byte file.
Later in the day, I was messing around with the file, alt-tabbed away from it, and noticed a few minutes later that Excel closed on its own. I thought I was losing my mind, so re-opened it and just kept an eye on it throughout the rest of the day and noticed that Excel would sporadically close. Sometimes it happened while I was refreshing a data table. Sometimes it happened while I was alt-tabbed away and Excel was running in the background.
This doesn't happen with any other Excel file I'm working with, so it's got to be something with this file or with how this file is interacting with some other software on my machine.
I have really talented front-line IT help desk people and they're stumped, so they're going to escalate it to one of our Windows engineers. But, so far we've not been able to find anything in any event log to indicate what may be happening.
Any ideas what may be going on or even where I can look to research on my own?
Thanks