Export to Excel not working for certain users (Error Code: 0x80040216)

[James_McKie]

Several of our users have reported issues using the Export to Excel option from within our custom Model Driven apps.

This seems to be affecting all tables and all the different export options (open online, static worksheet sheet, etc)
They get the same issue on all different apps and across all environments.

After clicking the Export to Excel option, they receive an Unexpected Error popup as below with Error Code: 0x80040216

We're using Microsoft 365 Enterprise with latest Windows & Office updates installed.

We're using Edge browser and have tried clearing all Cookies and settings.
We've also checked that no files are awaiting attention in Excel and have tried Deleting cached files in Excel.

It seems client specific as a user logging on to a different PC seems to work, but the issue soon returns.

One user has had their laptop completely rebuilt, and although this fixed the issue initially, within a day the issue was occurring again on their laptop.

Has anyone seen this before or have suggestions on how to resolve the issue?

[Mosteckyj]

I have now had 2 different clients report the same issue.

I have tested and my account on both works fine.

Both client users with the issue are SysAdmins.

Other users who are SysAdmins are working fine.

Seems its quite a sitewide MS bug. Time to raise a support ticket and let them investigate.

[kchubala]

Experiencing the same error inside a model-driven app when trying to export to Static Excel Worksheet with myself (Sysadmin) and another user (non-admin) today however a 3rd user (SysAdmin) did not see the error.

I agree @Mosteckyj , weird bug. We've opened a case with the Power Platform support team, will post back once I hear from them.

[Nitrophil1]

Same here we are a consulting companie and my user (sysadmin) the excel export dont word on all the client power app but all of my coworkers are fine

[kchubala · Accepted solution]

MS got back to me this morning and confirmed the bug. They have determined the source of the issue and the product team is already working on it, but no ETA for a fix.

They did provide me with the two following workarounds:

Method 1: If you change the browser resolution to a different one & refresh your session Then most likely user will be able to successfully Export to Excel.
Try different browser zoom and OS resolutions such that width in network call has whole number.
In some cases, it may never be a whole number. Then, try to Export from the old Advanced Find.

Method 2: Turn OFF the new Advanced Find Feature in the Admin Center.
After this the Filter icon on the Top bar will open old Advanced Find dialog
Export works from here.

I successfully tested Method #1 by simply changing Zoom% in Edge browser from 90% to 100% (or 80%), refreshed browser, and was able to export a static Excel worksheet.

[Nicolai_Hardahl]

Hi @kchubala I also have a client facing this issue. Will you kindly update us, when you got a ETA of the bug fix. 

Thanks in advance.

[James_McKie]

I've just had a similar response from Microsoft support:

This is a known issue, the fix is going to deploy by 27th of February-2023 and We have identified the error is due to invalid width of layout xml, which should be an integer. 

Mitigation | Workaround:

1. Export through Advanced Find.
2. Zoom in/out the browser, refresh the tab, and export on UCI again.

[pallavi_khude]

Hi,

Our client also facing the same issue for some users.  Does Method #1 solve the issue?

[Sumedha7]

Hi Guys, Is this resolved by now? One of the users who had the issue informed its working now.

[Nicolai_Hardahl]

Hi @pallavi_khude and @Sumedha7 - it is not fixed before 27th of February. Method #2 mentioned above worked for my clients, simply changing the zoom of the webpage 😮