illegal xml character

Question

Post reply

illegal xml character

SqlServerDBA318

SSCrazy

Points: 2353
More actions
January 27, 2016 at 2:41 pm

#308094

Hello all,
I have been searching for an answer for awhile and no luck.
I have SSRS 2014 spitting out about 70 reports a month without any issue for last year, but now two are having the same issue.
When I go to save as an Excel file it shows this error when I try to open:
"Excel found unreadable content in specific file, do you want to recover" - I click yes and it is blank.
Replaced Part: /xl/worksheets/sheet1.xml part with XML error. Illegal xml character. Line 1, column 282473463.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>error077960_01.xml</logFileName><summary>Errors were detected in file 'C:\Users\\Desktop\WS_Print.xlsx'</summary><removedParts summary="Following is a list of removed parts:"><removedPart>Replaced Part: /xl/worksheets/sheet1.xml part with XML error. Illegal xml character. Line 1, column 282473463.</removedPart></removedParts></recoveryLog>
I am not a XML guy so no clue and just to clarify I see where it says Line 1, column 282473463, but still no luck finding issue.
Any direction would be appreciated!
Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

Alan Burstein SSC Guru Points: 61136 More actions · Answer 1

Just a guess but perhaps, before saving as Excel file, you could change:

<summary>Errors were detected in file 'C:\Users\\Desktop\WS_Print.xlsx'</summary>

To

<summary>Errors were detected in file ''C:\Users\\Desktop\WS_Print.xlsx''</summary>

Note the two single quotes instead of one.

"I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

-- Itzik Ben-Gan 2001

mister.magoo SSC-Forever Points: 47068 More actions · Answer 2

I would take a look at the xml being produced.

First step is to "unzip" the xlsx file after it has been created - before you try and open it with Excel.

You can use any standard "Zip" program such as 7-zip for this.

In the unzipped content, you will look for the file /xl/worksheets/sheet1.xml

Open that with Notepad++ or similar (or an actual xml editor) and check whether it has been truncated, thus corrupting the XML inside.

If the file appears to be valid XML, you could try locating the specific location it reports as a problem (Character 282473463) and see if anything looks "bad".

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);