Errors exporting to excel

Report works fine in HTML and exporting to PDF but when exporting to excel and opening the file we receive a notification that errors were detected and a repair was attempted. The repair notification states that the damage to the file was too extensive to repair and the file can be opened with only the raw tabular data (no formatting or charts).
This only happens with certain parameter values?
--
Message posted via http://www.sqlmonster.comThere are a couple of fixes out there for Excel. Take a look at
Microsoft.com for Excel\Reporting services issues.
If you have a good repro I can do in house, please send it to me.
--
| From: "William Nichols via SQLMonster.com" <forum@.SQLMonster.com>
| Subject: Errors exporting to excel
| Date: Fri, 28 Jan 2005 13:07:35 GMT
| Organization: http://www.SQLMonster.com
| Message-ID: <b4e260ddb47c48b7bf16a89e152b3412@.SQLMonster.com>
| X-Abuse-Report: http://www.SQLMonster.com/Uwe/NB/Abuse.aspx
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 178.67-18-207.reverse.theplanet.com 67.18.207.178
| Lines: 1
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:41174
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Report works fine in HTML and exporting to PDF but when exporting to
excel and opening the file we receive a notification that errors were
detected and a repair was attempted. The repair notification states that
the damage to the file was too extensive to repair and the file can be
opened with only the raw tabular data (no formatting or charts).
|
| This only happens with certain parameter values?
|
| --
| Message posted via http://www.sqlmonster.com
||||I've got the same problem!
I turned off the legend on the chart, and now it works perfectly!
Any ideas'
Try turning off the legend and let me know if that worked.
- Joel
"William Nichols via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b4e260ddb47c48b7bf16a89e152b3412@.SQLMonster.com...
> Report works fine in HTML and exporting to PDF but when exporting to excel
> and opening the file we receive a notification that errors were detected
> and a repair was attempted. The repair notification states that the
> damage to the file was too extensive to repair and the file can be opened
> with only the raw tabular data (no formatting or charts).
> This only happens with certain parameter values?
> --
> Message posted via http://www.sqlmonster.com

ErrorCode and ErrorColumn in Excel Destination

I am exporting records with errors to Excel using the Excel Destination tool. The ErrorColumn is a numeric. How do I find out which column it is?

If you want to do this manually (i.e. not programmatically), you can open the Advanced UI for the Excel Dest, and go to the "Input and Output Properties" tab. There, under "Excel Destination Input", you can look through the colums. As you click on each one, look for the "ID" property on the right that has the value you found in the ErrorColumn field of the error row.

Let me know if this helps or not.

Thanks,
Mark|||Hi

How would you do this programmatically? Ideally, I'd like to include the actual column name as another output column in my error destination table. Also, is it possible to obtain the error description as well as the ErrorCode (similar to what you might see in the Execution Results pane when debugging)?

Thanks

Rob|||Hi Rob

I want to do something similar but write out the column name to a table along with the data when rejected. Did you ever figure out how to do this?

Thanks

Marcus|||While it's fairly easy to add an ErrorDescription column on top of the ErrorCode, it's NOT so easy to add an ErrorColumnName on top of the ErrorColumn numeric ID value, because of all the ifs ands and buts that determine whether the column name is readily available or not. (For example, did the preceding component have synchronous or asynchronous outputs, and so forth.)

You can run your error output through a Script Component and try looping through the columns in its InputColumnCollection and VirtualInputColumnCollection looking for the ID value that you've got in the ErrorColumn column to see that this information is usually unavailable.

-Doug