Showing posts with label garbage. Show all posts
Showing posts with label garbage. Show all posts

Sunday, February 26, 2012

Export To Excel Error

When exporting to pdf format, everything is fine.
However, exporting to excel leads to some garbage.
Can anyone tell me what is going on?
Output similar to the following is displayed in the excel file
MIME-Version: 1.0
X-Document-Type: Workbook
Content-Type: multipart/related;boundary="--=_NextPart_01C35DB7.4B204430"
This is a multi-part message in MIME format.
--=_NextPart_01C35DB7.4B204430
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: base64
Content-Location: file:///c:/Report.htm
77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm
--=_NextPart_01C35DB7.4B204430
Content-Type: text/html
Content-Transfer-Encoding: base64
Content-Location: file:///c:/Sheet1.htm
77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbW
9sc3Bhbj0iMyIgc3R5bGU9ImJvcmRlci1yaWdodDow
--=_NextPart_01C35DB7.4B204430
Content-Type: image/bmp
Content-Transfer-Encoding: base64
Content-Location: file:///c:/4.bmpAre you using MRS with service pack #1? If not, and you are exporting to an
older version of Excel you can see garbage. If you are on SP1, then I'm not
sure what could be going on.
"Sanjeev" wrote:
> When exporting to pdf format, everything is fine.
> However, exporting to excel leads to some garbage.
> Can anyone tell me what is going on?
> Output similar to the following is displayed in the excel file
> MIME-Version: 1.0
> X-Document-Type: Workbook
> Content-Type: multipart/related;boundary="--=_NextPart_01C35DB7.4B204430"
> This is a multi-part message in MIME format.
> --=_NextPart_01C35DB7.4B204430
> Content-Type: text/html;
> charset="utf-8"
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/Report.htm
> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm
> --=_NextPart_01C35DB7.4B204430
> Content-Type: text/html
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/Sheet1.htm
> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbW
> 9sc3Bhbj0iMyIgc3R5bGU9ImJvcmRlci1yaWdodDow
> --=_NextPart_01C35DB7.4B204430
> Content-Type: image/bmp
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/4.bmp
>
>|||I have the same problem.. And I talked with Microsoft Support Team..
Their answer is in the link below:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsmain/htm/rsc_architecture_v1_01df.asp
As a summary they say, use Excel 2002 or higher version !!!
I'm really disappointed with this..
Nothing to say more..
"Sanjeev" <sanjeev@.microsoft.com> wrote in message news:<eRin5rpuEHA.2016@.TK2MSFTNGP15.phx.gbl>...
> When exporting to pdf format, everything is fine.
> However, exporting to excel leads to some garbage.
> Can anyone tell me what is going on?
> Output similar to the following is displayed in the excel file
> MIME-Version: 1.0
> X-Document-Type: Workbook
> Content-Type: multipart/related;boundary="--=_NextPart_01C35DB7.4B204430"
> This is a multi-part message in MIME format.
> --=_NextPart_01C35DB7.4B204430
> Content-Type: text/html;
> charset="utf-8"
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/Report.htm
> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm
> --=_NextPart_01C35DB7.4B204430
> Content-Type: text/html
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/Sheet1.htm
> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbW
> 9sc3Bhbj0iMyIgc3R5bGU9ImJvcmRlci1yaWdodDow
> --=_NextPart_01C35DB7.4B204430
> Content-Type: image/bmp
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/4.bmp|||I am on SP1. Perhaps some setting is offset.
Thanks, Anyway.
"Shane Castle" <ShaneCastle@.discussions.microsoft.com> wrote in message
news:21C5DEAA-6CE5-41AF-865F-9FCD63B180C4@.microsoft.com...
> Are you using MRS with service pack #1? If not, and you are exporting to
> an
> older version of Excel you can see garbage. If you are on SP1, then I'm
> not
> sure what could be going on.
> "Sanjeev" wrote:
>> When exporting to pdf format, everything is fine.
>> However, exporting to excel leads to some garbage.
>> Can anyone tell me what is going on?
>> Output similar to the following is displayed in the excel file
>> MIME-Version: 1.0
>> X-Document-Type: Workbook
>> Content-Type:
>> multipart/related;boundary="--=_NextPart_01C35DB7.4B204430"
>> This is a multi-part message in MIME format.
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: text/html;
>> charset="utf-8"
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/Report.htm
>> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: text/html
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/Sheet1.htm
>> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbW
>> 9sc3Bhbj0iMyIgc3R5bGU9ImJvcmRlci1yaWdodDow
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: image/bmp
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/4.bmp
>>|||Thanks.
"Sema Yuce" <sema.yuce@.eczacibasi.com.tr> wrote in message
news:9844673f.0410252312.e19650a@.posting.google.com...
>I have the same problem.. And I talked with Microsoft Support Team..
> Their answer is in the link below:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsmain/htm/rsc_architecture_v1_01df.asp
> As a summary they say, use Excel 2002 or higher version !!!
> I'm really disappointed with this..
> Nothing to say more..
> "Sanjeev" <sanjeev@.microsoft.com> wrote in message
> news:<eRin5rpuEHA.2016@.TK2MSFTNGP15.phx.gbl>...
>> When exporting to pdf format, everything is fine.
>> However, exporting to excel leads to some garbage.
>> Can anyone tell me what is going on?
>> Output similar to the following is displayed in the excel file
>> MIME-Version: 1.0
>> X-Document-Type: Workbook
>> Content-Type:
>> multipart/related;boundary="--=_NextPart_01C35DB7.4B204430"
>> This is a multi-part message in MIME format.
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: text/html;
>> charset="utf-8"
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/Report.htm
>> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: text/html
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/Sheet1.htm
>> 77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbW
>> 9sc3Bhbj0iMyIgc3R5bGU9ImJvcmRlci1yaWdodDow
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: image/bmp
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/4.bmp

Sunday, February 19, 2012

Export to CSV fails with 3rd party web app

From my web application, exporting to Excel works fine, but when I export to CSV and open with Excel I get 2 garbage characters. I can export the report just fine from the ReportServer.

Is there something special that needs to be done? Could I have an old file?

Could it be something in my report? We always have the following components:
-- textboxes in the page header and footer
-- page header refers to parameter values; page footer refers to globals
-- 2 date parameters and 1 hidden boolean parameters

We're running SQL 2005 Reporting Services, and I have SP2 installed.

(I write the reports, not the web app)

?t

The export failed from SSRS, so the issue is not in the ReportViewer control.
It turns out a report parameter and a field in the dataset had the same name.
SELECT *, bad=@.bad FROM Employees

Changing the parameter name fixed it.
SELECT *, bad=@.notBadAtAll FROM Employees

Export to CSV fails with 3rd party web app

From my web application, exporting to Excel works fine, but when I export to CSV and open with Excel I get 2 garbage characters. I can export the report just fine from the ReportServer.

Is there something special that needs to be done? Could I have an old file?

Could it be something in my report? We always have the following components:
-- textboxes in the page header and footer
-- page header refers to parameter values; page footer refers to globals
-- 2 date parameters and 1 hidden boolean parameters

We're running SQL 2005 Reporting Services, and I have SP2 installed.

(I write the reports, not the web app)

?t

The export failed from SSRS, so the issue is not in the ReportViewer control.
It turns out a report parameter and a field in the dataset had the same name.
SELECT *, bad=@.bad FROM Employees

Changing the parameter name fixed it.
SELECT *, bad=@.notBadAtAll FROM Employees