Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Thursday, March 29, 2012

Exporting report to excel with subreports problem

Hello,

I got a error when exporting to excel one report that has a table and in a column it has a subreport.

Is this possible to do?

What is the work around?

The error that i got it is the following.


Server Error in '/Reports' Application.
--

For more information about this error navigate to the report server on the local server machine, or enable remote errors
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors]

[Exception: An error occurred during rendering of the report.]
Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension) +489
Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +959
Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& fileExtension) +84
Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +143
Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


--

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

Thank you


It is my understanding that the sub reports do NOT export to excel. I re-wrote many reports when I had to provide that functionality.

I realize this dosn't directly answer your question but rather than spend hours addressing the problem, you could re-do the report and get the result you want.

Tim

|||Well not what i wanted to hear, but thanks anyway

Tuesday, March 27, 2012

exporting error

attached is the error msg that display everytime i export the informations generated by CR v8.5 to excel file. i thought the reason for the error msg is the consumption of the 65T rows allowed in excel because when i export the report having much fewer informations (retrieve the same report in the short period of time), the exportation was successul.

On the other hand, when i tried the previous report version, any exportation was successful even when the retrieval arguments in date range is 3 months.

Please help mei have known the cause of this error, this is due to the subreport i inserted so i just editted the report and delete the sub report. on the other hand, can anyone help me why does the error occur? is it a bug of the CR 8.5? F.Y.I the CR report is directly retrieve in a server... H.E.L.Psql

Thursday, March 22, 2012

Exporting crystal reports in excel

Hi all

When i export crystal report file in excel it gives unknown error and the application get closed.
But the same report is getting exported in word and other applications

What is the reason?Can anybody help for this?
Plz also tell if their is any dll used for exporting rpt files.

Regards

AanchalI'm not sure about what exactly is the problem, may be while installing you skiped to select Excel related options. Try to install again in Complete mode and select whichever is related excel.

Good Luck,
Gragi|||Which version of Excel are you using?sql

Exporting Crystal Report To Excel

Hi,
I am having a problem while exporting Crystal Report to Excel Format. It is giving an error saying 'Missing Parameter Current Value' even after passing the parameters. Can any one help.
Thanks
MohithHi,

I try to export crystal report to excel format and its works fine.
but i don't know which version u used for crystal reports and excel

-Yags|||Try looking up the error message in Google or some other search engine.

Crystal Reports Online Tech Support:
http://support.businessobjects.com/search/advsearch.asp

Crystal Reports Forum:
http://support.businessobjects.com/forums/default.asp

Exporting CR from VB

am trying t export a report from CR ver 7.0 from VB 6.0
the report has 16000 rows, but its exporting only 8000+ records...
no error messages.
can anyone help me out.r u exporting to excel, if yes
try using

Report.Export

With Report.ExportOptions
.ExcelExportAllPages
End With

****where report is object of CRAXDRT.report

Dim Report As CRAXDRT.Report|||thanks sraheem for ur help.

yeah am trying to export to excel only.

i tried CRAXDRT

but i coud not find the option .ExcelExportAllPages with ExportOptions|||so sad to know that noone is there with a solution.

i thot its a simple problem and i didnt knew to solve it.

if anyone finds it out,...please let me know,sql

Monday, March 19, 2012

Export Wizard generates errors

I am trying to export data from my local server to the hosting server. However I get errors when executing it:

Validating (Error)

Messages

Error 0xc0202049: Data Flow Task: Failure inserting into the read-only column "ID".
(SQL Server Import and Export Wizard)

Error 0xc0202045: Data Flow Task: Column metadata validation failed.
(SQL Server Import and Export Wizard)

Error 0xc004706b: Data Flow Task: "component "Destination 7 - Batches" (497)" failed validation and returned validation status "VS_ISBROKEN".
(SQL Server Import and Export Wizard)

Error 0xc004700c: Data Flow Task: One or more component failed validation.
(SQL Server Import and Export Wizard)

Error 0xc0024107: Data Flow Task: There were errors during task validation.
(SQL Server Import and Export Wizard)

Any idea?

Did you try to insert values in the ID field and this is an identity? This will not work...|||I am just trying to copy all data from one server to another. It used to be simple task in SQl 2000. I am not sure how to do this now...|||...I'm qute sure that you have the same issue with 2000, too! You simply can't do an insert into an identity column (by default). However you might try to switch "Enable identity insert" in the "Mappings" screen on...|||

I used to be able to Run Wizard in 2000 and transfer all the data to the server. It si the same database.. I had an option to recreate destination tables first...

What is the simplest way to do it in new 2005? I can't figure it out. Basicly I want my development SQL Database have in synch with production hosting SQl Server... It is not some rocket science... I should be able to run some kind of wizard... The one I run does not allow me to slect drop destination tables, this option is greyd out... Also it is on table level, not for all tables.

If I design SSIS package I would have to modify it everytime I add new tables to the laptop DB, so the Wizard slution like in SQL 2000 seems much better.

Since the wizard in 2000 worked for me I am considering to downgrade to SQL 2000, it is a shame I have to do it, because 2005 suposed to be better product, yet it does not meet my expectations in this matter.

I wonder how other users find SQL 2005 comparing SQL 2000 in practical use, not just in theory.

|||

I'm very sorry, I can't understand your problem. From my point of view you can exactly do what you did with SQL 2000 with SQL 2005, too. Perhaps you have to explain it more detailed (step by step) what you did with 2000 and what you now do with 2005. I can drop and recreate tables without any problem. If you have identities, you had to (and still have to) click on "enable identity inserts"...

Or did you probably use the "copy database objects" wizzard? But I don't think so, that didn't fit to your description...

|||For some reason the option to recreate tables is greyed out in SQL 2005 wizard. I do not know why. Also this option is available on the table level. You have to click each table and change it. It used to be global setting for all tables in SQL 2000...|||

RADIOGENERIS wrote:

You have to click each table and change it. It used to be global setting for all tables in SQL 2000...

Surely the ability to define different behaviour for each one of them is a good thing?

|||

Sure, but having an easy way to change the default behaviour would be something great, too?!

Perhaps something to suggest "officially"?

|||

It was done this way in SQl 2000, why to remove this global option?

Also why is this option greyed out? Nobody can answer this question. What can be the reason?

Thanks,

|||

This option is designed to be used when the destination table is newly created. It would allow executing a saved package after the wizard creates the table, without modifications.

In your case (the table already exists) you would probably want to use the "Delete rows in destination table" option. We did not want to allow deleting tables that are not created by the wizard, since that may cause some unwished effects.

I agree that inability to set these options for more than one transfer at the time was a serious usability problem, and it has been addressed in SP1. The SP1 will allow bulk edits on all selected transfers and in addition to setting these options it would allow setting destination schemas to more than one destination table.

Thanks.

|||

Bob,

Thank you for your explanation. I am so happy you guys have noticed that. I am waiting fo SP1, would you know when this will become available?

My suggestion is that the option to recreate table should be always available, it was done this way in SQL 2000 and it worked. Let the user decide what they want. They do not have to check this option... You could give them some warning once they check it. I guess deleting rows in a destination table would work for me for now.

My point is that SQL Server 2000 data export/import wizard was a very good tool, I am sure many people would agree with me. Why to remove some of it's great functionality? It was simple and sufficient and if you need more you would design a package. It creted views, stored procedures for you, all in one step. It was perfect for me, as I need to synchronize my laptop with hosting environment on regular basis. I develop new stored procedures, tables etc. at the end of day I would just run a wizard... Now the process is very time consuming.

Hopefully SP1 will adress those issues. Seems like SQL 2005 is a very good product, yet it needs few tweaks. Not everybody is SSIS expert :)

Also have you tried to open this package generated by Wizard in Visual Studio? It takes forever. I have 1.86 Ghz laptop with 1GB memory...

I think you guys are so ahead in technology that you may forget about simple use cases sometimes :)

Rafal

|||

You have a good point Rafal. There's some very simple functionality in Enterprise Manager around scripting out objects that i am really missing.

If you want something to go into SP1 or the next version you should raise it at the Feedback Center: http://lab.msdn.microsoft.com/productfeedback/default.aspx

-Jamie

|||

Seems like I am not the first one who noticed those issues. I have found few suggestions submited already. Please take a look:

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=9eb6c773-2dbb-4a27-b9d8-225d6ed4385a

|||

I am not quite sure when SP1 will get out, my guess is sometime in the spring time.

You are welcome to post the feedback on the ways you wish the wizard to get improved. That will most certainly influence the work we choose to do on it. We do sometimes forget about simple use cases, but it is more often that we have to prioritize things we do to better utilize our resources. These priority lists are based on the feedback we hear from you guys. So again, do not hesitate to send it.

There is also one thing I wanted to point out about comparing DTS and SSIS import/export wizard. While they look similar, the used underlying components are a way different, and that had influence on some of the UI decisions we made.

Thanks.

Export Wizard Error

I am trying to use the Export Wizard to copy data from a SQL2k server
database to a SQL2005 database. My source and destination is SQL Native
Client and I am only interested in one table. Everything appears to be ready
when I start the process.
However, when validating I keep getting the following error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: etc,etc.
Talks about retrieving the COM class factory and CLSID and the "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
What else do I need to check?
Hi Roger
Have you saved this as a package? The exact text of your error is important.
I would guess there is possibly a datatype issue.
You could also try using oledb connection.
John
"Roger Denison" wrote:

> I am trying to use the Export Wizard to copy data from a SQL2k server
> database to a SQL2005 database. My source and destination is SQL Native
> Client and I am only interested in one table. Everything appears to be ready
> when I start the process.
> However, when validating I keep getting the following error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: etc,etc.
> Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> What else do I need to check?
|||John,
I tried using the OLEDB connection and still got the same error. Here is
the text of the error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: "Retrieving the COM class factory for component with
CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the following
error: 80040154.". Possible failure reasons: Problems with the query,
"ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.
It looks as if it is trying to execute a nameless query.
Any ideas?
tfyh
Roger.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Roger
> Have you saved this as a package? The exact text of your error is important.
> I would guess there is possibly a datatype issue.
> You could also try using oledb connection.
> John
> "Roger Denison" wrote:
|||Hi Roger
Error 80040154 is usally an issue with the COM component not being
installed, therefore you could try doing this on a different machine to prove
it is the local installation. You don't say which version you are running,
you may want to check if there is a service pack that could be installed if
you are not running on the latest.
John
"Roger Denison" wrote:
[vbcol=seagreen]
> John,
> I tried using the OLEDB connection and still got the same error. Here is
> the text of the error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: "Retrieving the COM class factory for component with
> CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the following
> error: 80040154.". Possible failure reasons: Problems with the query,
> "ResultSet" property not set correctly, parameters not set correctly, or
> connection not established correctly.
> It looks as if it is trying to execute a nameless query.
> Any ideas?
> tfyh
> Roger.
> "John Bell" wrote:
|||John,
I checked versions (9.0.1399) and everything seems to be in order. And
then, duh!, I noticed the SQL Server Agent on the destination wasn't running.
tfyh
Roger.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Roger
> Error 80040154 is usally an issue with the COM component not being
> installed, therefore you could try doing this on a different machine to prove
> it is the local installation. You don't say which version you are running,
> you may want to check if there is a service pack that could be installed if
> you are not running on the latest.
> John
> "Roger Denison" wrote:
|||Hi
9.0.1399 is RTM there is currently SP2 and psot SP2 hotfixes which you
should consider deploying.
SQLAgent should not affect the migration wizard unless you are running as a
package as a job.
John
"Roger Denison" wrote:
[vbcol=seagreen]
> John,
> I checked versions (9.0.1399) and everything seems to be in order. And
> then, duh!, I noticed the SQL Server Agent on the destination wasn't running.
> tfyh
> Roger.
> "John Bell" wrote:

Export Wizard Error

I am trying to use the Export Wizard to copy data from a SQL2k server
database to a SQL2005 database. My source and destination is SQL Native
Client and I am only interested in one table. Everything appears to be ready
when I start the process.
However, when validating I keep getting the following error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: etc,etc.
Talks about retrieving the COM class factory and CLSID and the "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
What else do I need to check?Hi Roger
Have you saved this as a package? The exact text of your error is important.
I would guess there is possibly a datatype issue.
You could also try using oledb connection.
John
"Roger Denison" wrote:
> I am trying to use the Export Wizard to copy data from a SQL2k server
> database to a SQL2005 database. My source and destination is SQL Native
> Client and I am only interested in one table. Everything appears to be ready
> when I start the process.
> However, when validating I keep getting the following error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: etc,etc.
> Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> What else do I need to check?|||John,
I tried using the OLEDB connection and still got the same error. Here is
the text of the error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: "Retrieving the COM class factory for component with
CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the following
error: 80040154.". Possible failure reasons: Problems with the query,
"ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.
It looks as if it is trying to execute a nameless query.
Any ideas?
tfyh
Roger.
"John Bell" wrote:
> Hi Roger
> Have you saved this as a package? The exact text of your error is important.
> I would guess there is possibly a datatype issue.
> You could also try using oledb connection.
> John
> "Roger Denison" wrote:
> > I am trying to use the Export Wizard to copy data from a SQL2k server
> > database to a SQL2005 database. My source and destination is SQL Native
> > Client and I am only interested in one table. Everything appears to be ready
> > when I start the process.
> >
> > However, when validating I keep getting the following error:
> > Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> > the following error: etc,etc.
> > Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> > property not set correctly, parameters not set correctly, or connection not
> > established correctly.
> >
> > What else do I need to check?|||Hi Roger
Error 80040154 is usally an issue with the COM component not being
installed, therefore you could try doing this on a different machine to prove
it is the local installation. You don't say which version you are running,
you may want to check if there is a service pack that could be installed if
you are not running on the latest.
John
"Roger Denison" wrote:
> John,
> I tried using the OLEDB connection and still got the same error. Here is
> the text of the error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: "Retrieving the COM class factory for component with
> CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the following
> error: 80040154.". Possible failure reasons: Problems with the query,
> "ResultSet" property not set correctly, parameters not set correctly, or
> connection not established correctly.
> It looks as if it is trying to execute a nameless query.
> Any ideas?
> tfyh
> Roger.
> "John Bell" wrote:
> > Hi Roger
> >
> > Have you saved this as a package? The exact text of your error is important.
> > I would guess there is possibly a datatype issue.
> >
> > You could also try using oledb connection.
> >
> > John
> >
> > "Roger Denison" wrote:
> >
> > > I am trying to use the Export Wizard to copy data from a SQL2k server
> > > database to a SQL2005 database. My source and destination is SQL Native
> > > Client and I am only interested in one table. Everything appears to be ready
> > > when I start the process.
> > >
> > > However, when validating I keep getting the following error:
> > > Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> > > the following error: etc,etc.
> > > Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> > > property not set correctly, parameters not set correctly, or connection not
> > > established correctly.
> > >
> > > What else do I need to check?|||John,
I checked versions (9.0.1399) and everything seems to be in order. And
then, duh!, I noticed the SQL Server Agent on the destination wasn't running.
tfyh
Roger.
"John Bell" wrote:
> Hi Roger
> Error 80040154 is usally an issue with the COM component not being
> installed, therefore you could try doing this on a different machine to prove
> it is the local installation. You don't say which version you are running,
> you may want to check if there is a service pack that could be installed if
> you are not running on the latest.
> John
> "Roger Denison" wrote:
> > John,
> >
> > I tried using the OLEDB connection and still got the same error. Here is
> > the text of the error:
> > Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> > the following error: "Retrieving the COM class factory for component with
> > CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the following
> > error: 80040154.". Possible failure reasons: Problems with the query,
> > "ResultSet" property not set correctly, parameters not set correctly, or
> > connection not established correctly.
> >
> > It looks as if it is trying to execute a nameless query.
> >
> > Any ideas?
> >
> > tfyh
> > Roger.
> >
> > "John Bell" wrote:
> >
> > > Hi Roger
> > >
> > > Have you saved this as a package? The exact text of your error is important.
> > > I would guess there is possibly a datatype issue.
> > >
> > > You could also try using oledb connection.
> > >
> > > John
> > >
> > > "Roger Denison" wrote:
> > >
> > > > I am trying to use the Export Wizard to copy data from a SQL2k server
> > > > database to a SQL2005 database. My source and destination is SQL Native
> > > > Client and I am only interested in one table. Everything appears to be ready
> > > > when I start the process.
> > > >
> > > > However, when validating I keep getting the following error:
> > > > Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> > > > the following error: etc,etc.
> > > > Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> > > > property not set correctly, parameters not set correctly, or connection not
> > > > established correctly.
> > > >
> > > > What else do I need to check?|||Hi
9.0.1399 is RTM there is currently SP2 and psot SP2 hotfixes which you
should consider deploying.
SQLAgent should not affect the migration wizard unless you are running as a
package as a job.
John
"Roger Denison" wrote:
> John,
> I checked versions (9.0.1399) and everything seems to be in order. And
> then, duh!, I noticed the SQL Server Agent on the destination wasn't running.
> tfyh
> Roger.
> "John Bell" wrote:
> > Hi Roger
> >
> > Error 80040154 is usally an issue with the COM component not being
> > installed, therefore you could try doing this on a different machine to prove
> > it is the local installation. You don't say which version you are running,
> > you may want to check if there is a service pack that could be installed if
> > you are not running on the latest.
> >
> > John
> >
> > "Roger Denison" wrote:
> >
> > > John,
> > >
> > > I tried using the OLEDB connection and still got the same error. Here is
> > > the text of the error:
> > > Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> > > the following error: "Retrieving the COM class factory for component with
> > > CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the following
> > > error: 80040154.". Possible failure reasons: Problems with the query,
> > > "ResultSet" property not set correctly, parameters not set correctly, or
> > > connection not established correctly.
> > >
> > > It looks as if it is trying to execute a nameless query.
> > >
> > > Any ideas?
> > >
> > > tfyh
> > > Roger.
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Roger
> > > >
> > > > Have you saved this as a package? The exact text of your error is important.
> > > > I would guess there is possibly a datatype issue.
> > > >
> > > > You could also try using oledb connection.
> > > >
> > > > John
> > > >
> > > > "Roger Denison" wrote:
> > > >
> > > > > I am trying to use the Export Wizard to copy data from a SQL2k server
> > > > > database to a SQL2005 database. My source and destination is SQL Native
> > > > > Client and I am only interested in one table. Everything appears to be ready
> > > > > when I start the process.
> > > > >
> > > > > However, when validating I keep getting the following error:
> > > > > Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> > > > > the following error: etc,etc.
> > > > > Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> > > > > property not set correctly, parameters not set correctly, or connection not
> > > > > established correctly.
> > > > >
> > > > > What else do I need to check?

Export Wizard Error

I am trying to use the Export Wizard to copy data from a SQL2k server
database to a SQL2005 database. My source and destination is SQL Native
Client and I am only interested in one table. Everything appears to be read
y
when I start the process.
However, when validating I keep getting the following error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: etc,etc.
Talks about retrieving the COM class factory and CLSID and the "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
What else do I need to check?Hi Roger
Have you saved this as a package? The exact text of your error is important.
I would guess there is possibly a datatype issue.
You could also try using oledb connection.
John
"Roger Denison" wrote:

> I am trying to use the Export Wizard to copy data from a SQL2k server
> database to a SQL2005 database. My source and destination is SQL Native
> Client and I am only interested in one table. Everything appears to be re
ady
> when I start the process.
> However, when validating I keep getting the following error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: etc,etc.
> Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> What else do I need to check?|||John,
I tried using the OLEDB connection and still got the same error. Here is
the text of the error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: "Retrieving the COM class factory for component with
CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the followin
g
error: 80040154.". Possible failure reasons: Problems with the query,
"ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.
It looks as if it is trying to execute a nameless query.
Any ideas?
tfyh
Roger.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Roger
> Have you saved this as a package? The exact text of your error is importan
t.
> I would guess there is possibly a datatype issue.
> You could also try using oledb connection.
> John
> "Roger Denison" wrote:
>|||Hi Roger
Error 80040154 is usally an issue with the COM component not being
installed, therefore you could try doing this on a different machine to prov
e
it is the local installation. You don't say which version you are running,
you may want to check if there is a service pack that could be installed if
you are not running on the latest.
John
"Roger Denison" wrote:
[vbcol=seagreen]
> John,
> I tried using the OLEDB connection and still got the same error. Here is
> the text of the error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: "Retrieving the COM class factory for component with
> CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the follow
ing
> error: 80040154.". Possible failure reasons: Problems with the query,
> "ResultSet" property not set correctly, parameters not set correctly, or
> connection not established correctly.
> It looks as if it is trying to execute a nameless query.
> Any ideas?
> tfyh
> Roger.
> "John Bell" wrote:
>|||John,
I checked versions (9.0.1399) and everything seems to be in order. And
then, duh!, I noticed the SQL Server Agent on the destination wasn't running
.
tfyh
Roger.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Roger
> Error 80040154 is usally an issue with the COM component not being
> installed, therefore you could try doing this on a different machine to pr
ove
> it is the local installation. You don't say which version you are running,
> you may want to check if there is a service pack that could be installed i
f
> you are not running on the latest.
> John
> "Roger Denison" wrote:
>|||Hi
9.0.1399 is RTM there is currently SP2 and psot SP2 hotfixes which you
should consider deploying.
SQLAgent should not affect the migration wizard unless you are running as a
package as a job.
John
"Roger Denison" wrote:
[vbcol=seagreen]
> John,
> I checked versions (9.0.1399) and everything seems to be in order. And
> then, duh!, I noticed the SQL Server Agent on the destination wasn't runni
ng.
> tfyh
> Roger.
> "John Bell" wrote:
>

Export with DTS to a dbf file

Hello,

I'm trying to export data from sql server2000 to a dbf file
When creating the dts package, i've got the following error (when creating the table in the dbf file):
"HResult of 2147467259 returned. Unexpected error occurred..."

The table i try to export is like:
Table1 (field1 int, field2 int...)

Does anyone have any idea?

Thanks in advance

IsabelleDo not forget that length of name field for DBF is only 10 ...
Check name of columns in your table.

Friday, March 9, 2012

Export to PDF Error: Index was out of range

When I view the report in HTML it works fine. It gives the following error when exported to PDF:

Index was out of range. Must be non negative and less than the size of the collection. Parameter name: Index.

Please help!

Hello,

Could you please provide some more info:

RS version

RDL file

Thanks!

Export to PDF error with SP1 still (encoding related)

Export to PDF error with SP1 still (encoding related)
my reports have some Chinese msg.
When review or display, everything seemed ok. But when I export it to PDF, Chinese msg showed as "'"
I've tried to export my report into other format with no error.
Before SP1, it's a problem. Now, with SP1, its still. :(
my SQL Server is SQL Server 2000 En + SP4If you want to show PDF reports in Traditional Chinese, try to set FontFamily to "æ?°ç´°æ'é«?" or other localized FontFamilies.
"wps8848" wrote:
> Export to PDF error with SP1 still (encoding related)
>
> my reports have some Chinese msg.
> When review or display, everything seemed ok. But when I export it to PDF, Chinese msg showed as "'"
> I've tried to export my report into other format with no error.
> Before SP1, it's a problem. Now, with SP1, its still. :(
> my SQL Server is SQL Server 2000 En + SP4
>|||thanks to SAM.
The problem is resolved. :)
What a pitty it is? Sign !
"sam" wrote:
> If you want to show PDF reports in Traditional Chinese, try to set FontFamily to "æ?°ç´°æ'é«?" or other localized FontFamilies.
>
> "wps8848" wrote:
> > Export to PDF error with SP1 still (encoding related)
> >
> >
> > my reports have some Chinese msg.
> > When review or display, everything seemed ok. But when I export it to PDF, Chinese msg showed as "'"
> >
> > I've tried to export my report into other format with no error.
> >
> > Before SP1, it's a problem. Now, with SP1, its still. :(
> >
> > my SQL Server is SQL Server 2000 En + SP4
> >
> >

Export to PDF error

Some users get the following error when exporting to PDF:
There was an error opening this document. The file does not exist.
They can save the document locally though and open it. We're all using the
same version of Acrobat Reader (6.0.1).
Has anyone experienced this before?
Thanks,
Jason MacKenzieJason, I have aboslutely experienced this same issue and it is a major
problem. Can someone from Microsoft please comment on this issue. We have
various version of .pdf in the office. 5.0 works fine it seems for Reporting
Services rendering to .pdf but we have a requirement for employees to see
their ADP paystubs in 6.0. Adober .pdf's load fine in the browser when
pulled up directly from other sources which leads me to believe this is a
driver issue on the reporting services side?
"Jason MacKenzie" wrote:
> Some users get the following error when exporting to PDF:
> There was an error opening this document. The file does not exist.
> They can save the document locally though and open it. We're all using the
> same version of Acrobat Reader (6.0.1).
> Has anyone experienced this before?
> Thanks,
> Jason MacKenzie
>
>|||Here's an additional caveat. This seems to be happening primarily on systems
with Adobe Acrobt 6.0 Professional installed?
"Scott" wrote:
> Jason, I have aboslutely experienced this same issue and it is a major
> problem. Can someone from Microsoft please comment on this issue. We have
> various version of .pdf in the office. 5.0 works fine it seems for Reporting
> Services rendering to .pdf but we have a requirement for employees to see
> their ADP paystubs in 6.0. Adober .pdf's load fine in the browser when
> pulled up directly from other sources which leads me to believe this is a
> driver issue on the reporting services side?
> "Jason MacKenzie" wrote:
> > Some users get the following error when exporting to PDF:
> >
> > There was an error opening this document. The file does not exist.
> >
> > They can save the document locally though and open it. We're all using the
> > same version of Acrobat Reader (6.0.1).
> >
> > Has anyone experienced this before?
> >
> > Thanks,
> >
> > Jason MacKenzie
> >
> >
> >

Wednesday, March 7, 2012

Export To Excel throws Error WrapperReportRenderingException

I have a report contains few tables.
The report runs without any problem (Url access) and export to other format
also without any problem.
Only when I export the same report to Excel, the following error occurs in
the reportserver log and its throws an error on screen.
This error only happens if I run the report with certain parameters. If I
select difference parameters, the report can export to excel successfully.
I have found out it is down to a table group - the group on expression, it
is using one of the dataset field which is a bigInt.
If I pick another field within the same dataset in the 'group on' expression
with the smae parameters, its works.
This bigInt field can be any value greater than 0 (usually a 9 characters
number) and could be a special defined value -1.
I hope there is enough information for anyone out there to help me....
Thanks
------
w3wp!reportrendering!e!11/29/2007-10:47:19:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
An error occurred during rendering of the report., ;
Info:
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
An error occurred during rendering of the report. -->
Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An
error occurred during rendering of the report. -->
System.InvalidOperationException: Operation is not valid due to the current
state of the object.
at
Microsoft.ReportingServices.ReportRendering.TableGroupCollection.get_Item(Int32
index)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReferenceInTable(TableHeaderFooterRows
header, TableHeaderFooterRows footer, TableGroupCollection tableGroups,
TableRowsCollection detailRows, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem
dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem
dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem
dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.CollectHiddenReportItems(IntList
indexPath, PageReportItems& pageRI)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreScanPage(ReportItem
parentDataRegion, Boolean isPageNeedsEvaluation, PageLayout& pageLayout,
PageReportItems& pageRIItems, Stack& dynamicLayoutStack, Hashtable&
rowHeightStateList, OutlineRenderStates[]& verticalOutlineStates,
OutlineRenderStates[]& horizontalOutlineStates)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderStaticPage(ReportItem
parentDataRegion, PageLayout pageLayout, Hashtable formulaRIMap, Int32
currentPageNumber, PageReportItems& pageRIItems, Stack& dynamicLayoutStack)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageLayout(PageLayout
pageLayout, Int32& currentPageNumber, Stack& stack)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageCollection(PageCollection
pageCollection, Int32& currentPageNumber, Stack& stack, PageLayout&
lastPageLayout)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderOrCountDynamicPage(Stack&
renderDynamicStack, Int32& currentPageNumber, Int32 stackTop, PageLayout&
lastPageLayout, Action action)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageCollection(PageCollection
pageCollection, Int32& currentPageNumber, Stack& stack, PageLayout&
lastPageLayout)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateWorkSheets()
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateMainSheet()
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderExcelWorkBook(CreateAndRegisterStream
createAndRegisterStream)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.ProcessReport(CreateAndRegisterStream
createAndRegisterStream)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapshot(IRenderingExtension
renderer, CreateReportChunk createChunkCallback, RenderingContext rc,
GetResource getResourceCallback)
-- End of inner exception stack trace --
w3wp!library!e!11/29/2007-10:47:19:: Unhandled exception was caught:
Microsoft.Reporting.WebForms.ReportServerException: An error occurred during
rendering of the report. (rrRenderingError) -->
Microsoft.Reporting.WebForms.ReportServerException: For more information
about this error navigate to the report server on the local server machine,
or enable remote errors
-- End of inner exception stack trace --
at Microsoft.Reporting.WebForms.ServerReport.InternalRender(String
format, String deviceInfo, String& extension, String& mimeType, String&
encoding, String[]& streams, Warning[]& warnings)
at Microsoft.Reporting.WebForms.ServerReport.Render(String format, String
deviceInfo, NameValueCollection additionalParams, String& mimeType, String&
extension)
at
Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String
format, String deviceInfo, NameValueCollection additionalParams, String&
mimeType, String& fileExtension)
at
Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection
urlQuery, HttpResponse response)
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
context)
at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
w3wp!library!c!11/29/2007-10:47:22:: i INFO: Call to RenderFirst(
'ProblemReports' )
------When you say another field works, do you mean with the same data type?
Try running your query in SQL management studio with the results
outputting to an excel file . What version of excel are you using ?
Cheers
Shai
On Dec 6, 12:56 am, <chrisexen...@.newsgroups.nospam> wrote:
> I have a report contains few tables.
> The report runs without any problem (Url access) and export to other format
> also without any problem.
> Only when I export the same report to Excel, the following error occurs in
> the reportserver log and its throws an error on screen.
> This error only happens if I run the report with certain parameters. If I
> select difference parameters, the report can export to excel successfully.
> I have found out it is down to a table group - the group on expression, it
> is using one of the dataset field which is a bigInt.
> If I pick another field within the same dataset in the 'group on' expression
> with the smae parameters, its works.
> This bigInt field can be any value greater than 0 (usually a 9 characters
> number) and could be a special defined value -1.
> I hope there is enough information for anyone out there to help me....
> Thanks
> ------
> w3wp!reportrendering!e!11/29/2007-10:47:19:: e ERROR: Throwing
> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingExceptio-n:
> An error occurred during rendering of the report., ;
> Info:
> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingExceptio-n:
> An error occurred during rendering of the report. -->
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An
> error occurred during rendering of the report. -->
> System.InvalidOperationException: Operation is not valid due to the current
> state of the object.
> at
> Microsoft.ReportingServices.ReportRendering.TableGroupCollection.get_Item(I-nt32
> index)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetRefere-nceInTable(TableHeaderFooterRows
> header, TableHeaderFooterRows footer, TableGroupCollection tableGroups,
> TableRowsCollection detailRows, IntList indexPath, Int32 startIndex)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetRefere-nce(ReportItem
> dataRegion, IntList indexPath, Int32 startIndex)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetRefere-nce(ReportItem
> dataRegion, IntList indexPath, Int32 startIndex)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetRefere-nce(ReportItem
> dataRegion, IntList indexPath, Int32 startIndex)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.CollectHi-ddenReportItems(IntList
> indexPath, PageReportItems& pageRI)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreScanPa-ge(ReportItem
> parentDataRegion, Boolean isPageNeedsEvaluation, PageLayout& pageLayout,
> PageReportItems& pageRIItems, Stack& dynamicLayoutStack, Hashtable&
> rowHeightStateList, OutlineRenderStates[]& verticalOutlineStates,
> OutlineRenderStates[]& horizontalOutlineStates)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderSta-ticPage(ReportItem
> parentDataRegion, PageLayout pageLayout, Hashtable formulaRIMap, Int32
> currentPageNumber, PageReportItems& pageRIItems, Stack& dynamicLayoutStack)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPag-eLayout(PageLayout
> pageLayout, Int32& currentPageNumber, Stack& stack)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPag-eCollection(PageCollection
> pageCollection, Int32& currentPageNumber, Stack& stack, PageLayout&
> lastPageLayout)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderOrC-ountDynamicPage(Stack&
> renderDynamicStack, Int32& currentPageNumber, Int32 stackTop, PageLayout&
> lastPageLayout, Action action)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPag-eCollection(PageCollection
> pageCollection, Int32& currentPageNumber, Stack& stack, PageLayout&
> lastPageLayout)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateW-orkSheets()
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateM-ainSheet()
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderExc-elWorkBook(CreateAndRegisterStream
> createAndRegisterStream)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.ProcessRe-port(CreateAndRegisterStream
> createAndRegisterStream)
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Re-port
> report, NameValueCollection reportServerParameters, NameValueCollection
> deviceInfo, NameValueCollection clientCapabilities,
> EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
> CreateAndRegisterStream createAndRegisterStream)
> -- End of inner exception stack trace --
> at
> Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Re-port
> report, NameValueCollection reportServerParameters, NameValueCollection
> deviceInfo, NameValueCollection clientCapabilities,
> EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
> CreateAndRegisterStream createAndRegisterStream)
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapsho-t(IRenderingExtension
> renderer, CreateReportChunk createChunkCallback, RenderingContext rc,
> GetResource getResourceCallback)
> -- End of inner exception stack trace --
> w3wp!library!e!11/29/2007-10:47:19:: Unhandled exception was caught:
> Microsoft.Reporting.WebForms.ReportServerException: An error occurred during
> rendering of the report. (rrRenderingError) -->
> Microsoft.Reporting.WebForms.ReportServerException: For more information
> about this error navigate to the report server on the local server machine,
> or enable remote errors
> -- End of inner exception stack trace --
> at Microsoft.Reporting.WebForms.ServerReport.InternalRender(String
> format, String deviceInfo, String& extension, String& mimeType, String&
> encoding, String[]& streams, Warning[]& warnings)
> at Microsoft.Reporting.WebForms.ServerReport.Render(String format, String
> deviceInfo, NameValueCollection additionalParams, String& mimeType, String&
> extension)
> at
> Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String
> format, String deviceInfo, NameValueCollection additionalParams, String&
> mimeType, String& fileExtension)
> at
> Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueColl-ection
> urlQuery, HttpResponse response)
> at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
> context)
> at
> System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplicat-ion.IExecutionStep.Execute()
> at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously)
> w3wp!library!c!11/29/2007-10:47:22:: i INFO: Call to RenderFirst(
> 'ProblemReports' )
> ------|||Hello Chris,
I would like to know whether you have applied the latest service pack of
SQL Server.
Please apply the service pack and let me know whether this issue resolved.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei and Shai
Thanks you for the replies.....
We do already have the latest service pack on.
Because the reporting services and SQL server are installed on two
serperated servers, I have checked both file versions.
The SQL Server version is :
Product Version is 9.00.3054.00
Product Level is SP2
Edition is Standard Edition (64-bit)
slqservr.exe (64-bit) File version is 2005.90.3054.0 - from HotFixbuild 3159
ReportingServicesService.exe (32-bit) File version is 9.0.3054.0
To answer Shai questions,
Unfotunately the dataset returned by the stored procedure do not have two
column with the same data type (BigInt) that I used for the table grouping.
I only tried another column with data type Int that returned the similar
data.
We have tried to run and export the report on two client machines, one has
Excel 2003 and one has Excel 2007.
And I am trying to figuring it out how to output the results from SQL
management studio to an excel file. :)
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:xPpOT%238NIHA.5204@.TK2MSFTNGHUB02.phx.gbl...
> Hello Chris,
> I would like to know whether you have applied the latest service pack of
> SQL Server.
> Please apply the service pack and let me know whether this issue resolved.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||<chrisexentra@.newsgroups.nospam> wrote in message
news:JaidnVK4m4PXn8XanZ2dnUVZ8tignZ2d@.pipex.net...
> Hi Wei and Shai
> Thanks you for the replies.....
> We do already have the latest service pack on.
> Because the reporting services and SQL server are installed on two
> serperated servers, I have checked both file versions.
> The SQL Server version is :
> Product Version is 9.00.3054.00
> Product Level is SP2
> Edition is Standard Edition (64-bit)
> slqservr.exe (64-bit) File version is 2005.90.3054.0 - from HotFixbuild
> 3159
> ReportingServicesService.exe (32-bit) File version is 9.0.3054.0
>
> To answer Shai questions,
> Unfotunately the dataset returned by the stored procedure do not have two
> column with the same data type (BigInt) that I used for the table
> grouping.
> I only tried another column with data type Int that returned the similar
> data.
> We have tried to run and export the report on two client machines, one has
> Excel 2003 and one has Excel 2007.
> And I am trying to figuring it out how to output the results from SQL
> management studio to an excel file. :)
>
>
> "Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
> news:xPpOT%238NIHA.5204@.TK2MSFTNGHUB02.phx.gbl...
>> Hello Chris,
>> I would like to know whether you have applied the latest service pack of
>> SQL Server.
>> Please apply the service pack and let me know whether this issue
>> resolved.
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> ==================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>|||Hi,
To export your query results in excel, in management studio, check
this option under query-> results to -> results to file. Then run your
query and itll ask you for a location , specify it as an excel file
and it will create a file if the file does not exist. Run your query ,
also run a dummy query by declaring a bigint variable and doing a
select . If you have updated service packs, then it has to be RS,
SQL , Excel or some rogue data. Try elimination to determine the cause
and then maybe we can look at why the crash happens.
Cheers
Shai
On Dec 6, 11:07 pm, <chrisexen...@.newsgroups.nospam> wrote:
> Hi Wei and Shai
> Thanks you for the replies.....
> We do already have the latest service pack on.
> Because the reporting services and SQL server are installed on two
> serperated servers, I have checked both file versions.
> The SQL Server version is :
> Product Version is 9.00.3054.00
> Product Level is SP2
> Edition is Standard Edition (64-bit)
> slqservr.exe (64-bit) File version is 2005.90.3054.0 - from HotFixbuild 3159
> ReportingServicesService.exe (32-bit) File version is 9.0.3054.0
> To answer Shai questions,
> Unfotunately the dataset returned by the stored procedure do not have two
> column with the same data type (BigInt) that I used for the table grouping.
> I only tried another column with data type Int that returned the similar
> data.
> We have tried to run and export the report on two client machines, one has
> Excel 2003 and one has Excel 2007.
> And I am trying to figuring it out how to output the results from SQL
> management studio to an excel file. :)
> "Wei Lu [MSFT]" <we...@.online.microsoft.com> wrote in messagenews:xPpOT%238NIHA.5204@.TK2MSFTNGHUB02.phx.gbl...
>
> > Hello Chris,
> > I would like to know whether you have applied the latest service pack of
> > SQL Server.
> > Please apply the service pack and let me know whether this issue resolved.
> > Sincerely,
> > Wei Lu
> > Microsoft Online Community Support
> > ==================================================> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > ==================================================> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.- Hide quoted text -
> - Show quoted text -|||Hi Shai,
I have set the results to file in the management studio. But when I execute
the stored procedure,
the save resoults dialog does not have Excel file type for me to select in
the 'save as type'.
It only has 'Report files (*.rpt)' type!
And I think we have all the latest service pack installed for SQL server and
RS.
We have a server running 64-bit sql server 2005, another server running
32-bit 2005 reporting services along with out web application.
On the RS server machine, we do not have Excel installed, or do we needed
to?
I run and export the report on my machine which has Excel 2007 installed.
I am currently run out of options Please, please help !
<shaikat.das@.gmail.com> wrote in message
news:b3eaf170-0e92-4224-b34b-363d92811c7b@.d21g2000prf.googlegroups.com...
> Hi,
> To export your query results in excel, in management studio, check
> this option under query-> results to -> results to file. Then run your
> query and itll ask you for a location , specify it as an excel file
> and it will create a file if the file does not exist. Run your query ,
> also run a dummy query by declaring a bigint variable and doing a
> select . If you have updated service packs, then it has to be RS,
> SQL , Excel or some rogue data. Try elimination to determine the cause
> and then maybe we can look at why the crash happens.
>
> Cheers
> Shai
> On Dec 6, 11:07 pm, <chrisexen...@.newsgroups.nospam> wrote:
>> Hi Wei and Shai
>> Thanks you for the replies.....
>> We do already have the latest service pack on.
>> Because the reporting services and SQL server are installed on two
>> serperated servers, I have checked both file versions.
>> The SQL Server version is :
>> Product Version is 9.00.3054.00
>> Product Level is SP2
>> Edition is Standard Edition (64-bit)
>> slqservr.exe (64-bit) File version is 2005.90.3054.0 - from HotFixbuild
>> 3159
>> ReportingServicesService.exe (32-bit) File version is 9.0.3054.0
>> To answer Shai questions,
>> Unfotunately the dataset returned by the stored procedure do not have two
>> column with the same data type (BigInt) that I used for the table
>> grouping.
>> I only tried another column with data type Int that returned the similar
>> data.
>> We have tried to run and export the report on two client machines, one
>> has
>> Excel 2003 and one has Excel 2007.
>> And I am trying to figuring it out how to output the results from SQL
>> management studio to an excel file. :)
>> "Wei Lu [MSFT]" <we...@.online.microsoft.com> wrote in
>> messagenews:xPpOT%238NIHA.5204@.TK2MSFTNGHUB02.phx.gbl...
>>
>> > Hello Chris,
>> > I would like to know whether you have applied the latest service pack
>> > of
>> > SQL Server.
>> > Please apply the service pack and let me know whether this issue
>> > resolved.
>> > Sincerely,
>> > Wei Lu
>> > Microsoft Online Community Support
>> > ==================================================>> > When responding to posts, please "Reply to Group" via your newsreader
>> > so
>> > that others may learn and benefit from your issue.
>> > ==================================================>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.- Hide quoted text -
>> - Show quoted text -
>|||Hello,
Have you tried to export the result to csv and open it in Excel?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
I have tried to export to csv and open it in Excel without any problem.
From what I found so far, it may be something to do with the grouping on the
table.
Please find three dataset csv files named :
FailedDataSet1.csv - with Paul1 and Brent1 and Malcolm1 data
FailedDataSet2.csv - with Paul1 and Brent1 data
SuccessDataSet.csv - with Brent1 and Malcolm1 data
These datasets contain three people's working data.
The rdl report has a list with 'details group' of the YEAR, WEEK_NO, ENUM
and NAME fields which gives the dataset saved above.
These ensure each report page has only one person per week of each year.
Within the list, there is a table. This table display all the data from the
dataset.
This table is group on the WorkingPeriodID field. (group on the WorkingDate
will not be correct)
Take the SuccessDataSet file as an example, the table will be something
likes:
(Page 1)
Working Date Name WorkingPeriodID
CNum ENum
19 / 11 Brent1 121897285
13150434 100992
20 / 11 Brent1 121897286
13035532 100992
21 / 11 Brent1 121897287
13035533 100992
Brent1 121897288
13150433 100992
<-- The table group should apply here which group on the WorkingPeriodId
field, and gives a total of the CNum -->
22 / 11 Brent1 121897289
13035534 100992
23 / 11 Brent1 121897290
13035535 100992
24 / 11 Brent1 121897291
1 100992
25 / 11 Brent1 121897292
1 100992
(Page 2)
Working Date Name WorkingPeriodID
CNum ENum
19 / 11 Malcolm1 121498129
13150283 100993
20 / 11 Malcolm1 121498130
13150282 100993
21 / 11 Malcolm1 121498131
13150281 100993
22 / 11 Malcolm1 121498132
13150280 100993
23 / 11 Malcolm1 121498133
13150279 100993
24 / 11 Malcolm1 121498134
1 100993
25 / 11 Malcolm1 121498135
1 100993
In normal situration, the workingPeriodId should be the same on each
workingdate.
This will gives a table row with of the total of the CNum field.
But in the above dataset, on 21 / 11, Brent1 have two rows with the
difference WorkingPeriodID.
Therefore the table group does not shows the total of the CNum row. (which
is corrected.)
Everything is fine with all three datasets, report can be rendered correctly
with RS and export to pdf correctly.
But if I try to export the FailedSataSet1 and DailedDataSet2 data to Excel,
Its gives the reporting Services error.
Only the data from the SuccessDataSet can be export to Excel successfully.
If I changed the WorkingPeriodId in the dataset to be the same on the 21 /
11 for Brent1. Everything works...
I hope these information will help and Thank you for taking time to help.
(if possible)
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:BPFLmUvOIHA.360@.TK2MSFTNGHUB02.phx.gbl...
> Hello,
> Have you tried to export the result to csv and open it in Excel?
>
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
begin 666 SuccessDataSet.csv
M5P!%`$4`2P!?`$X`3P`L`%D`10!!`%(`+ !7`$\`4@.!+`$D`3@.!'`% `10!2
M`$D`3P!$`$D`1 `L`%<`3P!2`$L`20!.`$<`1 !!`%0`10`L`$,`3@.!5`$T`
M+ !%`$X`50!-`"P`3@.!!`$T`10`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q
M`#@.`.0`W`#(`. `U`"P`,@.`P`# `-P`M`#$`,0`M`#$`.0`@.`# `, `Z`# `
M, `Z`# `, `N`# `, `P`"P`,0`S`#$`-0`P`#0`,P`T`"P`,0`P`# `.0`Y
M`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`
M.0`W`#(`. `V`"P`,@.`P`# `-P`M`#$`,0`M`#(`, `@.`# `, `Z`# `, `Z
M`# `, `N`# `, `P`"P`,0`S`# `,P`U`#4`,P`R`"P`,0`P`# `.0`Y`#(`
M+ !"`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W
M`#(`. `W`"P`,@.`P`# `-P`M`#$`,0`M`#(`,0`@.`# `, `Z`# `, `Z`# `
M, `N`# `, `P`"P`,0`S`# `,P`U`#4`,P`S`"P`,0`P`# `.0`Y`#(`+ !"
M`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`
M. `X`"P`,@.`P`# `-P`M`#$`,0`M`#(`,0`@.`# `, `Z`# `, `Z`# `, `N
M`# `, `P`"P`,0`S`#$`-0`P`#0`,P`S`"P`,0`P`# `.0`Y`#(`+ !"`'(`
M90!N`'0`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `Y
M`"P`,@.`P`# `-P`M`#$`,0`M`#(`,@.`@.`# `, `Z`# `, `Z`# `, `N`# `
M, `P`"P`,0`S`# `,P`U`#4`,P`T`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N
M`'0`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`.0`P`"P`
M,@.`P`# `-P`M`#$`,0`M`#(`,P`@.`# `, `Z`# `, `Z`# `, `N`# `, `P
M`"P`,0`S`# `,P`U`#4`,P`U`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`
M,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`.0`Q`"P`,@.`P
M`# `-P`M`#$`,0`M`#(`- `@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`
M,0`L`#$`, `P`#D`.0`R`"P`0@.!R`&4`;@.!T`#$`#0`*`#0`-P`L`#(`, `P
M`#<`+ `Q`#(`,0`X`#D`-P`R`#D`,@.`L`#(`, `P`#<`+0`Q`#$`+0`R`#4`
M( `P`# `.@.`P`# `.@.`P`# `+@.`P`# `, `L`#$`+ `Q`# `, `Y`#D`,@.`L
M`$(`<@.!E`&X`= `Q``T`"@.`T`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`
M,0`R`#D`+ `R`# `, `W`"T`,0`Q`"T`,0`Y`" `, `P`#H`, `P`#H`, `P
M`"X`, `P`# `+ `Q`#,`,0`U`# `,@.`X`#,`+ `Q`# `, `Y`#D`,P`L`$T`
M80!L`&,`;P!L`&T`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`.0`X
M`#$`,P`P`"P`,@.`P`# `-P`M`#$`,0`M`#(`, `@.`# `, `Z`# `, `Z`# `
M, `N`# `, `P`"P`,0`S`#$`-0`P`#(`. `R`"P`,0`P`# `.0`Y`#,`+ !-
M`&$`; !C`&\`; !M`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`
M. `Q`#,`,0`L`#(`, `P`#<`+0`Q`#$`+0`R`#$`( `P`# `.@.`P`# `.@.`P
M`# `+@.`P`# `, `L`#$`,P`Q`#4`, `R`#@.`,0`L`#$`, `P`#D`.0`S`"P`
M30!A`&P`8P!O`&P`;0`Q``T`"@.`T`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y
M`#@.`,0`S`#(`+ `R`# `, `W`"T`,0`Q`"T`,@.`R`" `, `P`#H`, `P`#H`
M, `P`"X`, `P`# `+ `Q`#,`,0`U`# `,@.`X`# `+ `Q`# `, `Y`#D`,P`L
M`$T`80!L`&,`;P!L`&T`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`
M.0`X`#$`,P`S`"P`,@.`P`# `-P`M`#$`,0`M`#(`,P`@.`# `, `Z`# `, `Z
M`# `, `N`# `, `P`"P`,0`S`#$`-0`P`#(`-P`Y`"P`,0`P`# `.0`Y`#,`
M+ !-`&$`; !C`&\`; !M`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T
M`#D`. `Q`#,`- `L`#(`, `P`#<`+0`Q`#$`+0`R`#0`( `P`# `.@.`P`# `
M.@.`P`# `+@.`P`# `, `L`#$`+ `Q`# `, `Y`#D`,P`L`$T`80!L`&,`;P!L
M`&T`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`.0`X`#$`,P`U`"P`
M,@.`P`# `-P`M`#$`,0`M`#(`-0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P
I`"P`,0`L`#$`, `P`#D`.0`S`"P`30!A`&P`8P!O`&P`;0`Q``T`"@.``
`
end
begin 666 FailedDataSet1.csv
M5P!%`$4`2P!?`$X`3P`L`%D`10!!`%(`+ !7`$\`4@.!+`$D`3@.!'`% `10!2
M`$D`3P!$`$D`1 `L`%<`3P!2`$L`20!.`$<`1 !!`%0`10`L`$,`3@.!5`$T`
M+ !%`$X`50!-`"P`3@.!!`$T`10`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q
M`#0`.0`X`#$`, `Q`"P`,@.`P`# `-P`M`#$`,0`M`#$`.0`@.`# `, `Z`# `
M, `Z`# `, `N`# `, `P`"P`,0`S`#$`-0`P`#0`,P`U`"P`,0`P`# `.0`Y
M`#$`+ !0`&$`=0!L`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`
M. `Q`# `,@.`L`#(`, `P`#<`+0`Q`#$`+0`R`# `( `P`# `.@.`P`# `.@.`P
M`# `+@.`P`# `, `L`#$`,P`Q`#4`, `T`#,`-@.`L`#$`, `P`#D`.0`Q`"P`
M4 !A`'4`; `Q``T`"@.`T`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`,0`P
M`#,`+ `R`# `, `W`"T`,0`Q`"T`,@.`Q`" `, `P`#H`, `P`#H`, `P`"X`
M, `P`# `+ `Q`#,`,0`U`# `- `S`#<`+ `Q`# `, `Y`#D`,0`L`% `80!U
M`&P`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`.0`X`#$`, `T`"P`
M,@.`P`# `-P`M`#$`,0`M`#(`,@.`@.`# `, `Z`# `, `Z`# `, `N`# `, `P
M`"P`,0`S`#$`-0`P`#0`,P`X`"P`,0`P`# `.0`Y`#$`+ !0`&$`=0!L`#$`
M#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`. `Q`# `-0`L`#(`, `P
M`#<`+0`Q`#$`+0`R`#,`( `P`# `.@.`P`# `.@.`P`# `+@.`P`# `, `L`#$`
M,P`Q`#4`, `T`#,`.0`L`#$`, `P`#D`.0`Q`"P`4 !A`'4`; `Q``T`"@.`T
M`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`,0`P`#8`+ `R`# `, `W`"T`
M,0`Q`"T`,@.`T`" `, `P`#H`, `P`#H`, `P`"X`, `P`# `+ `Q`"P`,0`P
M`# `.0`Y`#$`+ !0`&$`=0!L`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`
M,0`T`#D`. `Q`# `-P`L`#(`, `P`#<`+0`Q`#$`+0`R`#4`( `P`# `.@.`P
M`# `.@.`P`# `+@.`P`# `, `L`#$`+ `Q`# `, `Y`#D`,0`L`% `80!U`&P`
M,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `U`"P`,@.`P
M`# `-P`M`#$`,0`M`#$`.0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`
M,0`S`#$`-0`P`#0`,P`T`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-
M``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `V`"P`,@.`P`# `
M-P`M`#$`,0`M`#(`, `@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S
M`# `,P`U`#4`,P`R`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`
M- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `W`"P`,@.`P`# `-P`M
M`#$`,0`M`#(`,0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`# `
M,P`U`#4`,P`S`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W
M`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `X`"P`,@.`P`# `-P`M`#$`
M,0`M`#(`,0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`#$`-0`P
M`#0`,P`S`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`
M,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `Y`"P`,@.`P`# `-P`M`#$`,0`M
M`#(`,@.`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`# `,P`U`#4`
M,P`T`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P
M`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`.0`P`"P`,@.`P`# `-P`M`#$`,0`M`#(`
M,P`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`# `,P`U`#4`,P`U
M`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P`# `
M-P`L`#$`,@.`Q`#@.`.0`W`#(`.0`Q`"P`,@.`P`# `-P`M`#$`,0`M`#(`- `@.
M`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`L`#$`, `P`#D`.0`R`"P`
M0@.!R`&4`;@.!T`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`X`#D`-P`R
M`#D`,@.`L`#(`, `P`#<`+0`Q`#$`+0`R`#4`( `P`# `.@.`P`# `.@.`P`# `
M+@.`P`# `, `L`#$`+ `Q`# `, `Y`#D`,@.`L`$(`<@.!E`&X`= `Q``T`"@.`T
M`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`,0`R`#D`+ `R`# `, `W`"T`
M,0`Q`"T`,0`Y`" `, `P`#H`, `P`#H`, `P`"X`, `P`# `+ `Q`#,`,0`U
M`# `,@.`X`#,`+ `Q`# `, `Y`#D`,P`L`$T`80!L`&,`;P!L`&T`,0`-``H`
M- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`.0`X`#$`,P`P`"P`,@.`P`# `-P`M
M`#$`,0`M`#(`, `@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`#$`
M-0`P`#(`. `R`"P`,0`P`# `.0`Y`#,`+ !-`&$`; !C`&\`; !M`#$`#0`*
M`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`. `Q`#,`,0`L`#(`, `P`#<`
M+0`Q`#$`+0`R`#$`( `P`# `.@.`P`# `.@.`P`# `+@.`P`# `, `L`#$`,P`Q
M`#4`, `R`#@.`,0`L`#$`, `P`#D`.0`S`"P`30!A`&P`8P!O`&P`;0`Q``T`
M"@.`T`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`,0`S`#(`+ `R`# `, `W
M`"T`,0`Q`"T`,@.`R`" `, `P`#H`, `P`#H`, `P`"X`, `P`# `+ `Q`#,`
M,0`U`# `,@.`X`# `+ `Q`# `, `Y`#D`,P`L`$T`80!L`&,`;P!L`&T`,0`-
M``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`.0`X`#$`,P`S`"P`,@.`P`# `
M-P`M`#$`,0`M`#(`,P`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S
M`#$`-0`P`#(`-P`Y`"P`,0`P`# `.0`Y`#,`+ !-`&$`; !C`&\`; !M`#$`
M#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`. `Q`#,`- `L`#(`, `P
M`#<`+0`Q`#$`+0`R`#0`( `P`# `.@.`P`# `.@.`P`# `+@.`P`# `, `L`#$`
M+ `Q`# `, `Y`#D`,P`L`$T`80!L`&,`;P!L`&T`,0`-``H`- `W`"P`,@.`P
M`# `-P`L`#$`,@.`Q`#0`.0`X`#$`,P`U`"P`,@.`P`# `-P`M`#$`,0`M`#(`
M-0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`L`#$`, `P`#D`.0`S
7`"P`30!A`&P`8P!O`&P`;0`Q``T`"@.``
`
end
begin 666 FailedDataSet2.csv
M5P!%`$4`2P!?`$X`3P`L`%D`10!!`%(`+ !7`$\`4@.!+`$D`3@.!'`% `10!2
M`$D`3P!$`$D`1 `L`%<`3P!2`$L`20!.`$<`1 !!`%0`10`L`$,`3@.!5`$T`
M+ !%`$X`50!-`"P`3@.!!`$T`10`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q
M`#0`.0`X`#$`, `Q`"P`,@.`P`# `-P`M`#$`,0`M`#$`.0`@.`# `, `Z`# `
M, `Z`# `, `N`# `, `P`"P`,0`S`#$`-0`P`#0`,P`U`"P`,0`P`# `.0`Y
M`#$`+ !0`&$`=0!L`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`
M. `Q`# `,@.`L`#(`, `P`#<`+0`Q`#$`+0`R`# `( `P`# `.@.`P`# `.@.`P
M`# `+@.`P`# `, `L`#$`,P`Q`#4`, `T`#,`-@.`L`#$`, `P`#D`.0`Q`"P`
M4 !A`'4`; `Q``T`"@.`T`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`,0`P
M`#,`+ `R`# `, `W`"T`,0`Q`"T`,@.`Q`" `, `P`#H`, `P`#H`, `P`"X`
M, `P`# `+ `Q`#,`,0`U`# `- `S`#<`+ `Q`# `, `Y`#D`,0`L`% `80!U
M`&P`,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#0`.0`X`#$`, `T`"P`
M,@.`P`# `-P`M`#$`,0`M`#(`,@.`@.`# `, `Z`# `, `Z`# `, `N`# `, `P
M`"P`,0`S`#$`-0`P`#0`,P`X`"P`,0`P`# `.0`Y`#$`+ !0`&$`=0!L`#$`
M#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`T`#D`. `Q`# `-0`L`#(`, `P
M`#<`+0`Q`#$`+0`R`#,`( `P`# `.@.`P`# `.@.`P`# `+@.`P`# `, `L`#$`
M,P`Q`#4`, `T`#,`.0`L`#$`, `P`#D`.0`Q`"P`4 !A`'4`; `Q``T`"@.`T
M`#<`+ `R`# `, `W`"P`,0`R`#$`- `Y`#@.`,0`P`#8`+ `R`# `, `W`"T`
M,0`Q`"T`,@.`T`" `, `P`#H`, `P`#H`, `P`"X`, `P`# `+ `Q`"P`,0`P
M`# `.0`Y`#$`+ !0`&$`=0!L`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`
M,0`T`#D`. `Q`# `-P`L`#(`, `P`#<`+0`Q`#$`+0`R`#4`( `P`# `.@.`P
M`# `.@.`P`# `+@.`P`# `, `L`#$`+ `Q`# `, `Y`#D`,0`L`% `80!U`&P`
M,0`-``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `U`"P`,@.`P
M`# `-P`M`#$`,0`M`#$`.0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`
M,0`S`#$`-0`P`#0`,P`T`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-
M``H`- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `V`"P`,@.`P`# `
M-P`M`#$`,0`M`#(`, `@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S
M`# `,P`U`#4`,P`R`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`
M- `W`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `W`"P`,@.`P`# `-P`M
M`#$`,0`M`#(`,0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`# `
M,P`U`#4`,P`S`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W
M`"P`,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `X`"P`,@.`P`# `-P`M`#$`
M,0`M`#(`,0`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`#$`-0`P
M`#0`,P`S`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`
M,@.`P`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`. `Y`"P`,@.`P`# `-P`M`#$`,0`M
M`#(`,@.`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`# `,P`U`#4`
M,P`T`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P
M`# `-P`L`#$`,@.`Q`#@.`.0`W`#(`.0`P`"P`,@.`P`# `-P`M`#$`,0`M`#(`
M,P`@.`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`S`# `,P`U`#4`,P`U
M`"P`,0`P`# `.0`Y`#(`+ !"`'(`90!N`'0`,0`-``H`- `W`"P`,@.`P`# `
M-P`L`#$`,@.`Q`#@.`.0`W`#(`.0`Q`"P`,@.`P`# `-P`M`#$`,0`M`#(`- `@.
M`# `, `Z`# `, `Z`# `, `N`# `, `P`"P`,0`L`#$`, `P`#D`.0`R`"P`
M0@.!R`&4`;@.!T`#$`#0`*`#0`-P`L`#(`, `P`#<`+ `Q`#(`,0`X`#D`-P`R
M`#D`,@.`L`#(`, `P`#<`+0`Q`#$`+0`R`#4`( `P`# `.@.`P`# `.@.`P`# `
L+@.`P`# `, `L`#$`+ `Q`# `, `Y`#D`,@.`L`$(`<@.!E`&X`= `Q``T`"@.``
`
end|||Chris,
In the dialog box that opens , select "Allfiles", then type in the
file name with the extension , viz. Test.xls and that will create the
file for you.
Cheers
Shai
On Dec 10, 5:23 pm, we...@.online.microsoft.com (Wei Lu [MSFT]) wrote:
> Hello,
> Have you tried to export the result to csv and open it in Excel?
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello,
I would like to get the report definition so that I can go for further
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Shai,
Thanks for the input and it works. I can export the dataset to Excel without
any problem.
Please have a look at my reply to Wei eariler with more information.
Thank you again for the help...
<shaikat.das@.gmail.com> wrote in message
news:c31b3356-cc38-4f95-905f-c7c2ede4e7ff@.t1g2000pra.googlegroups.com...
> Chris,
> In the dialog box that opens , select "Allfiles", then type in the
> file name with the extension , viz. Test.xls and that will create the
> file for you.
>
> Cheers
> Shai
> On Dec 10, 5:23 pm, we...@.online.microsoft.com (Wei Lu [MSFT]) wrote:
>> Hello,
>> Have you tried to export the result to csv and open it in Excel?
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> ==================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>|||Hi
So its not Excel and its not SQL . Oook, now lets consider the
report , I suspect that the grouping on the big int field is causing
excel to crash. Depends on how many unique big ints you have in your
data set , but the next thing I would do is to try and isolate if any
one of the big int values is causing the crash. The easiest way to do
this would be to limit the big int in your data set to one of each
unique value and exporting the report to excel. But if you have a very
high number of big ints then it can be a long process. Whatever the
data , excel should not crash . Having said that , if the grouping is
too complicated, I would also suggest trying sub reports to simplify
the process.
Cheers
Shai|||Hi Wei,
This is just a test to see whether I am able to reply to this post.
I have tried to reply your post for number of time without any success.
I was thinking may be the attached files caused it so this reply is just a
test.
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:9oAE027OIHA.5204@.TK2MSFTNGHUB02.phx.gbl...
> Hello,
> I would like to get the report definition so that I can go for further
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Chris,
I could see your post, but I could not see other posts.
You may send the rdl file to me directly. To get me email address, please
remove the ONLINE in my display email address.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Sunday, February 26, 2012

Export to excel from report manager problem

When i use export from report manager to excel for some reason it gave us
that error
but one thing more i used open that report using visual studio on my friend
computer and then preview the report and then select save as excel file . it
didnt give me error but when i use report manager and then try to export to
excel has that error
Microsoft Excel File Repair Log
Errors were detected in file C:\test.xls'
The following is a list of repairs:
Damage to the file was so extensive that repairs were not possible. Excel
attempted to recover your formulas and values, but some data may have been
lost or corrupted.Hello Amjad.
I've seen this before. This happened when i had certain formulas in my
report, either in text boxes or in a chart. Are you using any complex
formulas? If you are, take them out temporarily, and try to export the
file. Let me know if it works.
Amjad wrote:
> When i use export from report manager to excel for some reason it gave us
> that error
> but one thing more i used open that report using visual studio on my friend
> computer and then preview the report and then select save as excel file . it
> didnt give me error but when i use report manager and then try to export to
> excel has that error
> Microsoft Excel File Repair Log
> Errors were detected in file C:\test.xls'
> The following is a list of repairs:
> Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have been
> lost or corrupted.|||Thanks
Yeah i was using a two charts but for certain reason for one year as year
was my parameter did give me any error and for another year data it gave me
error to open affter export. then i removed the chart and after that it didnt
actually i was using two chart , removing either of one solved the problem
but i need to include these chart back but due to that problem i removed it
temprarly....
Do you have any solution or any hot fix availabe to solve this problem.
because on of my friend computer it did export from visual studio preview
option not from report manager but on my computer it did not export both from
visual studio and report manager. it seem that his computer got some updates
for visual studio that i am missing thats why its giving me that problem even
from visual studio preview option. so if we find that hotfix so i can install
both on report manager server and my local computer...
"KevinGreen24@.gmail.com" wrote:
> Hello Amjad.
> I've seen this before. This happened when i had certain formulas in my
> report, either in text boxes or in a chart. Are you using any complex
> formulas? If you are, take them out temporarily, and try to export the
> file. Let me know if it works.
>
> Amjad wrote:
> > When i use export from report manager to excel for some reason it gave us
> > that error
> > but one thing more i used open that report using visual studio on my friend
> > computer and then preview the report and then select save as excel file . it
> > didnt give me error but when i use report manager and then try to export to
> > excel has that error
> >
> > Microsoft Excel File Repair Log
> >
> > Errors were detected in file C:\test.xls'
> > The following is a list of repairs:
> >
> > Damage to the file was so extensive that repairs were not possible. Excel
> > attempted to recover your formulas and values, but some data may have been
> > lost or corrupted.
>|||OK. Put the charts back in, and try to export again.
I'm not exactly sure of any hotfixes right now. If there's any service
packs / patches out there for MSRS 2005 you should install them. But
I'm not positive there are any. I'm sorry I couldn't be of more help.
Amjad wrote:
> Thanks
> Yeah i was using a two charts but for certain reason for one year as year
> was my parameter did give me any error and for another year data it gave me
> error to open affter export. then i removed the chart and after that it didnt
> actually i was using two chart , removing either of one solved the problem
> but i need to include these chart back but due to that problem i removed it
> temprarly....
> Do you have any solution or any hot fix availabe to solve this problem.
> because on of my friend computer it did export from visual studio preview
> option not from report manager but on my computer it did not export both from
> visual studio and report manager. it seem that his computer got some updates
> for visual studio that i am missing thats why its giving me that problem even
> from visual studio preview option. so if we find that hotfix so i can install
> both on report manager server and my local computer...
>
> "KevinGreen24@.gmail.com" wrote:
> > Hello Amjad.
> >
> > I've seen this before. This happened when i had certain formulas in my
> > report, either in text boxes or in a chart. Are you using any complex
> > formulas? If you are, take them out temporarily, and try to export the
> > file. Let me know if it works.
> >
> >
> > Amjad wrote:
> > > When i use export from report manager to excel for some reason it gave us
> > > that error
> > > but one thing more i used open that report using visual studio on my friend
> > > computer and then preview the report and then select save as excel file . it
> > > didnt give me error but when i use report manager and then try to export to
> > > excel has that error
> > >
> > > Microsoft Excel File Repair Log
> > >
> > > Errors were detected in file C:\test.xls'
> > > The following is a list of repairs:
> > >
> > > Damage to the file was so extensive that repairs were not possible. Excel
> > > attempted to recover your formulas and values, but some data may have been
> > > lost or corrupted.
> >
> >

Export to Excel fails - ASPNET_WP.EXE consumes 60% RAM

I'm trying to export a report to Excel that contains 60,000 rows (but not
more than Excels 65,000 limit) and I get an "internal server error".
When I check the event log on the server it states that aspnet_wp.exe
terminated the report process because it had consumed more than 60% of the
servers availible RAM (1Gb total).
PDF and CSV work fine. Does anyone know anything about this'
--
Cheers
NickExporting to Excel is quite intensive on resources. The problem is that MS
is trying for very high fidelity on what the data looks like. For instance
if you have drill down it creates a spreadsheet with drilldown. For that
amount of data I suggest that you use CSV in ASCII format (the default is
Unicode). Excel doesn't recognize Unicode CSV and puts it all in one column.
With ASCII format Excel properly puts them in the correct columns. Another
tip, for your table in the report, click on each field of the detail and
make sure it has the name that you want on Export. The CSV export uses this
name. To get CSV in ASCII you need to use a jump to URL and include ASCII in
the deviceinfo (or something like that, doing this from memory from home).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Nick Prudhoe" <NickPrudhoe@.discussions.microsoft.com> wrote in message
news:3F7F032F-9416-462B-89BC-F6C90E64FA5A@.microsoft.com...
> I'm trying to export a report to Excel that contains 60,000 rows (but not
> more than Excels 65,000 limit) and I get an "internal server error".
> When I check the event log on the server it states that aspnet_wp.exe
> terminated the report process because it had consumed more than 60% of the
> servers availible RAM (1Gb total).
> PDF and CSV work fine. Does anyone know anything about this'
> --
> Cheers
> Nick|||Thanks. I have already managed to get the same report to export to CSV. I'm
trying to prove reporting services out before my company goes down that
track. The performance on exports to Excel is disapointing, i would have
hoped it was better than PDF as it's an MS technology.
--
Cheers
Nick
"Bruce L-C [MVP]" wrote:
> Exporting to Excel is quite intensive on resources. The problem is that MS
> is trying for very high fidelity on what the data looks like. For instance
> if you have drill down it creates a spreadsheet with drilldown. For that
> amount of data I suggest that you use CSV in ASCII format (the default is
> Unicode). Excel doesn't recognize Unicode CSV and puts it all in one column.
> With ASCII format Excel properly puts them in the correct columns. Another
> tip, for your table in the report, click on each field of the detail and
> make sure it has the name that you want on Export. The CSV export uses this
> name. To get CSV in ASCII you need to use a jump to URL and include ASCII in
> the deviceinfo (or something like that, doing this from memory from home).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Nick Prudhoe" <NickPrudhoe@.discussions.microsoft.com> wrote in message
> news:3F7F032F-9416-462B-89BC-F6C90E64FA5A@.microsoft.com...
> > I'm trying to export a report to Excel that contains 60,000 rows (but not
> > more than Excels 65,000 limit) and I get an "internal server error".
> >
> > When I check the event log on the server it states that aspnet_wp.exe
> > terminated the report process because it had consumed more than 60% of the
> > servers availible RAM (1Gb total).
> >
> > PDF and CSV work fine. Does anyone know anything about this'
> > --
> > Cheers
> > Nick
>
>|||Yeah...one would think...although I have seen a significant performance
improvement in service pack 2.
Nick Prudhoe wrote:
> Thanks. I have already managed to get the same report to export to CSV. I'm
> trying to prove reporting services out before my company goes down that
> track. The performance on exports to Excel is disapointing, i would have
> hoped it was better than PDF as it's an MS technology.
>

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