Open in Excel result in error

sjobrf

When "Open in Excel" from SSMS. I get this error (see attachment Err_01)

The recovery log says:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">

<logFileName>error172600_01.xml</logFileName>

<summary>Errors were detected in file 'C:\Users\jb6095\AppData\Local\Temp\rut1mgpk.na1\Exported results 2022-11-30_09-26-25.xlsx'</summary>

<repairedParts>

<repairedPart>Repaired Part: /xl/worksheets/sheet1.xml part with XML error.  HRESULT 0x8000ffff Line 1, column 0.</repairedPart>

</repairedParts>

</recoveryLog>

The resulting error (see attachment Err_02)

The generated Excel file.

Please find a solution fast.

jl@energidanmark.dk

Resently I also began to get this exact error.
I have just updated SQL Prompt to 10.13, already have the newest SSMS 18.12.1, and Excel is 2016 64 bit 16.0.5369.
And i still got the error.

mikecare

I get the same error.  Also when pasting into Excel.  it puts all data into the same column

ATurner

Hi All

This is currently a known issue and the development team are looking into this. 

mrjeffjohnston

Is there any update here?

Sarah B

I'm please to advise that a fix for this issue has been included in the latest release of SQL Prompt (v.10.13.4) 
 

sjobrf

I have installed v.10.13.4 and try to open in excel.

But I still get and error

The message is:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">

<logFileName>error286760_01.xml</logFileName>

<summary>Errors were detected in file 'C:\Users\xxxx\AppData\Local\Temp\een4du4m.bpk\Exported results 2023-01-19_16-18-56.xlsx'</summary>

<repairedRecords>

<repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet1.xml part</repairedRecord>

</repairedRecords>

</recoveryLog>

So it the fix is not sufficient 

markb2

I have the same problem.

Sql Prompt 10.13.4.32349

Excel for Microsoft 365 MSO (16.0.13801.21072) 64-bit

SSMS v18.12.1

and same problem with SSMS v19.0.1

Jon_Kirkwood

Hi all, 

Thank you for your updates and your patience as this is investigated.
Our development team has accepted this into their backlog to be worked on. 
They have advised a bug reference # TBE-51 and is expected to be resolved as part of a future patch of SQL Prompt. 

A potential workaround is reverting to v10.12.2 where this is reported as working
Download link: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.12.2.28458.exe

When a patch is released that includes a fix for this issue I will endeavor to update this forum post. 
Otherwise please monitor the release page for confirmation of fix after patch v10.13.5
https://documentation.red-gate.com/sp/release-notes-and-other-versions/sql-prompt-10-13-release-notes