Error using xlsread (line 249) Excel Worksheet could not be activated.
877 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Error using xlsread (line 249) Excel Worksheet could not be activated.
whenever I try xlsread, it just gives me this error I've tried reinstalling, but still did not work.
4 comentarios
mehmet utku
el 21 de Abr. de 2023
Editada: mehmet utku
el 21 de Abr. de 2023
clear all worked for me thank you.
Respuestas (12)
Tobias Elve
el 6 de Mayo de 2020
Editada: Tobias Elve
el 6 de Mayo de 2020
A 'clear all' does the trick; without restarting MATLAB
7 comentarios
Ismaeel
el 4 de Ag. de 2018
I had the same problem. After closing-reopening MATLAB, it worked just fine. I have no add-in plugin in Excel.
1 comentario
KAE
el 30 de Mayo de 2019
Editada: KAE
el 30 de Mayo de 2019
I get this problem when I have to stop a Matlab script (CTRL-C) which opens a large Excel file. The next time I run the script, it crashes and says 'Excel Worksheet could not be activated'. If i restart Matlab, it is resolved, but that is inconvenient. I'm using R2019a and I believe it was occuring in R2018b and possibly earlier. I have no Excel plugins that I know of.
Walter Roberson
el 6 de Oct. de 2016
Another case with the same problem: https://www.mathworks.com/matlabcentral/answers/275384-xlswrite-error-worksheet-could-not-be-activated
I have been wondering if this has to do with Excel plugins:
"Certain Excel add-ins may also prevent proper termination of Excel. Some known add-ins that might cause issues are Broadcom's "Send to Bluetooth" add-in (btsendto_office.dll) and Bloomberg's TaskpaneHost add-in. Disabling the add-ins that cause issues is a possible workaround."
There have been other reports having to do with Excel plugins that I cannot seem to find at the moment. I suggest going into Excel and seeing if you have any plugins active, and if you do then disabling them and then trying again in MATLAB.
1 comentario
Rambod Naimi
el 10 de Nov. de 2016
I am having similar issues with the Excel. I think i have narrowed it down to the fact that it takes longer than 5 seconds on my machine to open the file. there is a actTimeout which is internal to matlab. I don't know how to increase this value to check. but the message is coming from openExcelWorkbook.m file line 33. so i think this is the main issue with some PC's, the time to create a file and verify it was successful is longer than 5 seconds! I have popped the question to mathworks, hope they can answer!
2 comentarios
Sean Desten
el 27 de Feb. de 2017
In my case, there were multiple worksheets in the Excel Workbook I was opening. In my code, I was opening first worksheet #1, then worksheet #2. But when opening my workbook, it was open to #2. Switching to #1 in Excel, then saving, fixed the issue.
However, I could not replicate the bug by opening up the Excel book, switching to #2 again and saving (this should have been the initial state that was causing the bug). The code proceeded to open both worksheets without any issue.
Potentially, Excel got stuck in some sort of weird state that 'locked' the worksheets and prevented them from being activated by MATLAB (I'm using locked because I don't know a better word to use - I do not mean actual locking of the worksheet). Switching worksheets and saving may have switched Excel to a more normal state. For reference, I'm using Excel 2016 and MATLAB R2016b.
2 comentarios
Anders Simonsen
el 21 de Abr. de 2017
Yes, switching to the first worksheet before saving solved the issue for me as well. Thanks a lot :-)
MiguelMauricio
el 4 de Ag. de 2017
I got the same problem. I deleted some worksheets and it was solved. Thanks
M Zagorowska
el 7 de Sept. de 2017
I have the same problem - it appears when I save something to Excel using Matlab (this part is OK), then open&close the Excel file outside Matlab, and then try to save something with Matlab to the same file (different rows/worksheet) - this is when I get 'Excel Worksheet could not be activated.' After looking into Windows Task Manager, I can see that the Excel process is not closed - so I end it manually and Matlab works again. Probably not the best way to solve it, but, hey, it works ;) Any official solution would be appreciated, though.
3 comentarios
Shashank Singh
el 5 de Feb. de 2018
Editada: Shashank Singh
el 5 de Feb. de 2018
This error is occurring in Windows 7 too. I have MATLAB 2016Rb and Office 365.
Cade Cockrell
el 9 de Abr. de 2019
I belive it is due to a corrupted file. Try resaving the excel file under a different name as a new file. This worked for me
Ambati Lakshmipathi
el 21 de Mayo de 2019
I am also getting error as below
Error using xlsread (line 257)
Excel Worksheet could not be activated.
i am using 2019a version
0 comentarios
Anthony
el 1 de Oct. de 2017
I had this error, but it was resolved after applying a MS office update that I had been dragging my feet on for some time.
0 comentarios
Md Azimur Rahman
el 10 de Mayo de 2018
I had the same issue. After Removing Foxit add-in it worked.
0 comentarios
Kevin Rusch
el 13 de Ag. de 2020
Can confirm that restarting worked even when
clear all;
didn't.
0 comentarios
Wenhui Qiao
el 1 de Mzo. de 2022
Hi, I met with the same problem and finally figured out these excels were generated and may still in use by another software. When I closed this software, my program run without that error. Thanks!
0 comentarios
Ver también
Categorías
Más información sobre Data Import from MATLAB en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!