Jan Update and Build 15002:DataFormat.Error: The input couldn't be recognized as a valid Excel docum

[Funkmiester]

NIGHTMARE!

I am building a couple of dashboards in desktop, done 60Hrs this week alone.

Working fine yestereday- all use excel files and tables as data sources

Today- Update inside windows 10 insiderPro build 15002 this morning

Update to Jan 2017 PowerBI

Now every dash won't update with the message 

DataFormat.Error: The input couldn't be recognized as a valid Excel document.

Every file opens fine in excel not corrupted, even tried with new data, same message

I've rolled back to an earlier Power BI but get the same error, any other ideas welcome.

Is there a setting in the build 15002 that doesn't recognise excel files as excel files???

[curth]

It looks like we're hitting some kind of bug in the CLR JIT. You can temporarily work around the problem by creating a new file in the "bin" subdirectory of the Power BI Desktop install directory with the name "Microsoft.Mashup.Container.NetFX40.exe.config". The contents should be

<configuration>
<runtime>
<useLegacyJit enabled="1" />
</runtime>
</configuration>

You'll need to restart Power BI Desktop for the change to take effect. This will force an older JIT to be used which will avoid the problem.

[curth]

Minor correction: it's actually a problem with NGEN and not the JIT. This workaround will prevent the NGEN'd image from being loaded and will therefore fix the problem.

[Funkmiester]

Oh Obviously, why didn't I think of that. 

3 weeks to get a technical workaround after we have all modified our source tables back to plain cells.

See in the world outside microsoft this is what you have done:

Me- Buy new tyres- invest heavily in time and effort to make them work on a special race car.

Me one random morning- "Oh no all 4 tyres on my car are flat"

Me to Tyre salesman-"Why did my tyres go flat they were fine yesterday"

Tyre salesman- ".............................." for 3 weeks

Me- go out buy new wheels and tyres, probably from a different supplier

Tyre salesman 3 weeks later- "Oh yes we came round and stuck a knife through your tyres because that's our new procedure now"

Tyre salesman "But it's OK if you are a materials expert you can cold weld the rubber using a high strength butyl epoxy compound and a special machine"

Me- "why the **@@("*&&^ did you stick a knife in my tyres, not tell me about it or even offer me new tyres.............."

Now this is how other companies do it

Tyre salesman " We had a new procedure through from head office to stick a knife in all the tyres we had sold customers. However we thought about our customers first and decided that maybe that would be something they would not like so we tried and tested it on our own cars first and realised that having a knife through our tyres is a really **@&& thing to happen and modified the procedure to avoid it."

Or even how about

Me and everyone else- "You broke a fundemantal bit of PowerBI"

Microsoft the next day- "we're very sorry, we didn't mean to do it, we're very sorry for all the time and money it has cost you, let us rush out an immediate patch via PBI or the win10 build"

"And again we are really are sorry"

Tell me again why I would ever reccommend a Microsoft product to anyone? Your marketting department seem to ask me every 2 minutes, perhaps you should copy them into this.......

[powerbi13]

Still don't have this issue resolved. 

Line 1: Source = Excel.Workbook(File.Contents([excel path and file name])),

Line 2: Directory_Sheet = Source{[Item="RRDirectory",Kind="Sheet"]}[Data],

Line 2 is throwing the error below:

DataFormat.Error: The input couldn't be recognized as a valid Excel document.
Details:
    Binary

On the "APPLIED STEPS" section on the right, when I click on line 1, I can see the sheets availabe in the excel document, but line 2 gives the error above.

I tried putting the config file in the bin director...still not working.  It's definitely a change in one of the recent builds or other because I haven't changed the files and it had been working fine for months.

[Anonymous]

I had the same issue. After four hours of investigations, I found a possible trick : the excel files should not contain hyperlinks. In mine, url's were mentionned with their hyperlinks.

[Anonymous]

I had the same issue. After hours of investigations, I found the possible issue : the excel files should not contain hyperlinks. In mine, url's were mentionned with their hyperlinks.