Unable to select table of excel data source due to update Microsoft Office Excel

Before I could only use *.xls files to use for data behind the tests of Telerik and now when I use *.xlsx it works.

Before update of Microsoft Office:

- I could use *.xls
- I could not use *.xlsx

After update of Microsoft Office:

- I can not use *.xls
- I can use *.xlsx

I have a workaround, so I will change all my files to *.xlsx but this still seems important to investigate what is causing this.

 

Hi Martijn,

Thank you for reaching us out.

I suppose the issue you have faced is listed here along with a solution. Please give it a try and let me know if you would need any further assistance.

Thanks in advance!

Regards,
Elena Tsvetkova
Progress Telerik

Hi,

I have exactly the same problem - all my scripts suddenly can't read my excel files.  I have tried saving as .xlsx but when then trying to bind to that file I am still not able to select the table.  Martijn is all you did just open in Excel and save as the *.xlsx?  I have hundreds of data driven scripts and now can't use a single one, right in the middle of release testing!!

Please Elena - that solution isn't working for me and I need further assistance. To reiterate, I ran scripts yesterday data bound to *.xls files, today none of them work and cannot select the table to bind them again to work.  I have tried removing the binding, deleting the spreadsheet, adding again in either *.xls or *.xlsx format and tried re-binding and nothing allowing me to data drive my scripts using excel as I cannot select the table.  Please help anyone?

Thanks

Helen

Hi Helen,

I saved the excel (*.xls) to (*.xlsx) and rebind every single test that is bind to a test since it is actual a different file.

What I did exactly was:

- Copy *.xls files to another folder
- Open the *.xls
- Save the *.xls to *.xlsx
- Open Telerik Test Studio
- Remove Data Binding for every test related to the data source (right click on test in project explorer which has a binding)
- Go to Manage
- Remove the *.xls
- Press + to add new datasource (choose *.xlsx)
- Select test you want to bind to a datasource
- Go to Bind Test

This should be done for every test that has a binding with that data source. You should remember the binding rows and tables you choose before and set that.

@Elena: This is very cumbersome so it would be nice if this will be fixed as soon as possible because we need to change all bindings. If it was only the files that needed to be changed it wouldn't really matter. Could you maybe investigate this issue in combination with the update of Microsoft Office that took place at 11th of October?

Probably either one of the updates below caused the issue:

Update voor Microsoft Excel 2016 (KB4011166) 32-bits editie
Update voor Microsoft Office 2016 (KB4011167) 32-bits editie
Beveiligingsupdate voor Microsoft Office 2016 (KB2920723) 32-bits editie
Beveiligingsupdate voor Microsoft Office 2016 (KB4011185) 32-bits editie

Thanks and regards,

Martijn

Hi Elena,
I have the same problem and I can't find the solution which you mean.
I tried to change .xls to .xlsx. It didn't work.

Some more details from my side.

My problems began from Windows updates:

1. KB4041676 for Windows 10

2. KB4041693 for Windows Server 2012 R2

I attached the screens.

I don't have installed MS Office on a machine which binds/runs tests.

Hi All,

Martijn,  Thanks for that, that is exactly what I did and doesn't work for me.  Even creating a new xlsx file from scratch and a new script cannot see the tables to bind.  I too didn't have an Office Update.  Mine I believe is caused by the patches Ivan refers to.

Ivan, Yes that is exactly the same as me.  If I uninstall the KB4041676 update all my scripts work again using the .xls.  It appears there is an issue on the patch - seems a load of MS applications have gone to pot from this update, something to do with all of these sitting on the Jet ODBC data source driver???

Problem is because it is a security update it reinstalls next power off!  So I uninstalled again this morning to be able to use my scripts but it does have some security updates in it and I can't go through this process constantly to be able to use the software :-(

 

Hi gyus,

Thank you all for the support and efforts in identifying the root cause for the observed misbehavior. 

Please allow us some time to identify what that update changes in regards to the Excel files used in Test Studio. Here is a public feedback in our portal which progress you could follow, add any further details, vote for it to increase its importance and etc. 

I hope this will be fixed and introduced as soon as possible. Meanwhile you could try uninstalling the update KB4041676 as a workaround. 

Please if anyone has anything else to add or raise any concerns feel free to continue the discussion. 

Thank you all in advance for your understanding! 

Regards,
Elena Tsvetkova
Progress Telerik

Hi Elena 

Me and one my colleague have a same problem, we tried by uninstalling the update 'KB4041676' in windows 10, problem get resolved. But in windows 7 we don't know which update we need to uninstall? 

 

Thank you 

Sai

Hi Sai,

Thanks for your cooperation. 

Unfortunately I also do not have a machine with WIndows 7 to double check that. What I could confirm is that the Update was pushed by Microsoft on 10/10/2017. having that on mind you could double check which are the updates installed on that day or few days later depending on your company policies and read further on the web for these particular updates. 

Thanks in advance for your understanding! 

Regards,
Elena Tsvetkova
Progress Telerik

Hi, 

Was the fix for this issuer implemented? I am still unable to make a selection.

Thank you 

Hello Masha,

As far as I am aware Microsoft released further security updates for all supported Windows versions that fix the introduced issue. Though I would recommend you double check that on the Microsoft page as per your exact Windows version. 

In case there is anything else I could be helpful with please let me know! Thanks! 

Regards,
Elena Tsvetkova
Progress Telerik

Future reference, this fixed my issue.

https://www.microsoft.com/en-us/download/confirmation.aspx?id=23734

Hi Herb,

Thank you for the note. The information you have found is also available in our documentation, but I have missed to add reference to that. 

Though, thanks to you, I will share it once again for anyone who encounters the same misbehavior. 

Regards,
Elena Tsvetkova
Progress Telerik