Error using xlsread (line 249) Excel Worksheet could not be activated.

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.

[Robert Bunting]

Following up on the finding that doing "clear all" works, I find that doing "clear functions" prior to calling xlsread works.

However, there are still Excel processes that accumulate, which I kill in Task Manager.

I am running W10, MatLab 2018b, and Office 365. I have been working with Excel files for years, and this problem ("Error using xlsread (line 257) Excel Worksheet could not be activated.") only started happening today.

[S Deligeorges]

I have slight variatiuon on the problem. using Matlab R19b, windows 10. I can open an excel file once with xlsread, but every time after that I get the line 249 error. clear all does not fix it, restarting matlab does not fix it, rebooting the machine does not fix it. Matlab touching the file once had made all my data unreadable by Matlab. Any suggestions ?

[mehmet utku]

clear all worked for me thank you.

[yoav smith]

how to delete rows from an array

Answer 1

[Tobias Elve]

A 'clear all' does the trick; without restarting MATLAB

[Rafael Freire]

Worked flawless for me. Thank you

[杨 格]

It worked for me too.

[Nancy Mohamed]

It worked for me too, thank you.

[TESFAYE YIMAM MOHAMMAD]

Thanks, it works for me too.

[NILADRI]

Exactly!! Thank You so much

[Axel]

thanks!!

[Abid Morshed]

Thanks

Answer 2

[Ismaeel]

I had the same problem. After closing-reopening MATLAB, it worked just fine. I have no add-in plugin in Excel.

[KAE]

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.

Answer 3

[Walter Roberson]

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:

https://www.mathworks.com/matlabcentral/answers/98261-why-do-some-excel-processes-fail-to-terminate-after-using-xlsread-xlswrite-or-xlsfinfo-in-matlab

"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.

[Walter Roberson]

Another plug-in often mentioned as being a problem is Foxit.

Answer 4

[Rambod Naimi]

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!

[K E]

Please post any solution they give you! When I have this issue, sometimes restarting Matlab resolves it, and it will not recur when I run the program again.

[sreelatha Aihloor Subramanyam]

this helped me.Thanks

Answer 5

[Sean Desten]

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.

[Anders Simonsen]

Yes, switching to the first worksheet before saving solved the issue for me as well. Thanks a lot :-)

[MiguelMauricio]

I got the same problem. I deleted some worksheets and it was solved. Thanks

Answer 6

[M Zagorowska]

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.

[M Zagorowska]

Quick update - this happens only with Windows 10, with Windows 7 it works fine.

[Shashank Singh]

This error is occurring in Windows 7 too. I have MATLAB 2016Rb and Office 365.

[Cade Cockrell]

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

Answer 7

[Ambati Lakshmipathi]

I am also getting error as below

Error using xlsread (line 257)

Excel Worksheet could not be activated.

i am using 2019a version

Answer 8

[Anthony]

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.

Answer 9

[Md Azimur Rahman]

I had the same issue. After Removing Foxit add-in it worked.

Answer 10

[Flavio Ferrari]

Restart Matlab (R2019a) worked for me

Answer 11

[Kevin Rusch]

Can confirm that restarting worked even when

clear all;

didn't.

Answer 12

[Wenhui Qiao]

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!