"The input couldn't be recognized as a valid Excel document."

%3CLINGO-SUB%20id%3D%22lingo-sub-275998%22%20slang%3D%22en-US%22%3ERe%3A%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-275998%22%20slang%3D%22en-US%22%3EDid%20you%20try%20the%20solution%20provided%20by%20Sergei%20in%20his%20first%20post%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%22it's%20enough%20to%20open%20the%20file%20in%20Excel%20and%20save%20it%20(without%20any%20changes)%20%E2%80%93%20Excel%20is%20clever%20enough%20to%20fix%20the%20scheme.%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251262%22%20slang%3D%22en-US%22%3ERe%3A%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251262%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20625px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F49489i8DD254125FAD58C1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22errore.png%22%20title%3D%22errore.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20face%20the%20same%20problem.%20I%20don't%20know%20why%20first%203%20tables%20are%20ok%2C%20but%20the%20next%20two%20no.%20How%20can%20I%20fix%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-63798%22%20slang%3D%22en-US%22%3ERe%3A%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-63798%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Todd%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECombine%20Binaries%20starts%20working%20with%20Excel%20workbook%20formats%20from%20January%20this%20year%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.office.com%2F2017%2F02%2F08%2Fjanuary-2017-updates-for-get-transform-in-excel-2016-and-the-power-query-add-in%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.office.com%2F2017%2F02%2F08%2Fjanuary-2017-updates-for-get-transform-in-excel-2016-and-the-power-query-add-in%2F%3C%2FA%3E%2C%20i%20guess%20from%20build%207668.2066.%20On%20earlier%20builds%20it%20worked%20only%20with%20CSV%20(or%20txt)%20formats.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20old%20builds%20available%20and%20can't%20check%20how%20Combine%20Binaries%20worked%20before.%20Now%20it%20in%20most%20cases%20correctly%20recognizes%26nbsp%3Bfile%20format%20and%20use%20Excel.Workbook%20or%20Csv.Document%20functions%20depends%20on%20file%20format.%20Perhaps%20on%20earlier%20version%20connector%20was%20not%20so%20clever%20and%26nbsp%3Bgave%20an%20error%20what%20can't%20recognize%20the%20format.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20easy%20to%20check%20if%20try%20to%20open%20Excel%20workbook%20by%20From%20File-%26gt%3BFrom%20CSV%2C%20exactly%20the%20same%20connector%26nbsp%3Bas%20within%20Combine%20Binaries.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20that's%20bit%20different%20story.%20In%20brief%2C%20in%20your%20situation%20PQ%20analyzes%20which%20actual%20format%20the%20file%20has%20and%2C%20if%20can%2C%20use%20proper%20connector%20independently%20on%20which%20UI%20menu%20you%20use%20to%20connect%20the%20file%20(latest%20builds)%20or%20give%20an%20error%20(older%20builds).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20case%20we%20connect%20to%20the%20file%20with%20proper%20connector%20which%20has%20to%20work%20with%20our%20file%20format%2C%20but%20PQ%20can't%20parse%20the%20file%20due%20to%20internal%20errors%20in%20XML%20structure%20of%20the%20file%20(more%20exactly%2C%20non-standard%20XML%20configuration%20from%20PQ%20point%20of%20view).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-63630%22%20slang%3D%22en-US%22%3ERe%3A%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-63630%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20this%20error%20but%20it%20seems%20to%20be%20computer%20specific%2C%20or%26nbsp%3Bmore%20accurately%20Excel%20version%20specific.%20Using%20the%20same%20source%20files%2C%20a%20Power%20Query%20%7C%20Combine%20Binaries%20will%20work%20from%20one%20computer%20but%20not%20another.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Excel%20365%20ProPlus%20version%201701%20build%207766.2071%20(First%20Release%20for%20Deferred%20Channel)%20it%20works%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Excel%20365%20ProPlus%20version%201609%20build%207369.2127%20(Deferred%20Channel%20updates)%20I%20get%20the%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%20error.%20Updated%20from%20Current%20Channel%20to%20version%201702%20build%207870.2038%20and%20the%20Combine%20Binaries%20worked%20without%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EScope%3A%20Combine%20Excel%20rows%20from%26nbsp%3Bmultiple%20similarly%20formatted%20excel%20sheets%20into%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50475%22%20slang%3D%22en-US%22%3E%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50475%22%20slang%3D%22en-US%22%3E%3CP%3ESuch%20alert%20could%20appear%20when%20you%20try%20to%20use%20Power%20BI%20connector%20on%20Excel%20file.%20It's%26nbsp%3Bunderstandable%20if%20the%20source%20file%20is%20corrupted%20and%20can't%26nbsp%3Bbe%20opened%20in%20Excel.%20However%2C%20it%20looks%20strange%20if%20Excel%20opens%20the%20file%20in%20question%20and%20shows%20nothing%20wrong.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBased%20on%20our%20experience%20above%20is%20usually%20means%20what%20something%20is%20wrong%20with%20XML%20scheme%20of%20the%20Excel%20workbook.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMushup%20trace%20(Data-%26gt%3BNew%20Query-%26gt%3BQuery%20Options-%26gt%3BDiagnostics-%26gt%3BEnable%20tracing)%20could%20give%20some%20additional%20information%2C%20but%20often%20not%20enough%20to%20find%20the%20reason.%3C%2FP%3E%3CP%3EWe%20had%20two%20main%20scenarios%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EXML%20scheme%20is%20not%20complete%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EUsually%20if%20Excel%20file%20was%20generated%20by%20third-party%20tool.%20Such%20tool%20could%20generate%20quite%20limited%20XML%20scheme%20which%20is%20enough%20to%20open%20the%20file%20in%20Excel%20and%20to%20work%20with%20it%2C%20but%20not%20enough%20for%20Power%20BI%20connector.%20As%20an%20example%2C%20trace%20log%20shows%3C%2FP%3E%3CPRE%3E%5BDataFormat.Error%5D%20The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%5Cr%5CnStackTrace%3A%5Cn%E2%80%A6%0A%E2%80%A6%0A%5BDataFormat.Error%5D%20We%20couldn't%20find%20a%20part%20named%20'%2Fxl%2FsharedStrings.xml'%20in%20the%20Excel%20package.%5Cr%5CnStackTrace%3A%5Cn%E2%80%A6%3C%2FPRE%3E%3CP%3ESuch%20case%20is%20easy%20to%20fix%20%E2%80%93%20it's%26nbsp%3Benough%20to%20open%20the%20file%20in%20Excel%20and%20save%20it%20(without%20any%20changes)%20%E2%80%93%20Excel%20is%20clever%20enough%20to%20fix%20the%20scheme.%20For%20the%20routine%20regular%20tasks%20we%20use%20poweshell%20script%20which%20does%20exactly%20the%20same%20in%20background.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EThere%20is%20the%20link%20within%20Excel%20file%20which%20is%20not%20recognizable%20as%20valid%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EUsually%20if%20Excel%20file%20is%20synced%2Fkept%20with%20some%20cloud%20storage.%20One%20of%20the%20variants%2C%20wrong%20link%20could%20appear%20with%20copy%2Fpaste%20from%20another%20such%20file.%20That%20could%20be%20active%20link%20in%20one%20of%20the%20cells%3B%20or%20the%20link%20within%20conditional%20formatting%20formula%3B%20or%20even%20the%20link%20which%20actually%20isn't%26nbsp%3Bused%20by%20Excel%20but%20kept%20somewhere%20inside%20the%20scheme.%20For%20example%2C%20in%20one%20of%20the%20files%20I%20found%20in%20Data-%26gt%3BConsolidate-%26gt%3BAll%20references%20the%20link%20like%3C%2FP%3E%3CPRE%3E'%5C%5Cdrive.tresorit.com%407235%5CTresors%E2%80%A6.%5C%5Bfile.xlsx%5DSheet'!%24AC%246%3A%24AC%24357%3C%2FPRE%3E%3CP%3Eon%20the%20file%20which%20was%20deleted%20long%20ago%20and%20isn't%26nbsp%3Bused%2C%20but%20for%20some%20strange%20reason%20the%20link%20was%20kept%20within%20the%20scheme.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20for%20such%20case%20trace%20log%20doesn't%26nbsp%3Bgive%20enough%20information%20to%20localize%20the%20issue%2C%20it%20looks%20like%3C%2FP%3E%3CPRE%3E%5BDataFormat.Error%5D%20The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%5Cr%5CnStackTrace%3A%5Cn%E2%80%A6%0A%E2%80%A6%0AnExceptionType%3A%20System.UriFormatException%2C%20System%2C%20Version%3D4.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089%5Cr%5CnMessage%3A%20Invalid%20URI%3A%20The%20hostname%20could%20not%20be%20parsed.%5Cr%5CnStackTrace%3A%5Cn%3C%2FPRE%3E%3CP%3EPerhaps%20I%20have%20not%20enough%20knowledge%20for%20more%20straight%20forward%20localization%20of%20the%20problem%2C%20but%20the%20only%20way%20is%20to%20exclude%20Excel%20file%20parts%20one%20by%20one%20and%20check%20if%20the%20issue%20disappeared.%20Another%20way%20could%20be%20to%20unzip%20Excel%20file%20and%20check%20if%20wookbook.xml%20or%20sheetNN.xml%20have%20something%20suspicious%20inside.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-50475%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBI%20%26amp%3B%20Data%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGet%20%26amp%3B%20Transform%20Data%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1565403%22%20slang%3D%22en-US%22%3ERe%3A%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1565403%22%20slang%3D%22en-US%22%3E%3CP%3EI%20realize%20this%20is%20an%20older%20post%2C%20but%20relevant%20nonetheless.%20I%20got%20the%20error%20of%20input%20not%20recognized%20as%20valid%20Excel%20document%2C%20and%20was%20able%20thanks%20to%20your%20instructions%20to%20save%20the%20file%20without%20changes%20and%20open%20the%20file%20in%20Power%20BI.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20challenge%20I%20have%20is%20that%20I%20have%20a%20server%20folder%20full%20of%20these%20reports%20that%20I%20would%20like%20to%20transform%20and%20combine%20within%20Power%20BI%20based%20on%20folder%20location%2C%20without%20having%20to%20open%20and%20save%20each%20individual%20file.%20Do%20you%20know%20of%20a%20way%20within%20Power%20BI%20to%20resolve%20the%20XML%20issue%2C%20or%20perhaps%20something%20I%20can%20do%20with%20powershell%20to%20import%20the%20%22restored%22%20files%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20background%3A%20the%20Excel%20files%20I'm%20trying%20to%20import%20are%20created%20and%20stored%20through%20an%20SAP%20batch%20job.%20Here's%20some%20information%20I%20copied%20from%20the%20Tracer%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E04T15%3A20%3A36.0872649Z%22%2C%22Action%22%3A%22ExcelReaderOpenXml%2FExceptionHandler%22%2C%22HostProcessId%22%3A%2214184%22%2C%22PartitionKey%22%3A%22Section1%2FEXLIST_500_APAC_20200803030134%2FSource%22%2C%22Exception%22%3A%22Exception%3A%5Cr%5CnExceptionType%3A%20System.InvalidOperationException%2C%20mscorlib%2C%20Version%3D4.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089%5Cr%5CnMessage%3A%20Specified%20part%20does%20not%20exist%20in%20the%20package.%5Cr%5CnStackTrace%3A%5Cn%20%20%20at%20System.IO.Packaging.Package.GetPart(Uri%20partUri)%5Cr%5Cn%20%20%20at%20Microsoft.Mashup.Engine1.Library.Excel.ExcelReaderOpenXml.RelationshipHidingPackage.GetPartCore(Uri%20partUri)%5Cr%5Cn%20%20%20at%20System.IO.Packaging.Package.GetPartHelper(Uri%20partUri)%5Cr%5Cn%20%20%20at%20System.IO.Packaging.Package.GetPart(Uri%20partUri)%5Cr%5Cn%20%20%20at%20DocumentFormat.OpenXml.Packaging.OpenXmlPart.Load(OpenXmlPackage%20openXmlPackage%2C%20OpenXmlPart%20parent%2C%20Uri%20uriTarget%2C%20String%20id%2C%20Dictionary%602%20loadedParts)%5Cr%5Cn%20%20%20at%20DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage%20openXmlPackage%2C%20OpenXmlPart%20sourcePart%2C%20PackageRelationshipCollection%20relationshipCollection%2C%20Dictionary%602%20loadedParts)%5Cr%5Cn%20%20%20at%20DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage%20openXmlPackage%2C%20OpenXmlPart%20sourcePart%2C%20PackageRelationshipCollection%20relationshipCollection%2C%20Dictionary%602%20loadedParts)%5Cr%5Cn%20%20%20at%20DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage%20openXmlPackage%2C%20OpenXmlPart%20sourcePart%2C%20PackageRelationshipCollection%20relationshipCollection%2C%20Dictionary%602%20loadedParts)%5Cr%5Cn%20%20%20at%20DocumentFormat.OpenXml.Packaging.OpenXmlPackage.Load()%5Cr%5Cn%20%20%20at%20DocumentFormat.OpenXml.Packaging.SpreadsheetDocument.Open(Package%20package%2C%20OpenSettings%20openSettings)%5Cr%5Cn%20%20%20at%20Microsoft.Mashup.Engine1.Library.Excel.ExcelReaderOpenXml.ReadTablesUnguarded()%5Cr%5Cn%20%20%20at%20Microsoft.Mashup.Engine1.Library.Excel.ExcelReaderOpenXml.ReadTables()%5Cr%5Cn%5Cr%5Cn%5Cr%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20tips%2Fadvice!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1741563%22%20slang%3D%22en-US%22%3ERe%3A%20%22The%20input%20couldn't%20be%20recognized%20as%20a%20valid%20Excel%20document.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1741563%22%20slang%3D%22en-US%22%3E%3CP%3Ethis%20error%20is%20specific%20to%20excel%202016%20whereas%20i%20did%20not%20observe%20the%20same%20in%20excel%20365.%3C%2FP%3E%3CP%3EAny%20suggestions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

Such alert could appear when you try to use Power BI connector on Excel file. It's understandable if the source file is corrupted and can't be opened in Excel. However, it looks strange if Excel opens the file in question and shows nothing wrong.

 

Based on our experience above is usually means what something is wrong with XML scheme of the Excel workbook.

 

Mushup trace (Data->New Query->Query Options->Diagnostics->Enable tracing) could give some additional information, but often not enough to find the reason.

We had two main scenarios

 

  • XML scheme is not complete

Usually if Excel file was generated by third-party tool. Such tool could generate quite limited XML scheme which is enough to open the file in Excel and to work with it, but not enough for Power BI connector. As an example, trace log shows

[DataFormat.Error] The input couldn't be recognized as a valid Excel document.\r\nStackTrace:\n…
…
[DataFormat.Error] We couldn't find a part named '/xl/sharedStrings.xml' in the Excel package.\r\nStackTrace:\n…

Such case is easy to fix – it's enough to open the file in Excel and save it (without any changes) – Excel is clever enough to fix the scheme. For the routine regular tasks we use poweshell script which does exactly the same in background.

 

  • There is the link within Excel file which is not recognizable as valid

Usually if Excel file is synced/kept with some cloud storage. One of the variants, wrong link could appear with copy/paste from another such file. That could be active link in one of the cells; or the link within conditional formatting formula; or even the link which actually isn't used by Excel but kept somewhere inside the scheme. For example, in one of the files I found in Data->Consolidate->All references the link like

'\\drive.tresorit.com@7235\Tresors….\[file.xlsx]Sheet'!$AC$6:$AC$357

on the file which was deleted long ago and isn't used, but for some strange reason the link was kept within the scheme.

 

Unfortunately for such case trace log doesn't give enough information to localize the issue, it looks like

[DataFormat.Error] The input couldn't be recognized as a valid Excel document.\r\nStackTrace:\n…
…
nExceptionType: System.UriFormatException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\r\nMessage: Invalid URI: The hostname could not be parsed.\r\nStackTrace:\n

Perhaps I have not enough knowledge for more straight forward localization of the problem, but the only way is to exclude Excel file parts one by one and check if the issue disappeared. Another way could be to unzip Excel file and check if wookbook.xml or sheetNN.xml have something suspicious inside.

6 Replies

I have this error but it seems to be computer specific, or more accurately Excel version specific. Using the same source files, a Power Query | Combine Binaries will work from one computer but not another.

 

Using Excel 365 ProPlus version 1701 build 7766.2071 (First Release for Deferred Channel) it works fine.

 

Using Excel 365 ProPlus version 1609 build 7369.2127 (Deferred Channel updates) I get the "The input couldn't be recognized as a valid Excel document." error. Updated from Current Channel to version 1702 build 7870.2038 and the Combine Binaries worked without error.

  

Scope: Combine Excel rows from multiple similarly formatted excel sheets into one.

Hi Todd,

 

Combine Binaries starts working with Excel workbook formats from January this year https://blogs.office.com/2017/02/08/january-2017-updates-for-get-transform-in-excel-2016-and-the-pow..., i guess from build 7668.2066. On earlier builds it worked only with CSV (or txt) formats.

 

I have no old builds available and can't check how Combine Binaries worked before. Now it in most cases correctly recognizes file format and use Excel.Workbook or Csv.Document functions depends on file format. Perhaps on earlier version connector was not so clever and gave an error what can't recognize the format.

 

That's easy to check if try to open Excel workbook by From File->From CSV, exactly the same connector as within Combine Binaries.

 

Anyway, that's bit different story. In brief, in your situation PQ analyzes which actual format the file has and, if can, use proper connector independently on which UI menu you use to connect the file (latest builds) or give an error (older builds).

 

In my case we connect to the file with proper connector which has to work with our file format, but PQ can't parse the file due to internal errors in XML structure of the file (more exactly, non-standard XML configuration from PQ point of view). 

 

 

 

 

errore.png

 

I face the same problem. I don't know why first 3 tables are ok, but the next two no. How can I fix this?

Did you try the solution provided by Sergei in his first post?

"it's enough to open the file in Excel and save it (without any changes) – Excel is clever enough to fix the scheme."

I realize this is an older post, but relevant nonetheless. I got the error of input not recognized as valid Excel document, and was able thanks to your instructions to save the file without changes and open the file in Power BI. 

 

The challenge I have is that I have a server folder full of these reports that I would like to transform and combine within Power BI based on folder location, without having to open and save each individual file. Do you know of a way within Power BI to resolve the XML issue, or perhaps something I can do with powershell to import the "restored" files?

 

Some background: the Excel files I'm trying to import are created and stored through an SAP batch job. Here's some information I copied from the Tracer:

 

04T15:20:36.0872649Z","Action":"ExcelReaderOpenXml/ExceptionHandler","HostProcessId":"14184","PartitionKey":"Section1/EXLIST_500_APAC_20200803030134/Source","Exception":"Exception:\r\nExceptionType: System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\r\nMessage: Specified part does not exist in the package.\r\nStackTrace:\n   at System.IO.Packaging.Package.GetPart(Uri partUri)\r\n   at Microsoft.Mashup.Engine1.Library.Excel.ExcelReaderOpenXml.RelationshipHidingPackage.GetPartCore(Uri partUri)\r\n   at System.IO.Packaging.Package.GetPartHelper(Uri partUri)\r\n   at System.IO.Packaging.Package.GetPart(Uri partUri)\r\n   at DocumentFormat.OpenXml.Packaging.OpenXmlPart.Load(OpenXmlPackage openXmlPackage, OpenXmlPart parent, Uri uriTarget, String id, Dictionary`2 loadedParts)\r\n   at DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart sourcePart, PackageRelationshipCollection relationshipCollection, Dictionary`2 loadedParts)\r\n   at DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart sourcePart, PackageRelationshipCollection relationshipCollection, Dictionary`2 loadedParts)\r\n   at DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart sourcePart, PackageRelationshipCollection relationshipCollection, Dictionary`2 loadedParts)\r\n   at DocumentFormat.OpenXml.Packaging.OpenXmlPackage.Load()\r\n   at DocumentFormat.OpenXml.Packaging.SpreadsheetDocument.Open(Package package, OpenSettings openSettings)\r\n   at Microsoft.Mashup.Engine1.Library.Excel.ExcelReaderOpenXml.ReadTablesUnguarded()\r\n   at Microsoft.Mashup.Engine1.Library.Excel.ExcelReaderOpenXml.ReadTables()\r\n\r\n\r

 

Thanks in advance for any tips/advice!

this error is specific to excel 2016 whereas i did not observe the same in excel 365.

Any suggestions?